Rename the two machine labels that nothing stores or publishes
Two names sat on the movable side of the line and had not moved.
`OpenAgentsWeb.RouteAuthority` declared the scope `machine:status` for
`GET /controller/status` while its immediate siblings, the two
`/controller/pairings` routes, declared `computer:pairing:create` and
`computer:pairing:claim`. It is now `computer:status`, and the principal reads
"active paired computer bearer". No token carries the string and no pipeline
authorizes against it: the only consumer is
`OpenAgentsWeb.ContributionContract.site_access/2`, which publishes a scope
only for paths the contribution contract lists, and `/controller/status` is
not one. Rendering that document yields two `machine` matches, both the
machine-readable representation URL and the phrase "on the same machine", and
no scope. `ApiRouteAuthority`, which feeds `GET /api/v3`, has no `machine`
string at all.
The four computer tools declared the `policy_facets` consent
`machine_pairing`. It is now `computer_pairing`. Unlike the neighbouring
`residency`, which reaches `artifact.facets` and so the `artifact_digest` and
`registry_digest` a `module_route_receipts` row stores, `policy_facets` is
only shape-checked — `OpenAgents.Tools.Registry` bounds its size and nothing
else reads it. It is not persisted, not digested, and not published, so the
name was free.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DTmy4SEXrHXouw5sZbs3f4
- Co-Authored-By
- Claude Opus 5 (1M context) <noreply@anthropic.com>
Deploy story
What this commit did to the running system — joined from the
forge receipt chain, the part a commit page elsewhere cannot
show.
Not deployed through the forge lane
No push, promotion, build, or deploy receipt references this
commit (receipts are scanned over a bounded recent window).
Changes shipped by full node replacement carry their proof in
the release gate receipt instead.