Add REUSE-WP-0014 local repo registry rollout workplan
Some checks failed
ci / validate-registry (push) Has been cancelled

Define workstation-wide scope (all ~/ git repos), track 60 repos in
local-repo-roster.yaml with batch assignments, and document establishment
checklist for remaining 55 pending registries.
This commit is contained in:
2026-06-16 01:40:49 +02:00
parent 195cd6e2d5
commit e91c529358
4 changed files with 848 additions and 2 deletions

View File

@@ -0,0 +1,264 @@
---
id: REUSE-WP-0014
type: workplan
title: "Local workstation repo registry rollout"
domain: helix_forge
repo: reuse-surface
status: active
owner: codex
topic_slug: helix-forge
created: "2026-06-17"
updated: "2026-06-17"
---
# Local workstation repo registry rollout
Establish a capability registry (`registry/indexes/capabilities.yaml` plus entries)
in **every git repository** present one level under the workstation home
directory. REUSE-WP-0013 delivered `establish` tooling; REUSE-WP-0012/0013
dogfood established **five** repos ad hoc. This workplan systematizes the
remainder with a **tracked roster** and batched execution.
**Tracking artifact:** `registry/federation/local-repo-roster.yaml`
**Procedure:** `reuse-surface establish --scaffold` → seed (if any) → `validate --root` → commit → push → `establish --publish-check``hub register`
## Scope definition — “locally present repo”
A repo is in scope when **all** of the following hold:
| Criterion | Rule |
|---|---|
| Location | `~/<slug>/` — exactly one directory level under `$HOME` |
| Git | `git -C ~/<slug> rev-parse --is-inside-work-tree` succeeds |
| Exclusions | Dot-directories (e.g. `~/.grok`), non-git folders |
**Not in scope:** nested clones, `~/go/pkg`, `~/bin`, worktrees unless they appear
as top-level `~/<slug>` checkouts.
This replaces the informal “sibling repo” rule used in WP-0012/0013 (federation
manifest + hub block list + `owner` field in reuse-surface only).
## Roster summary (2026-06-17)
| Metric | Count |
|---|---|
| Total local git repos | **60** |
| Established | **5** |
| Pending | **55** |
| Pending with reuse-surface seed entries | **3** (`activity-core`, `audit-core`, `flex-auth`) |
### Already established
`reuse-surface`, `state-hub`, `feature-control`, `identity-canon`, `shard-wiki`
— see `history/2026-06-17-sibling-registry-established.md`.
Update `local-repo-roster.yaml` after each batch (`status`, `capability_count`,
`hub_registered`, `publish_check`).
## Suggested execution order
```text
T01 roster (done — maintain as source of truth)
→ T02 seed-ready repos (activity-core, audit-core, flex-auth)
→ T03T08 batches B01B06 (alphabetical pending slugs)
→ T09 hub register + publish-check sweep
→ T10 federation sources + deduplication
→ T11 documentation
```
## Per-repo establishment checklist
```bash
cd ~/<slug>
reuse-surface establish --scaffold --domain helix_forge
# if seed_capability_ids in roster: copy entries from reuse-surface by owner
# optional: LLM_CONNECT_URL=... reuse-surface establish --discover --dry-run
reuse-surface validate --root .
git add registry/ && git commit -m "Add capability registry"
git push origin main
reuse-surface establish --publish-check \
--raw-url https://gitea.coulomb.social/coulomb/<slug>/raw/main/registry/indexes/capabilities.yaml
REUSE_SURFACE_URL=https://reuse.coulomb.social reuse-surface hub register \
--repo <slug> --url <raw-url> --domain helix_forge
```
Mark roster fields when each step completes.
---
## Adopt Local Repo Roster
```task
id: REUSE-WP-0014-T01
status: done
priority: high
```
Create and maintain `registry/federation/local-repo-roster.yaml`:
- One row per `~/<slug>` git repo with `status`, `batch`, `seed_capability_ids`,
`hub_registered`, `publish_check`
- Regenerate or patch `summary` counts when batches complete
- Reference roster from this workplan and `docs/RegistryFederation.md`
**Done:** initial roster generated 2026-06-17 (60 repos, 5 established, 55 pending).
## Establish Seed-Ready Repos
```task
id: REUSE-WP-0014-T02
status: todo
priority: high
```
Establish repos that already have capability entries in reuse-surface index
(`owner` = repo slug):
| Slug | Seed IDs |
|---|---|
| `activity-core` | `capability.activity.event-coordinate` |
| `audit-core` | `capability.audit.event-retain` |
| `flex-auth` | `capability.authorization.policy-evaluate` |
Copy entry Markdown + index rows; validate; commit; push; publish-check; hub
register. Update roster to `established`.
## Establish Batch B01
```task
id: REUSE-WP-0014-T03
status: todo
priority: medium
```
Slugs: `activity-core`, `agentic-resources`, `artifact-store`, `audit-core`,
`can-you-assist`, `citation-engine`, `citation-evidence`, `citation-work`,
`coordination-engine`, `domain-tree`
Note: `activity-core` and `audit-core` overlap T02 — skip duplicate work if T02
finishes first; empty scaffold acceptable for repos without seeds.
## Establish Batch B02
```task
id: REUSE-WP-0014-T04
status: todo
priority: medium
```
Slugs: `email-connect`, `evidence-anchor`, `evidence-binder`, `evidence-source`,
`flex-auth`, `guide-board`, `helix-forge`, `hub-core`, `human-resources`,
`ihp-railiance-probe`
## Establish Batch B03
```task
id: REUSE-WP-0014-T05
status: todo
priority: medium
```
Slugs: `info-tech-canon`, `infospace-bench`, `inter-hub`, `issue-core`,
`kaizen-agentic`, `key-cape`, `kontextual-engine`, `llm-connect`,
`markitect-filter`, `markitect-main`
## Establish Batch B04
```task
id: REUSE-WP-0014-T06
status: todo
priority: medium
```
Slugs: `markitect-quarkdown`, `markitect-tool`, `net-kingdom`, `open-cmis-tck`,
`open-reuse`, `ops-bridge`, `ops-hub`, `ops-warden`, `phase-memory`,
`railiance-apps`
## Establish Batch B05
```task
id: REUSE-WP-0014-T07
status: todo
priority: medium
```
Slugs: `railiance-cluster`, `railiance-enablement`, `railiance-fabric`,
`railiance-forge`, `railiance-infra`, `railiance-platform`, `repo-scoping`,
`repo-seed`, `tegwick-control`, `the-custodian`
## Establish Batch B06
```task
id: REUSE-WP-0014-T08
status: todo
priority: medium
```
Slugs: `user-engine`, `vantage-point`, `vergabe-teilnahme`, `whynot-control`,
`whynot-design`
## Hub Register And Publish-Check Sweep
```task
id: REUSE-WP-0014-T09
status: todo
priority: high
```
For every roster row with `status: established` and `publish_check: pending`:
- Run `establish --publish-check` against Gitea raw URL
- `hub register` (or `hub update`) on `https://reuse.coulomb.social`
- Set `hub_registered: true` and `publish_check: pass` in roster
Target: hub federates all established local repos with HTTP 200 indexes.
## Federation Sources And Deduplication
```task
id: REUSE-WP-0014-T10
status: todo
priority: medium
```
- `reuse-surface hub sync --merge` after registrations
- `federation compose` — document duplicate-ID policy for entries migrated to
owner repos (e.g. wiki capabilities in reuse-surface vs shard-wiki)
- Plan removal of canonical duplicates from reuse-surface index (separate commit
per owner agreement)
## Documentation And Gap Analysis
```task
id: REUSE-WP-0014-T11
status: todo
priority: low
```
- `docs/RegistryFederation.md` — link `local-repo-roster.yaml` and scope definition
- `history/` — rollout milestone note when all batches complete
- `docs/IntentScopeGapAnalysis.md` — federation membership progress
- Optional: `reuse-surface stats --federation-ready` roster-driven CI informational
---
## Acceptance
- [ ] `local-repo-roster.yaml` lists all 60 local git repos with current status
- [ ] 55 pending repos reach `status: established` (or explicit `excluded` with rationale)
- [ ] Every established repo passes `validate --root` and `publish-check` (HTTP 200)
- [ ] Hub registers all established repos with published indexes
- [ ] Roster `summary.established` equals 60 (or documented exclusions)
- [ ] Federation compose succeeds with updated sources manifest
## Out of scope
- Repos not checked out under `~/<slug>`
- Auto `establish --discover` for every repo (optional per repo only)
- Removing reuse-surface canonical entries without owner review (T10 plans only)
## Progress log
| Date | Event |
|---|---|
| 2026-06-17 | WP-0014 created; roster 5/60 established; batches B01B06 assigned |