coulomb/reuse-surface
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity
Files
593738f20975acc64d37799111682544625954e2
reuse-surface/history/2026-06-17-sibling-registry-established.md
tegwick 195cd6e2d5
Some checks failed
ci / validate-registry (push) Has been cancelled
Details
Document sibling registry establishment and sync hub sources 
Record bootstrap of state-hub, feature-control, identity-canon, and shard-wiki
registries; hub sync materializes URL sources for all five federated repos.
2026-06-16 01:35:24 +02:00

1.2 KiB
Raw Blame History

Sibling capability registries established

Date: 2026-06-17
Method: reuse-surface establish --scaffold + entry migration from reuse-surface by owner

Repos bootstrapped

Repo Capabilities Commit Raw URL status
state-hub 2 70df013 HTTP 200
feature-control 3 82c7884 HTTP 200
identity-canon 2 c66bebc HTTP 200
shard-wiki 8 b31e9bc HTTP 200

Entries were copied from reuse-surface/registry/capabilities/ where owner matched the sibling repo slug. All repos passed reuse-surface validate --root <repo>.

Federation

  • Local registry/federation/sources.yaml — sibling index sources enabled
  • reuse-surface federation compose — 35 capabilities (15 duplicate IDs warned across reuse-surface + shard-wiki/wiki entries still present in both indexes)
  • Production hub https://reuse.coulomb.social — registered all four siblings; GET /v1/federated returned 27 capabilities across 5 repos

Follow-up

  • Deduplicate wiki capabilities still listed in reuse-surface index vs shard-wiki canonical index
  • Remove migrated entries from reuse-surface index when owners agree on single source of truth
Reference in New Issue View Git Blame Copy Permalink