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

Align capability index domain
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 11:59:37 +02:00
parent d21f8d97b8
commit 0c962ff508
2 changed files with 10 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

2
registry/indexes/capabilities.yaml
View file

@ -1,6 +1,6 @@
version: 1
updated: '2026-08-21'
domain: helix_forge
domain: infotech
capabilities:
- id: capability.evidence.binding
name: Evidence-to-Target Binding

10
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 railiance-platform federation action and repo-manager registrar indexing
blocking_reason: awaiting repo-manager production registrar indexing
```
Run the reuse-surface validator and the repository quality checks, synchronize
@ -79,3 +79,11 @@ 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`.
Federation confirmed 2026-08-21 in reuse-surface message
`5dff19b9-fed6-4acf-b14e-2859620afcf9`: the source is enabled, the public compose
is fresh, and both capabilities appear with the assessed vectors. REUSE-WP-0020
T03 and T04 are closed. The same review identified a non-blocking metadata
inconsistency, so the index header is aligned from the scaffold default
`helix_forge` to this repository's and both rows' actual domain, `infotech`.
Only production-registrar identifier assignment remains before T02 can close.