reuse-surface/templates/capability-entry.template.md

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

id	name	summary	owner	status	domain	tags	maturity	external_evidence	discovery	availability	relations	evidence	consumer_guidance	promotion_history
capability.domain.example	Example Capability	One sentence describing what this capability enables.	team-or-person	draft	helix_forge	example	discovery availability current target confidence rationale D0 D5 low Explain why the current discovery level is defensible and what evidence is still missing for promotion. current target confidence rationale A0 A3 low Explain the current consumption mode and the natural target availability.	completeness reliability level confidence basis satisfied_expectations broken_expectations out_of_scope_expectations C0 low scope_vs_intent_and_consumer_expectations level confidence basis known_reliability_risks R0 low consumer_quality_signals	intent includes excludes assumptions use_cases research_memos What this capability is meant to make possible for planners and consumers. behavior that belongs inside the capability behavior explicitly outside the capability assumptions shaping the capability boundary	current_level target_level current_artifacts target_artifacts consumption_modes A0 A3 informational	depends_on supports related_to	documentation tests consumer_feedback bug_reports incidents	recommended_for not_recommended_for known_limitations describe suitable reuse scenarios describe unsafe or weak reuse scenarios list known gaps, risks, or missing evidence

Example Capability

Overview

Describe the capability in plain language for human readers. The YAML front matter above is the machine-readable source of truth for maturity, evidence, relations, and consumer guidance.

Assessment notes

Discovery

Record why the selected discovery level is defensible. Link research memos, use cases, and scope boundaries that support promotion.

Availability

Record how consumers can access the capability today and what artifact would raise availability to the target level.

Completeness

Compare declared intent, current scope, and consumer expectations. Record broken expectations explicitly rather than hiding them.

Reliability

Record consumer-relevant quality evidence. Do not confuse reliability with completeness or internal code quality.

Promotion checklist

• ID follows capability.<domain>.<name> pattern
• Maturity enums match specs/CapabilityMaturityStandard.md
• external_evidence is populated separately from maturity
• Relations reference valid capability IDs
• Index entry added or updated in registry/indexes/capabilities.yaml