reuse-surface/registry/capabilities/capability.registry.register.md

id, name, summary, owner, status, domain, tags, maturity, external_evidence, discovery, availability, relations, evidence, consumer_guidance

id	name	summary	owner	status	domain	tags	maturity	external_evidence	discovery	availability	relations	evidence	consumer_guidance
capability.registry.register	Capability Registration	Register a new capability so it becomes visible for planning and implementation reuse.	reuse-surface	draft	helix_forge	registry governance meta	discovery availability current target confidence rationale D3 D5 medium Core use case UC-RS-001 is documented in specs/UseCaseCatalog.md and the registry model is bounded in INTENT.md, but concrete promotion workflows are not yet grounded in registry artifacts. current target confidence rationale A0 A3 medium Registration is currently manual through Markdown entries and the index. A CLI validator/query tool would raise availability to A3.	completeness reliability level name confidence basis satisfied_expectations broken_expectations out_of_scope_expectations C1 Fragmentary low scope_vs_intent_and_consumer_expectations capability IDs can be assigned in registry entries maturity vectors can be recorded at registration time no automated duplicate detection yet no promotion history tracking yet hosting registered capabilities enforcing implementation architecture level confidence basis known_reliability_risks R0 low consumer_quality_signals registry consistency depends on manual index maintenance	intent includes excludes assumptions use_cases research_memos Make a capability candidate visible in the registry so humans and agents can discover, assess, compare, and reuse it instead of rebuilding it in isolation. stable capability ID assignment initial discovery and availability classification explicit completeness and reliability placeholders evidence and relation references implementing the registered capability certifying implementation quality operating runtime services for registered capabilities unregistered capabilities are invisible for registry-driven reuse low-maturity entries are acceptable when evidence gaps are explicit UC-RS-001 specs/UseCaseCatalog.md specs/ProductRequirementsDocument.md	current_level target_level current_artifacts target_artifacts consumption_modes A0 A3 templates/capability-entry.template.md registry/indexes/capabilities.yaml tools/validate-registry tools/query-registry informational markdown authoring	depends_on supports related_to capability.feature-control.evaluate capability.identity.vocabulary-canonicalize capability.registry.validate	documentation tests consumer_feedback bug_reports incidents INTENT.md specs/UseCaseCatalog.md	recommended_for not_recommended_for known_limitations making a new capability visible at D0/A0/C0/R0 with minimal friction seeding planning discussions before implementation exists treating registry presence as proof of implementation readiness skipping explicit evidence for maturity promotion manual index updates are required after adding an entry duplicate detection is guidance-only in the MVP

Capability Registration

Overview

Registration is the entry point for reuse visibility. A capability that is not registered cannot be discovered through the registry surface, even if code or documentation exists elsewhere.

Current reuse mode

Humans and agents add Markdown entries under registry/capabilities/ and update registry/indexes/capabilities.yaml. This is informational reuse (A0): read, plan, and author entries.

Next promotion steps

1. Attach concrete use cases and actors to reach D5.
2. Add a CLI validator to reach A3.
3. Record consumer expectations and broken expectations as external evidence.