docs: refresh SCOPE and INTENT↔SCOPE gap analysis post WP-0014
SCOPE.md reflects 60-repo rollout, federation compose metrics, and open publish/dedup blockers. IntentScopeGapAnalysis maps INTENT success criteria to delivery and proposes priorities 25–27.
This commit is contained in:
parent
41d11b3c57
commit
834abb80f7
3 changed files with 162 additions and 158 deletions
|
|
@ -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
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue