coulomb/reuse-surface
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Complete REUSE-WP-0003: registry CLI, docs alignment, and coverage

Browse Source 
Align INTENT.md with delivered layout, add CapabilityRegistryConcept guide,
extend schema with promotion_history, ship reuse-surface validate/query/export
CLI, register three more helix_forge capabilities, and refresh SCOPE and gap
analysis to reflect A3 tooling and D5/A3/C4/R2 self-assessment.
This commit is contained in:
Bernd Worsch
2026-06-15 01:12:09 +02:00
parent 80bccc4bbb
commit 0dbef6d1a3
20 changed files with 1051 additions and 165 deletions
Download Patch File Download Diff File Expand all files Collapse all files

54
docs/IntentScopeGapAnalysis.md
View File

@@ -13,25 +13,21 @@ current delivered scope so future workplans can close them deliberately.
`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 actually delivers today:
an MVP registry foundation at **A0 availability** with manual, Markdown-first
workflows.
implementation. `SCOPE.md` describes what the repository actually delivers today: an MVP registry
with **A3 CLI tooling** (`validate`, `query`, `export`) atop Markdown-first
authoring.
The two documents are **directionally aligned** on registry-first reuse, four
maturity dimensions, and human/agent consumers. The main gaps are:
maturity dimensions, and human/agent consumers. REUSE-WP-0003 closed the
priority gaps from section 8. Remaining gaps are primarily scale, automation,
and presentation concerns:
1. **Delivery depth** — INTENT promises eventual technical foundation and broad
planning/implementation support; SCOPE delivers informational tooling only.
2. **Structural drift** — INTENT's expected repository layout and entry shape
differ from the implemented layout and schema in small but important ways.
3. **Evidence and operations** — INTENT emphasizes consumer evidence and
progress tracking; SCOPE has no reliability evidence, promotion history, or
automated validation yet.
4. **Document cross-coverage** — SCOPE operationalizes State Hub, MVP acceptance
criteria, and helix_forge domain context that INTENT does not mention; INTENT
carries success criteria and conceptual depth that SCOPE does not restate.
1. **Planning analytics** — no gap reports, overlap detection, or catalog site.
2. **Reliability depth** — registry product dogfood evidence is early (R2).
3. **Document cross-coverage** — SCOPE still carries operational detail INTENT
omits; INTENT success criteria are not fully enumerated in SCOPE.
**Current reuse-surface vector (self-assessment):** `D4 / A0 / C3 / R0`
**Current reuse-surface vector (self-assessment):** `D5 / A3 / C4 / R2`
---
@@ -256,18 +252,25 @@ own evidence (e.g. feature-control at R3).
## 8. Priority Gap Closure Order
Recommended sequence for future workplans:
| Priority | Gap | Outcome | Status |
|---|---|---|---|
| 1 | INTENT layout stale | INTENT layout aligned to delivered structure | Closed (WP-0003) |
| 2 | No automated validation | `reuse-surface validate` | Closed (WP-0003) |
| 3 | Thin registry coverage | Six helix_forge entries | Closed (WP-0003) |
| 4 | Missing concept docs | `docs/CapabilityRegistryConcept.md` | Closed (WP-0003) |
| 5 | No promotion history | `promotion_history` in schema/template | Closed (WP-0003) |
| 6 | Search/filter manual only | `reuse-surface query` | Closed (WP-0003) |
| 7 | No registry export | `reuse-surface export` | Closed (WP-0003) |
| 8 | Self-reliability evidence | `capability.registry.register` at R2; friction recorded | Closed (WP-0003) |
### Next recommended work
| Priority | Gap | Suggested outcome |
|---|---|---|
| 1 | INTENT layout stale | Update INTENT "Initial Repository Role" to match `SCOPE.md` layout |
| 2 | No automated validation | CLI or script: validate entries against schema |
| 3 | Thin registry coverage | Register additional helix_forge capabilities beyond 3 samples |
| 4 | Missing concept docs | Add `docs/CapabilityRegistryConcept.md` distilled from INTENT |
| 5 | No promotion history | Add `promotion_history` to schema or separate changelog |
| 6 | Search/filter manual only | CLI `query` with discovery/availability filters |
| 7 | No registry export | YAML/JSON bundle export for agents (UC-RS-019) |
| 8 | Self-reliability evidence | Dogfood registry; record friction as reliability evidence |
| 9 | Catalog site | Static browsable capability catalog (UC-RS-018) |
| 10 | Overlap detection | CLI or report for duplicate/overlapping capabilities |
| 11 | CI validation | Run `reuse-surface validate` in CI on registry changes |
| 12 | Registry federation | Cross-repo capability index composition |
---
@@ -285,4 +288,5 @@ Recommended sequence for future workplans:
| Date | Change |
|---|---|
| 2026-06-15 | Initial analysis after REUSE-WP-0002 completion |
| 2026-06-15 | Initial analysis after REUSE-WP-0002 completion |
| 2026-06-15 | REUSE-WP-0003 closed priority gaps 1–8; vector updated to D5/A3/C4/R2 |