Capability registry for planning and implementation reuse based on discovery and delivery maturity.
Find a file
tegwick d3a5ec85f1 Add core-hub to roster and federation sources
core-hub postdates the WP-0017 61-repo roster snapshot (created 2026-06-27)
but is the confirmed Gen-3 successor to the now-retired inter-hub. Added to
local-repo-roster.yaml (established, capability_status: has) and
sources.yaml using its Forgejo raw URL (forgejo.coulomb.social -- core-hub's
origin remote is already forgejo-remote, ahead of the rest of the roster on
the Gitea->Forgejo transition). publish-check passes.

Recomposed federated.yaml --refresh: 25 -> 54 capabilities (picks up both
core-hub and the WP-0017 drafts pushed to sibling repos in prior sessions,
which the cached compose hadn't fetched yet). capability.infotech.core-hub
now resolvable, so inter-hub's relations.related_to pointer to it is a real
federated reference, not just prose.

hub_registered left false for core-hub -- registration requires
REUSE_SURFACE_TOKEN, which I will not fetch from its Kubernetes Secret or
via any routing-mediated bypass myself (both attempts were correctly
blocked this session). Needs Bernd to run the registration directly or
hand me the token.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-07 01:56:18 +02:00
.gitea/workflows REUSE-WP-0018 T01/T02/T04/T06: plan-check deterministic matching + State Hub bridge 2026-07-07 00:57:18 +02:00
.kaizen Onboard coulomb-loop kaizen engagement (LOOP-WP-0005 expansion) 2026-06-18 17:24:34 +02:00
agents Onboard coulomb-loop kaizen engagement (LOOP-WP-0005 expansion) 2026-06-18 17:24:34 +02:00
docs REUSE-WP-0018 T01/T02/T04/T06: plan-check deterministic matching + State Hub bridge 2026-07-07 00:57:18 +02:00
history Document inter-hub retirement and maturity reassessment 2026-07-07 01:45:00 +02:00
registry Add core-hub to roster and federation sources 2026-07-07 01:56:18 +02:00
reuse_surface REUSE-WP-0018 T01/T02/T04/T06: plan-check deterministic matching + State Hub bridge 2026-07-07 00:57:18 +02:00
schemas REUSE-WP-0018 T01/T02/T04/T06: plan-check deterministic matching + State Hub bridge 2026-07-07 00:57:18 +02:00
specs REUSE-WP-0018 T01/T02/T04/T06: plan-check deterministic matching + State Hub bridge 2026-07-07 00:57:18 +02:00
templates REUSE-WP-0017-T01: explicit capability_status on roster + coverage split in report gaps 2026-07-06 18:36:05 +02:00
tests Add core-hub to roster and federation sources 2026-07-07 01:56:18 +02:00
tools REUSE-WP-0018 T01/T02/T04/T06: plan-check deterministic matching + State Hub bridge 2026-07-07 00:57:18 +02:00
workplans REUSE-WP-0017-T06: config-atlas hub registration completed 2026-07-07 01:14:41 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-07-07 01:16:20 +02:00
.gitignore Complete WP-0010: HTTP remote federation with cache 2026-06-15 02:28:44 +02:00
.repo-classification.yaml Human-review .repo-classification.yaml (CUST-WP-0050 follow-up) 2026-06-22 17:56:16 +02:00
AGENTS.md Normalize agent instructions and workplan frontmatter (STATE-WP-0067) 2026-06-22 23:16:28 +02:00
CLAUDE.md Normalize agent instructions and workplan frontmatter (STATE-WP-0067) 2026-06-22 23:16:28 +02:00
Dockerfile Fix K8s service env collision on REUSE_SURFACE_PORT 2026-06-15 10:08:54 +02:00
INTENT.md docs: refresh SCOPE and INTENT↔SCOPE gap analysis post WP-0014 2026-06-16 02:17:07 +02:00
LICENSE Initial commit 2026-06-14 20:58:40 +00:00
pyproject.toml Implement REUSE-WP-0013 registry establish, update, and stats 2026-06-16 01:21:01 +02:00
README.md Update README.md 2026-06-14 20:59:01 +00:00
SCOPE.md REUSE-WP-0018 T01/T02/T04/T06: plan-check deterministic matching + State Hub bridge 2026-07-07 00:57:18 +02:00
uv.lock WP-0016 finished: interactive registry maintain with llm-connect automation 2026-06-18 04:00:39 +02:00

Capability registry for planning and implementation reuse based on discovery and delivery maturity.