diff --git a/INTENT.md b/INTENT.md index 78ca225..9ba5a8e 100644 --- a/INTENT.md +++ b/INTENT.md @@ -268,7 +268,7 @@ reuse-surface/ │ ├── README.md │ ├── capabilities/ # per-entry Markdown │ ├── indexes/ # capabilities.yaml, federated.yaml -│ └── federation/ # sources.yaml, cache/ +│ └── federation/ # sources.yaml, local-repo-roster.yaml, cache/ ├── docs/ │ ├── CapabilityRegistryConcept.md │ ├── RegistryFederation.md @@ -287,7 +287,8 @@ See `SCOPE.md` for what is possible now versus planned. See `docs/IntentScopeGapAnalysis.md` for tracked gaps between intent and delivered scope. Federation operations: `docs/RegistryFederation.md` and `specs/FederationHubAPI.md`. Assessment history: -`history/2026-06-15-intent-scope-assessment.md`. +`history/2026-06-15-intent-scope-assessment.md`, +`history/2026-06-16-local-repo-registry-rollout-complete.md`. ## Success Criteria diff --git a/SCOPE.md b/SCOPE.md index d543b02..d224bfd 100644 --- a/SCOPE.md +++ b/SCOPE.md @@ -62,7 +62,8 @@ The MVP registry foundation, CLI tooling (REUSE-WP-0003), federation stack - **Export planning cohorts** with `reuse-surface report cohorts` - **Bootstrap a sibling registry** with `reuse-surface establish --scaffold` - **Verify index publish readiness** with `reuse-surface establish --publish-check` -- **View registry stats** with `reuse-surface stats` +- **View registry stats** with `reuse-surface stats` (per-repo or + `--roster registry/federation/local-repo-roster.yaml --federation-ready`) - **Draft or refresh entries** with `reuse-surface establish --discover` and `reuse-surface update` (optional llm-connect backend) - **Run the hub locally or in a container** with `reuse-surface serve` @@ -79,13 +80,18 @@ index, CLI automation, and the production hub. - **Automatic hub refresh** — federated compose is on-demand; no polling or webhooks -- **Cross-repo federation at scale** — hub has one registered repo; sibling - domains must publish capability indexes before registration (see - `history/2026-06-16-hub-registration-blocks.md`) +- **Fully fetchable federation** — hub registers **60** workstation repos; **13** + still fail Gitea raw URL probe (operator visibility). See + `registry/federation/local-repo-roster.yaml` and + `history/2026-06-16-wp0014-remaining-work-by-repo.md` +- **Clean federated ID namespace** — **16** duplicate IDs across reuse-surface + and owner-repo indexes until per-owner dedup (see + `history/2026-06-16-federation-deduplication-plan.md`) +- **Multi-domain federation** — all indexed capabilities remain `helix_forge` - **Planning analytics beyond cohorts** — no gap reports, roadmap views, or standardization tracker beyond `report cohorts`, query, and export - **Managed platform posture** — hub runs as a container (A5 artifact) without - documented SLO, multi-replica, or Postgres backing + implemented SLO, multi-replica, or Postgres backing (criteria documented) - **Formal consumer feedback loop** for registry workflows (reliability evidence is mostly structural: CI/tests, not production telemetry) @@ -93,25 +99,32 @@ See `tools/README.md` for command reference. ## Current State -- **Status:** active MVP registry with CLI, federation, and production hub. -- **Capabilities:** 20 helix_forge entries in `registry/capabilities/`. +- **Status:** active MVP registry with CLI, federation, production hub, and + workstation-wide registry rollout (REUSE-WP-0014 finished). +- **Capabilities (reuse-surface):** 20 helix_forge entries in + `registry/capabilities/` (18 owner-migrated; dedup pending). +- **Workstation roster:** 60 local git repos at `~//` tracked in + `registry/federation/local-repo-roster.yaml` — all **established**, **60/60** + hub-registered, **47/60** publish-check pass. +- **Federation:** `registry/federation/sources.yaml` — **60** hub-synced URL + sources; `registry/indexes/federated.yaml` — **37** composed capability rows + (16 duplicate-ID warnings, 13 remote fetch warnings). - **CLI / service:** `reuse_surface/` — validate, query, export, overlaps, - catalog, federation, graph, hub client, `serve` (FastAPI hub). -- **Production hub:** `https://reuse.coulomb.social` on Railiance01 - (`92.205.62.239`); image `gitea.coulomb.social/coulomb/reuse-surface:cb7a6e4`; - TLS live; dogfood registration for `reuse-surface` (12 capabilities composed - on `/v1/federated`). + catalog, federation, graph, hub client, establish/update/stats, `serve` + (FastAPI hub). +- **Production hub:** `https://reuse.coulomb.social` — **60** repo registrations; + `GET /v1/federated` serves composed index from published raw URLs. - **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`. - **CI:** `.gitea/workflows/ci.yml` — validate, federation compose, catalog, graph, pytest, informational `report cohorts`. -- **Federated index:** `registry/indexes/federated.yaml` (local compose). - **Relation graph:** `docs/graph/capability-graph.mmd`, `docs/graph/index.html`. - **Searchable catalog:** `docs/catalog/search.html`. -- **Workplans:** REUSE-WP-0001 through REUSE-WP-0012 finished/archived; - **REUSE-WP-0013** finished (registry establish/update/stats). -- **Assessment history:** `history/2026-06-15-intent-scope-assessment.md`. +- **Workplans:** REUSE-WP-0001 through REUSE-WP-0014 finished; archived under + `workplans/archived/`. +- **Assessment history:** `history/` — intent/scope assessments, rollout + milestone, dedup plan, per-repo follow-up. - **Self-assessed vector:** `D5 / A4 / C5 / R3` (see `docs/IntentScopeGapAnalysis.md`). ## Repository Layout @@ -130,7 +143,7 @@ reuse-surface/ ├── registry/ │ ├── capabilities/ # per-entry Markdown │ ├── indexes/ # capabilities.yaml, federated.yaml -│ └── federation/ # sources.yaml, cache/ +│ └── federation/ # sources.yaml, local-repo-roster.yaml, cache/ ├── docs/ ├── tools/ └── workplans/ diff --git a/docs/IntentScopeGapAnalysis.md b/docs/IntentScopeGapAnalysis.md index 1560095..0c71dd9 100644 --- a/docs/IntentScopeGapAnalysis.md +++ b/docs/IntentScopeGapAnalysis.md @@ -3,36 +3,44 @@ **Repository:** `reuse-surface` **Artifact:** `docs/IntentScopeGapAnalysis.md` **Status:** Living analysis -**Updated:** 2026-06-16 +**Updated:** 2026-06-16 **Purpose:** Record alignment, drift, and open gaps between declared intent and current delivered scope so future workplans can close them deliberately. +**Canon:** Product truth in `INTENT.md`; delivery truth in `SCOPE.md`. + --- ## 1. Summary -`INTENT.md` describes the long-term capability registry product: a reuse surface -that makes capabilities visible, assessable, and consumable across planning and -implementation. `SCOPE.md` describes what the repository delivers today: an -**active MVP** with **20 helix_forge capabilities**, **A3 CLI tooling**, a -**hosted federation hub at A4** (`https://reuse.coulomb.social`), federation -compose, catalog/graph UIs, pytest + CI gates, and Markdown-first authoring. +`INTENT.md` defines the long-term capability registry product: a reuse surface +that makes capabilities visible, assessable, and consumable for planning and +implementation across repos and organizations. -REUSE-WP-0001 through REUSE-WP-0011 closed the original MVP and federation -roadmap. The documents are **directionally aligned** on registry-first reuse, -four maturity dimensions, and human/agent consumers. +`SCOPE.md` (refreshed post–WP-0014) describes current delivery: -**Remaining gaps** after REUSE-WP-0014 rollout are **operational polish** items: +| Dimension | Delivered today | +|---|---| +| Registry product | 20 helix_forge entries in reuse-surface; maturity model, schema, validation | +| Tooling | CLI **A3+**; hosted hub HTTP API **A4** at `https://reuse.coulomb.social` | +| Federation | 60 hub registrations; 60 URL sources; 37 composed federated rows | +| Workstation rollout | 60/60 local repos established (`local-repo-roster.yaml`) | +| Authoring aids | `establish`, `update`, `stats`, optional llm-connect discover | +| Observability | `report cohorts`, catalog/graph UIs, pytest + CI gates | -1. **Gitea publish visibility** — 60/60 workstation repos established and hub - registered; **13/60** still fail Gitea raw URL probe (operator action). Roster: - `registry/federation/local-repo-roster.yaml`. -2. **Index deduplication** — 16 duplicate IDs across reuse-surface and owner repos; - removal plan in `history/2026-06-16-federation-deduplication-plan.md`. -3. **Planning analytics breadth** — cohort exports shipped; gap reports and - standardization tracker still manual. -4. **Hub automation** — `hub sync` shipped; polling/webhooks still absent. -5. **Managed platform posture** — A5 container documented; A6/Postgres deferred. +REUSE-WP-0001 through REUSE-WP-0014 closed the MVP, federation hub, intent +alignment, registry bootstrap, and **local workstation registry rollout**. The +documents remain **directionally aligned** on registry-first reuse, four maturity +dimensions, and human/agent consumers. + +**Open gaps** (operator or follow-on workplans): + +1. **Gitea publish visibility** — 13/60 repos fail raw URL probe (federation fetch). +2. **Index deduplication** — 16 duplicate IDs (reuse-surface vs owner repos). +3. **Planning analytics breadth** — no gap reports, roadmap views, or standardization tracker. +4. **Hub automation** — no polling/webhooks for federated refresh. +5. **Managed platform posture** — A6/Postgres/multi-replica not implemented. +6. **Consumer reliability evidence** — catalog mostly R0–R2; thin telemetry loop. **Current reuse-surface product vector (self-assessment):** `D5 / A4 / C5 / R3` @@ -42,129 +50,121 @@ four maturity dimensions, and human/agent consumers. | Topic | INTENT.md | SCOPE.md | Status | |---|---|---|---| -| Registry-first boundary | Unregistered capabilities invisible | Same | Aligned | -| Four maturity dimensions | D, A, C, R with separate internal/external evidence | Same model in entries and schema | Aligned | -| Human and agent consumers | Registry formats for both | Markdown + YAML index + CLI + hub API | Aligned | -| Reuse over inventory | Explicit principle | Workflows, overlaps, federation | Aligned | -| Planning vs implementation reuse | Distinct dimensions | Query, vectors, consumption_modes | Aligned | -| Technical foundation | “Eventually technical” | CLI A3, hub API A4, container A5 artifact | Aligned (MVP met) | -| Implementation consumption modes | Discoverable modes per capability | Supported in schema and index | Aligned | -| Cross-repo / org reuse | D7 generalized primitives | helix_forge; hub 60 repos; 37 federated caps | Partial | -| Success criteria | Eight outcomes | Most met; cohort reports added | Partial | -| Repository layout in INTENT | `standards/`, JSON schema, single yaml | Aligned in WP-0012 | Aligned | -| State Hub / workplans | Not in INTENT | In scope; ADR-001 sync | SCOPE-only (OK) | -| Hosting registered capabilities | Out of scope | Hub hosts metadata/URLs only | Aligned | +| Registry-first boundary | Unregistered capabilities invisible | Same | **Aligned** | +| Four maturity dimensions | D, A, C, R; internal vs external evidence | Same in entries and schema | **Aligned** | +| Human and agent consumers | Registry formats for both | Markdown + YAML + CLI + hub API | **Aligned** | +| Reuse over inventory | Explicit principle | Query, overlaps, federation, dedup plan | **Aligned** | +| Planning vs implementation reuse | Distinct dimensions | Query, vectors, `consumption_modes` | **Aligned** | +| Technical foundation | Eventually technical | CLI A3, hub A4, container A5 artifact | **Aligned** | +| Cross-repo capability visibility | Reuse across repos/products/orgs | 60 repos scaffolded; 37 federated caps | **Partial** | +| Generalized primitives (D7) | Beyond single repo/domain | helix_forge only; no D7 pipeline view | **Partial** | +| Success criteria (8 outcomes) | See §5 | Most met; analytics + normalization partial | **Partial** | +| Repository layout | Tree in INTENT §Initial Repository Role | Matches SCOPE; roster artifact added | **Aligned** | +| State Hub / workplans | Not in INTENT | ADR-001 sync; delivery process | SCOPE-only (OK) | +| Hosting capabilities | Out of scope | Hub stores metadata/URLs only | **Aligned** | --- ## 3. INTENT → SCOPE Gaps (Open) -What INTENT still expects beyond current SCOPE delivery. +What `INTENT.md` still expects beyond current `SCOPE.md` delivery. -### 3.1 Cross-repo federation breadth (Medium — polish remaining) +### 3.1 Cross-repo federation fetch and namespace (Medium) -| INTENT claim | Current SCOPE reality | Gap | +| INTENT claim | SCOPE reality | Gap | |---|---|---| -| Capabilities reusable across repos, products, orgs | 20 reuse-surface entries + 17 owner rows; 37 federated | No multi-domain federation yet | -| Find capabilities before rebuilding (network scale) | Hub **60** registrations; compose **37** capabilities | 13 repos Gitea raw 404; 16 duplicate IDs | +| Capabilities reusable across repos, products, orgs | 60 repos on hub; 37 federated rows | Single domain (`helix_forge`) | +| Find capabilities before rebuilding at network scale | Hub + compose + roster | 13 indexes not HTTP-fetchable | +| Identify duplicates (success criterion) | `overlaps` + compose `warn` | 16 duplicate IDs unresolved in indexes | -**Status (WP-0014):** All workstation repos (`~//`) established with -registry scaffolds. `hub sync --merge` materializes 60 URL sources. Operator -must fix Gitea visibility for 13 slugs (see roster). Deduplicate owner-migrated -entries per `history/2026-06-16-federation-deduplication-plan.md`. +**Follow-up:** `history/2026-06-16-wp0014-remaining-work-by-repo.md` (Gitea); +`history/2026-06-16-federation-deduplication-plan.md` (reuse-surface dedup). ### 3.2 Planning support breadth (Low–Medium) -| INTENT claim | Current SCOPE reality | Gap | +| INTENT claim | SCOPE reality | Gap | |---|---|---| -| Plan prototype/MVP/enhancement/platform work | `report cohorts`, query, catalog | No gap reports or roadmap views | -| Identify gaps, duplicates, overlaps, standardization | `overlaps` command | No standardization tracker | -| Track progress to generalized capabilities (D7) | `promotion_history` per entry | No cross-entry D7 pipeline view | - -**Status (WP-0012):** `reuse-surface report cohorts` ships planning/implementation -filter exports. Broader portfolio analytics remain future work. +| Plan prototype/MVP/enhancement/platform work | `report cohorts`, query, catalog | No portfolio gap reports | +| Identify gaps, overlaps, standardization candidates | `overlaps` | No standardization workflow | +| Track progress to generalized capabilities (D7) | Per-entry `promotion_history` | No cross-entry D7 pipeline | ### 3.3 Hub operations (Low–Medium) -| INTENT claim | Current SCOPE reality | Gap | +| INTENT claim | SCOPE reality | Gap | |---|---|---| -| Offline federation manifest sync | `hub sync` with `--merge` / `--replace` | Shipped | -| Operational reuse | Production hub; hardening doc | No polling/webhooks; SQLite single-replica | - -**Status (WP-0012):** Backup, cert renewal, token rotation, and Postgres -decision criteria documented in `docs/deploy/reuse-kubernetes.md`. Multi-replica -implementation deferred. +| Operational federation | Production hub; `hub sync` | On-demand compose; no webhooks | +| Dependable platform consumption (R4+) | Container deploy doc | SQLite single-replica; no SLO enforcement | ### 3.4 Consumer reliability evidence (Low–Medium) -| INTENT claim | Current SCOPE reality | Gap | +| INTENT claim | SCOPE reality | Gap | |---|---|---| -| Reliability from consumer signals | Schema + checklist in `registry/README.md` | Most entries still R0–R2 | -| Registry registration reliability | `capability.registry.register` at R3 | Broader catalog evidence thin | +| Reliability from consumer signals | Schema + README checklist | Most entries R0–R2 | +| Trust for important workflows (R4+) | CI + hub smoke | No formal consumer_feedback loop | -**Status (WP-0012):** Three entries promoted with `consumer_feedback` and CI/hub -citations; formal telemetry loop still absent. +### 3.5 Owner-repo capability depth (Low — ongoing) + +| INTENT claim | SCOPE reality | Gap | +|---|---|---| +| Rich registry across organization | 60 scaffolds; 8 seeded | 47 repos at capability_count 0 | +| Discover mature capabilities network-wide | 37 federated rows | Growth is per-repo, optional | --- ## 4. Closed Gaps (Historical) -Previously high-severity gaps now delivered (REUSE-WP-0003 through WP-0011): - -| Area | Delivery | -|---|---| -| Automated validation | `reuse-surface validate` + CI | -| Query / export | `query`, `export` | -| Catalog and overlaps | `catalog`, `overlaps`, searchable HTML | -| Federation compose | Local + HTTP URL sources + cache | -| Network federation | Remote fetch in compose | -| Relation graphs | `graph`, Mermaid, HTML explorer | -| Hosted hub | `reuse-surface serve`, `hub` CLI, `reuse.coulomb.social` | -| Test suite | 20 pytest tests, fail-on-warnings in CI | -| Concept docs | `docs/CapabilityRegistryConcept.md` | -| Registry coverage | 20 capabilities (from 3 initial samples) | +| Workplan / milestone | Gap closed | Evidence | +|---|---|---| +| WP-0003 – WP-0011 | MVP CLI, validation, catalog, federation, hub | Archived workplans; pytest | +| WP-0012 | `hub sync`, cohort reports, INTENT layout, hub hardening doc | `hub_sync.py`, `docs/deploy/` | +| WP-0013 | Registry bootstrap in sibling repos | `establish`, `update`, `stats` | +| WP-0014 | Workstation registry rollout; hub 60 registrations | `local-repo-roster.yaml`; milestone history | +| Priority 18 | Sibling / workstation hub membership | 60/60 `hub list` | +| Priority 19–24 | See §8 | WP-0012/0013 deliveries | --- -## 5. Success Criteria vs Delivery +## 5. INTENT Success Criteria vs SCOPE Delivery -INTENT success criteria after WP-0011: +From `INTENT.md` §Success Criteria: -| Success criterion | Met today? | Notes | -|---|---|---| -| Find reusable capabilities before rebuilding | **Yes (MVP)** | Index, query, catalog, hub `/v1/federated` | -| Compare maturity consistently | **Yes** | Vectors, schema enums, graph relations | -| Distinguish conceptual readiness from delivery | **Yes** | D vs A separation | -| Distinguish internal assessment from external evidence | **Yes** | `maturity` vs `external_evidence` | -| Plan prototype/MVP/enhancement/platform work | **Partial** | `report cohorts` + query/catalog; no gap reports | -| Identify gaps, duplicates, overlaps, standardization | **Partial** | Overlaps command; no standardization workflow | -| Track progress to generalized capabilities | **Partial** | Per-entry `promotion_history`; no D7 pipeline | -| Make reuse normal in product/architecture work | **Partial** | AGENTS.md, hub 60 repos; publish/dedup polish | +| # | Criterion | Met? | SCOPE evidence | Remaining gap | +|---|---|---|---|---| +| 1 | Find reusable capabilities before rebuilding | **Yes** | Index, query, catalog, hub `/v1/federated`, federation compose | 13 sources not fetchable | +| 2 | Compare maturity consistently | **Yes** | Vectors, schema, graph relations | — | +| 3 | Distinguish conceptual readiness from delivery | **Yes** | D vs A in model and index | — | +| 4 | Distinguish internal assessment from external evidence | **Yes** | `maturity` vs `external_evidence` | — | +| 5 | Plan prototype/MVP/enhancement/platform work | **Partial** | `report cohorts`, query | No gap/roadmap reports | +| 6 | Identify gaps, duplicates, overlaps, standardization | **Partial** | `overlaps`, compose collision warnings | Dedup + standardization tracker | +| 7 | Track progress to generalized capabilities (D7) | **Partial** | `promotion_history` per entry | No org-wide D7 view | +| 8 | Make reuse normal in architecture work | **Partial** | AGENTS.md, 60-repo rollout | Publish + dedup polish | + +**Score:** 4 fully met, 4 partial — consistent with **C5** product completeness for +known registry expectations, not yet saturated (**C6**). --- ## 6. Completeness Assessment (SCOPE vs INTENT) -Using INTENT's completeness framing for the **reuse-surface product**: - | Area | INTENT expectation | Current delivery | Level | |---|---|---|---| | Registry model and principles | Full | INTENT + specs | C5 | -| Maturity standard | Full | `specs/CapabilityMaturityStandard.md` | C5 | +| Maturity standard | Full | `CapabilityMaturityStandard.md` | C5 | | Entry authoring | Full for MVP | Template + schema + README | C5 | -| Sample / seed registry | Examples | 20 helix_forge entries | C4 | -| Discovery surface | Machine-readable | Index, query, export, hub API | C5 | +| Seed registry (reuse-surface) | Examples + meta | 20 entries | C4 | +| Discovery surface | Machine-readable | Index, query, export, hub API, federated | C5 | | Validation | Tooling | `validate` + CI | C5 | | Search / filter | Supported | query, catalog HTML | C4 | -| Federation | Cross-repo | Compose + hub sync; 60 hub members; 37 federated caps | C5 | -| Agent instructions | Expected | AGENTS.md + tools README | C4 | -| Technical consumption | A3+ for tools | CLI A3, hub A4 | C4 | +| Federation membership | Cross-repo | 60 hub members; compose + sync | C5 | +| Federation fetch reliability | Published indexes | 47/60 publish pass | C3 | +| Workstation bootstrap | Org-wide visibility | Roster + establish tooling | C4 | +| Agent instructions | Expected | AGENTS.md, tools README | C4 | +| Technical consumption | A3+ tools | CLI A3, hub A4 | C4 | | Planning analytics | Success criteria | `report cohorts` | C3 | -| Documentation canon | Concept + assessment | Concept doc; assessment via README | C4 | +| Documentation canon | Concept + living delta | Concept doc + this file | C4 | -**Overall completeness vs INTENT:** **C5 (Expectation Complete)** for known -registry product expectations — workstation rollout (60 repos), hub sync, -cohort reports, and federation compose shipped; Gitea publish and dedup remain. +**Overall completeness vs INTENT:** **C5** for reuse-surface product scope; +**C3** for end-to-end fetchable federation until Gitea blockers clear. --- @@ -172,52 +172,48 @@ cohort reports, and federation compose shipped; Gitea publish and dedup remain. | Signal | State | |---|---| -| Automated tests | pytest (registry, federation, hub, hub_sync, reports) | -| Schema validation in CI | validate, federation, catalog, graph, pytest | -| Production hub | `reuse.coulomb.social` — TLS, health, dogfood registration | -| Consumer feedback on registry workflows | None formal | -| Known friction | 13 Gitea raw 404 repos; 16 federated duplicate IDs; hub SQLite single-replica | +| Automated tests | pytest (registry, federation, hub, hub_sync, stats, reports) | +| CI gates | validate, federation compose, catalog, graph, pytest | +| Production hub | `reuse.coulomb.social` — TLS, 60 registrations | +| Workstation rollout | Deterministic establish/validate; roster tracked | +| Consumer feedback | Informal; 3 entries with structured `consumer_feedback` | +| Known friction | 13 Gitea 404; 16 duplicate IDs; hub SQLite single-replica | **Overall reliability vs INTENT consumer-evidence framing:** **R3 (Usable)** — -CI and production smoke support normal agent/operator workflows with known -limitations. Not yet **R4 Dependable** without SLO, backup, and feedback data. +CI and production paths support normal agent/operator workflows with documented +limitations. **R4 (Dependable)** blocked on SLO, backup automation, and +consumer telemetry. --- ## 8. Priority Gap Closure Order -### Closed (WP-0001 – WP-0011) +### Closed (priorities 1–24) -Priorities 1–17 from the original roadmap are **closed**. See section 4 and -archived workplans under `workplans/archived/`. +See §4 and archived workplans `workplans/archived/`. -### Proposed next work +### Proposed next (priorities 25–27) -| Priority | Gap | Suggested outcome | Status | +| Priority | Gap | Suggested outcome | Owner | |---|---|---|---| -| 18 | Sibling hub registrations | Workstation repos on hub | **Closed** (WP-0014) — 60/60 registered; 13 publish blocked | -| 19 | `hub sync` | Write `sources.yaml` from hub state | **Closed** (WP-0012) | -| 20 | Planning cohort reports | Export/filter views for D5+/A4+ candidates | **Closed** (WP-0012) | -| 21 | INTENT layout sync | Update INTENT.md tree and example entry shape | **Closed** (WP-0012) | -| 22 | Hub hardening | Postgres option, backup, documented SLO (A5→A6 path) | **Closed** (doc; implementation deferred) | -| 23 | External evidence program | Raise catalog R levels with consumer_feedback | **Closed** (checklist + 3 entries; telemetry deferred) | -| 24 | Registry bootstrap tooling | `establish`, `update`, `stats` for sibling repos | **Closed** (WP-0013) | +| 25 | Gitea publish visibility (13 repos) | Raw URL HTTP 200 for all roster rows | Operator / Gitea | +| 26 | Federated ID deduplication | Per-owner removal from reuse-surface index | reuse-surface + owners | +| 27 | Planning analytics + standardization | Gap reports or standardization tracker workplan | Future WP | -**Workplan:** `REUSE-WP-0014` (finished). Prior: `REUSE-WP-0013`, `REUSE-WP-0012`. -**Assessment snapshots:** -`history/2026-06-15-intent-scope-assessment.md`, -`history/2026-06-16-hub-registration-blocks.md`, -`history/2026-06-16-local-repo-registry-rollout-complete.md`. +**Follow-up docs (no workplan ID):** + +- `history/2026-06-16-wp0014-remaining-work-by-repo.md` +- `history/2026-06-16-federation-deduplication-plan.md` +- `registry/federation/local-repo-roster.yaml` --- ## 9. Document Maintenance Rules -- Re-run this analysis when either `INTENT.md` or `SCOPE.md` changes materially. -- When a gap closes, update sections 3–8 and adjust the self-assessment vector. -- New workplans that close gaps should reference the relevant row in section 8. -- Prefer updating `SCOPE.md` for delivery truth and `INTENT.md` for product - truth; use this file to track delta between them. +- Re-run this analysis when `INTENT.md` or `SCOPE.md` changes materially. +- When a gap closes, update §3–§8 and adjust the self-assessment vector in `SCOPE.md`. +- New workplans should reference priority rows from §8. +- Prefer `SCOPE.md` for delivery truth; `INTENT.md` for product truth. --- @@ -225,15 +221,9 @@ archived workplans under `workplans/archived/`. | Date | Change | |---|---| -| 2026-06-15 | Initial analysis after REUSE-WP-0002 completion | -| 2026-06-15 | REUSE-WP-0003 closed priorities 1–8; vector D5/A3/C4/R2 | -| 2026-06-15 | REUSE-WP-0004 closed priorities 9–11 | -| 2026-06-15 | REUSE-WP-0005 closed priorities 12 and 14 | -| 2026-06-15 | REUSE-WP-0006 expanded registry to 12 capabilities | -| 2026-06-15 | REUSE-WP-0007–0010 closed catalog UI, graph UI, pytest, network federation | -| 2026-06-15 | REUSE-WP-0011 closed priority 17; hub live at reuse.coulomb.social | -| 2026-06-15 | Post-WP-0011 refresh: 20 capabilities, vector D5/A4/C4/R3, priorities 18–23 proposed | -| 2026-06-15 | REUSE-WP-0012 proposed; assessment archived in `history/2026-06-15-intent-scope-assessment.md` | -| 2026-06-16 | REUSE-WP-0012 closed priorities 19–23; priority 18 deferred on sibling index blocks; vector C5 | -| 2026-06-17 | REUSE-WP-0013 closed priority 24; establish/update/stats + optional llm-connect assist | -| 2026-06-16 | REUSE-WP-0014 closed priority 18; 60 workstation repos; roster + federation compose | \ No newline at end of file +| 2026-06-15 | Initial analysis after REUSE-WP-0002 | +| 2026-06-15 | WP-0003–0011 progress; vector milestones | +| 2026-06-16 | WP-0012 closed priorities 19–23 | +| 2026-06-17 | WP-0013 closed priority 24 | +| 2026-06-16 | WP-0014 closed priority 18; 60 workstation repos | +| 2026-06-16 | **SCOPE refresh + full INTENT success-criteria mapping**; priorities 25–27 proposed | \ No newline at end of file