generated from coulomb/repo-seed
Complete REUSE-WP-0003: registry CLI, docs alignment, and coverage
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:
@@ -74,7 +74,8 @@ Definitions live in `specs/CapabilityMaturityStandard.md`.
|
||||
|
||||
### UC-RS-004 — Search by planning need
|
||||
|
||||
1. Read `indexes/capabilities.yaml` and scan `summary`, `tags`, and `vector`.
|
||||
1. Run `reuse-surface query --discovery-min D4` or read the index and scan
|
||||
`summary`, `tags`, and `vector`.
|
||||
2. Open candidate entries and review `discovery.intent`, `discovery.use_cases`,
|
||||
and `discovery.includes`.
|
||||
3. Prefer entries with discovery `D3+` for roadmap work and `D5+` for MVP
|
||||
@@ -131,6 +132,8 @@ or `generalizes` rather than creating silent duplicates.
|
||||
1. Attach evidence appropriate to the target level in
|
||||
`specs/CapabilityMaturityStandard.md`.
|
||||
2. Update `maturity` and/or `external_evidence` with rationale and confidence.
|
||||
3. Update `availability.current_artifacts` when a new consumption mode appears.
|
||||
4. Refresh the index `vector` and run the validation checklist.
|
||||
5. Set `status: reviewed` or `approved` when an assessor validates the entry.
|
||||
3. Append a `promotion_history` record with `date`, `dimension`, `from`, `to`,
|
||||
and `rationale` (optional `author`).
|
||||
4. Update `availability.current_artifacts` when a new consumption mode appears.
|
||||
5. Refresh the index `vector` and run `reuse-surface validate`.
|
||||
6. Set `status: reviewed` or `approved` when an assessor validates the entry.
|
||||
Reference in New Issue
Block a user