reuse-surface/SCOPE.md

SCOPE

One-liner

Capability registry for planning and implementation reuse based on discovery and delivery maturity.

Core Idea

reuse-surface provides a registry-centric reuse layer for capabilities. It makes capabilities visible, comparable, assessable, and reusable for planning, implementation, and operation. A capability that is not registered is invisible for reuse within this product boundary.

In Scope

• Maintain the capability maturity model, standards, schemas, registry formats, examples, indexes, validation guidance, and agent instructions.
• Keep INTENT.md, specs/, registry artifacts, and State Hub workplans aligned on the registry-first reuse boundary.
• Support humans and agents as registry consumers through Markdown-first authoring and machine-readable metadata.
• Record decisions, progress, and workplan status through State Hub.
• Verify changes with documentation review, git diff --check, and ADR-001 consistency checks.

Out of Scope

• Host or operate the registered capabilities themselves.
• Replace package registries, service catalogs, issue trackers, or project management systems.
• Judge internal code quality as capability maturity.
• Own unrelated adjacent systems or make irreversible operational decisions without human approval.

Current State

• Status: active specification scaffold.
• The repository is currently documentation-only. It has no package manifest, build system, runtime app, or executable test suite.
• specs/ contains the product requirements, use case catalog, and capability maturity standard. INTENT.md defines the registry model and guiding principles.
• registry/, schemas/, templates/, and tools/ contain the MVP registry foundation seeded by REUSE-WP-0002.

Getting Oriented

• Start with: INTENT.md
• Product requirements: specs/ProductRequirementsDocument.md
• Use cases: specs/UseCaseCatalog.md
• Maturity standard: specs/CapabilityMaturityStandard.md
• Agent instructions: AGENTS.md
• Workplans: workplans/