coulomb/evidence-binder
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Record federation and registrar escalation
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details

Browse source
This commit is contained in:
tegwick 2026-08-21 10:29:29 +02:00
parent 9e3f4a6994
commit d21f8d97b8
1 changed files with 10 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

11
workplans/EBIND-WP-0002-capability-index-repair.md
View file

@ -43,7 +43,7 @@ Acceptance:
id: EBIND-WP-0002-T02
status: wait
priority: high
blocking_reason: awaiting federation refresh confirmation and production registrar indexing
blocking_reason: awaiting railiance-platform federation action and repo-manager registrar indexing
```
Run the reuse-surface validator and the repository quality checks, synchronize
@ -70,3 +70,12 @@ refresh the source in State Hub message `9c857277-f0e9-4f29-9def-896bdba1fcc3`.
Closeout is waiting on two external-state confirmations: the capabilities
appearing in the federated API, and production-registrar assignment of State Hub
identifiers for this new workplan and its tasks.
Rechecked 2026-08-21: the hosted registration still reports `enabled: false`
and the federated API omits both capability IDs. The approved
`reuse-surface-hub-write-token` route was attempted without exposing or
persisting the credential, but OpenBao denied the proxy caller on the owning
runtime lane. The enable-and-compose action is escalated to the lane owner in
State Hub message `ad3221d0-ccd5-4f90-89b3-8bfec24a1f49`. The unread registrar
request was also rerouted to `repo-manager` in message
`5c74f09d-6ee6-4bac-b02f-18e6ab9ad173`.