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

id	name	summary	owner	status	domain	tags	maturity	external_evidence	discovery	availability	relations	evidence	consumer_guidance	promotion_history
capability.registry.register	Capability registry and federation	Owner Markdown entries, indexes, federation hub and planning queries.	reuse-surface	draft	helix_forge	registry governance meta security netkingdom framework-reuse	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 A3 A5 medium Source interface assessed 2026-10-14: Owner Markdown entries, indexes, federation hub and planning queries. Availability describes the delivery form, not production acceptance. Discovery is not readiness; empty and stale entries need evidence-led maintenance.	completeness reliability level name confidence basis satisfied_expectations broken_expectations out_of_scope_expectations C2 Partial medium scope_vs_intent_and_consumer_expectations capability IDs can be assigned in registry entries maturity vectors can be recorded at registration time CLI validate, query, and export support registry workflows promotion history can be recorded in entries federation repo registration via hosted hub API and hub CLI no automated duplicate detection yet hosting registered capabilities enforcing implementation architecture level name confidence basis known_reliability_risks evidence R3 Usable medium consumer_quality_signals index drift still possible if authors skip validate CLI requires local venv install sibling repos cannot register until indexes publish raw URLs satisfied_signals CI validate with fail-on-warnings on every push hub register/list/federated smoke on production reuse.coulomb.social pytest coverage for hub API and federation compose paths	intent includes excludes assumptions use_cases research_memos Owner Markdown entries, indexes, federation hub and planning queries Owner Markdown entries, indexes, federation hub and planning queries Discovery is not readiness; empty and stale entries need evidence-led maintenance unregistered capabilities are invisible for registry-driven reuse low-maturity entries are acceptable when evidence gaps are explicit UC-RS-001 U01: Architect composes a security deployment from explicit owner contracts and case types U09: Maintainer observes posture, prioritizes findings, coordinates work and verifies outcomes U14: Framework adopter validates and reuses selected contracts, tools and reference compositions specs/UseCaseCatalog.md specs/ProductRequirementsDocument.md	current_level target_level current_artifacts target_artifacts consumption_modes A3 A5 docs/RegistryFederation.md specs/CapabilityMaturityStandard.md packaged container release with documented SLO library CLI	depends_on supports related_to capability.feature-control.evaluate capability.identity.vocabulary-canonicalize capability.registry.validate capability.security.iam-tooling-suite	documentation tests consumer_feedback bug_reports incidents docs/RegistryFederation.md specs/CapabilityMaturityStandard.md tests/test_hub.py tests/test_hub_sync.py .forgejo/workflows/ci.yml reuse-surface dogfood (REUSE-WP-0011): production hub registration and /v1/federated compose succeeded on Railiance01 without write-path regressions after WP-0011 deploy.	recommended_for not_recommended_for known_limitations Architect composes a security deployment from explicit owner contracts and case types Maintainer observes posture, prioritizes findings, coordinates work and verifies outcomes Framework adopter validates and reuses selected contracts, tools and reference compositions Discovery is not readiness; empty and stale entries need evidence-led maintenance Discovery is not readiness; empty and stale entries need evidence-led maintenance 2026-10-14 architecture review estimates operational maturity separately; a registry entry does not authorize execution or establish deployment.	date dimension from to rationale author 2026-06-14 discovery D0 D1 Added name, summary, and registry-first intent from INTENT.md. reuse-surface date dimension from to rationale author 2026-06-15 discovery D1 D3 Bounded scope with UC-RS-001 and MVP registry artifacts in specs/. reuse-surface date dimension from to rationale author 2026-06-15 availability A0 A3 reuse-surface CLI shipped validate, query, and export commands. reuse-surface date dimension from to rationale author 2026-06-15 availability A3 A4 Hosted federation hub live at reuse.coulomb.social; hub register/update via HTTP API and reuse-surface hub CLI; production deploy on Railiance01. reuse-surface date dimension from to rationale author 2026-06-16 reliability R2 R3 CI gates, pytest hub/federation coverage, and production hub smoke support normal registration workflows with documented limitations. reuse-surface date dimension from to rationale author 2026-10-14 availability A4 A3 Interface-form reassessment from current owner sources; no completeness/reliability promotion. codex

Capability registry and federation

Owner Markdown entries, indexes, federation hub and planning queries.

Reuse boundary

Discovery is not readiness; empty and stale entries need evidence-led maintenance.

Supported use cases

• U01: Architect composes a security deployment from explicit owner contracts and case types
• U09: Maintainer observes posture, prioritizes findings, coordinates work and verifies outcomes
• U14: Framework adopter validates and reuses selected contracts, tools and reference compositions

Evidence and integration

• docs/RegistryFederation.md
• specs/CapabilityMaturityStandard.md

Assessment: CUST-WP-0081, 2026-10-14. Relations identify interfaces to compose; they do not certify native integration. Existing external evidence levels are retained where present. New entries use conservative C1/R0 until consumer assessment exists.