Bootstrap and first implementation

SCOPE.md

@@ -1,32 +1,53 @@
 # SCOPE
 
-> This file was generated by `statehub register`. Refine it as the repository
-> boundaries become clearer.
-
 ## One-liner
 
 Capability registry for planning and implementation reuse based on discovery and delivery maturity.
 
 ## Core Idea
 
-reuse-surface exists to provide the capability described in INTENT.md.
+`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 repository's primary implementation.
-- Keep docs, tests, and operational metadata current.
+- 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
 
-- Own unrelated adjacent systems.
-- Make irreversible operational decisions without human approval.
+- 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; implementation and stability should be verified by the repo agent.
+- 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/
+- Workplans: workplans/