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

Close REUSE-WP-0020: evidence-binder live, 64 capabilities federated
All checks were successful
ci / validate-registry (push) Successful in 1m6s
Details
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
evidence-binder published their repaired index at e462775 and correctly held
the re-enable request until it was visible on Forgejo. Pre-checked this time
before touching production: backing entries return 200, and a local compose of
all 61 sources gave 64 capabilities with zero warnings and no duplicate IDs.

Public endpoint now serves 61 sources / 64 capabilities, with both
capability.evidence.binding and capability.evidence.rect-registry at
D3 / A2 / C3 / R3.

Open T09 for the gap this exposed: enabling a source does not invalidate the
composed index. The endpoint kept serving a stale compose, reporting
stale: false throughout, until POST /v1/federated/compose was called by hand.
A repo can be correctly registered and silently invisible.

SCOPE.md: refresh the federated counts, record the deployed image, and correct
the multi-domain claim — member rows have begun carrying their own domain
(evidence-binder publishes domain: infotech) even though the manifest is still
composed under helix_forge.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-08-21 10:46:59 +02:00
parent ff826beb33
commit d1de320743
3 changed files with 59 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

12
SCOPE.md
View file

@ -217,7 +217,9 @@ index, CLI automation, and the production hub.
## What Is Not Possible Yet
- **Multi-domain federation** — all indexed capabilities remain `helix_forge`
- **Multi-domain federation** — the federated index is still composed under a
single `helix_forge` manifest domain, though member rows have begun carrying
their own (`evidence-binder` publishes `domain: infotech`)
- **Planning analytics breadth** — `report gaps` shipped (REUSE-WP-0015-T03);
no roadmap views or standardization tracker beyond `overlaps` and compose
collision warnings
@ -239,14 +241,16 @@ See `tools/README.md` for command reference.
hub-registered (inter-hub registration disabled on hub), **62/62**
publish-check pass, **62/62** capability coverage (`has` or explicit `none`).
- **Federation:** `registry/federation/sources.yaml` — **61** enabled sources;
`registry/indexes/federated.yaml` — **61** composed capability rows
`registry/indexes/federated.yaml` — **64** composed capability rows
(inter-hub excluded; core-hub included; 0 duplicate-ID warnings at last compose).
- **CLI / service:** `reuse_surface/` — validate, query, export, overlaps,
catalog, federation, graph, hub client, establish/update/stats, `serve`
(FastAPI hub).
- **Production hub:** `https://reuse.coulomb.social` — **61** enabled repo
registrations; `GET /v1/federated` serves **61** capabilities from published
raw URLs (compose refreshed 2026-07-07).
registrations; `GET /v1/federated` serves **64** capabilities from published
raw URLs (compose refreshed 2026-08-21). Runs image
`forgejo.coulomb.social/coulomb/reuse-surface:main-b035664` (Helm revision 8);
`/health`, `/v1/repos`, `/v1/federated`, and `/v1/reuse-events` all answer.
- **Specs:** `specs/FederationHubAPI.md`, `schemas/hub-registration.schema.yaml`.
- **Docs:** `docs/CapabilityRegistryConcept.md`, `docs/RegistryFederation.md`,
`docs/IntentScopeGapAnalysis.md`, deploy guide `docs/deploy/reuse-kubernetes.md`.