evidence-binder/workplans/EBIND-WP-0002-capability-index-repair.md
tegwick e462775bae
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
CI Smoke / container-smoke (push) Successful in 2s
Repair capability federation index
2026-08-21 08:58:31 +02:00

69 lines
2.5 KiB
Markdown

---
id: EBIND-WP-0002
type: workplan
title: "Repair capability registry federation metadata"
domain: infotech
repo: evidence-binder
status: active
owner: codex
topic_slug: capability_registry_federation
created: "2026-08-21"
updated: "2026-08-21"
---
# EBIND-WP-0002 — Repair capability registry federation metadata
Restore `evidence-binder` to the reuse-surface federation after its capability
index was found to contain `SCOPE.md` advertisement blocks instead of validated
registry rows. Preserve the valid SCOPE advertisements, add resolvable registry
entries, and assess maturity from current repository evidence.
## Repair and document the capability entries
```task
id: EBIND-WP-0002-T01
status: done
priority: high
```
Translate both index rows to the federation contract and add their backing
Markdown entries. Use repository evidence, current consumer integration, and
the reuse-surface maturity standard to choose defensible D/A/C/R vectors.
Acceptance:
- both rows expose all required federation fields and stable capability IDs
- both `path` values resolve to schema-valid Markdown entries
- maturity rationale distinguishes source availability from completeness and
reliability evidence
## Validate, synchronize, and request federation re-enable
```task
id: EBIND-WP-0002-T02
status: wait
priority: high
blocking_reason: validated repair must be published to Forgejo and indexed by the production registrar
```
Run the reuse-surface validator and the repository quality checks, synchronize
the workplan with State Hub, and send non-secret completion evidence to the
reuse-surface owner so its federation source can be re-enabled.
Acceptance:
- registry validation passes without index-drift warnings
- tests, typecheck, lint, and repository diff checks pass
- State Hub records the completed work and reuse-surface receives the repair
summary and maturity vectors
Local implementation completed 2026-08-21. The checked-out reuse-surface
validator accepted both entries with warnings treated as failures. Repository
verification passed 43 tests plus typecheck, lint, and `git diff --check`. The
quality pass also found and removed a stale `AttributeValueType` import that had
been failing both typecheck and lint.
Closeout is waiting on two external-state changes: publication of the validated
working-tree repair to Forgejo, after which reuse-surface can re-enable the
member source, and production-registrar assignment of State Hub identifiers for
this new workplan and its tasks.