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

id	name	summary	owner	status	domain	tags	maturity	external_evidence	discovery	availability	relations	evidence	consumer_guidance	promotion_history
capability.registry.validate	Capability registry validation	Schema, index consistency and relation checks.	reuse-surface	draft	helix_forge	registry validation cli security netkingdom framework-reuse	discovery availability current target confidence rationale D4 D5 medium UC-RS-023 is implemented via reuse-surface validate with schema and drift checks. current target confidence rationale A3 A3 high Source interface assessed 2026-10-14: Schema, index consistency and relation checks. Availability describes the delivery form, not production acceptance. Schema validity alone proves neither capability behavior nor hosted freshness.	completeness reliability level name confidence basis satisfied_expectations broken_expectations out_of_scope_expectations C3 Functional Core medium scope_vs_intent_and_consumer_expectations schema validation for entry front matter index drift detection optional relation integrity checks runtime validation of registered capability implementations level name confidence basis known_reliability_risks evidence R3 Usable medium consumer_quality_signals requires local venv install relation warnings require explicit --relations flag satisfied_signals validate --relations --fail-on-warnings in CI tests/test_registry.py schema and drift coverage	intent includes excludes use_cases research_memos Schema, index consistency and relation checks Schema, index consistency and relation checks Schema validity alone proves neither capability behavior nor hosted freshness UC-RS-023 U01: Architect composes a security deployment from explicit owner contracts and case types U14: Framework adopter validates and reuses selected contracts, tools and reference compositions specs/UseCaseCatalog.md	current_level target_level current_artifacts consumption_modes A3 A3 docs/RegistryFederation.md schemas/capability.schema.yaml library CLI	depends_on supports related_to capability.registry.register capability.registry.register capability.security.iam-tooling-suite	documentation tests consumer_feedback docs/RegistryFederation.md schemas/capability.schema.yaml tests/test_registry.py reuse-surface CI: registry changes fail when schema validation or relation checks warn with --fail-on-warnings, giving agents a dependable pre-merge gate.	recommended_for not_recommended_for known_limitations Architect composes a security deployment from explicit owner contracts and case types Framework adopter validates and reuses selected contracts, tools and reference compositions Schema validity alone proves neither capability behavior nor hosted freshness Schema validity alone proves neither capability behavior nor hosted freshness 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-16 reliability R2 R3 CI fail-on-warnings and pytest registry coverage support dependable validation. reuse-surface

Capability registry validation

Schema, index consistency and relation checks.

Reuse boundary

Schema validity alone proves neither capability behavior nor hosted freshness.

Supported use cases

• U01: Architect composes a security deployment from explicit owner contracts and case types
• U14: Framework adopter validates and reuses selected contracts, tools and reference compositions

Evidence and integration

• docs/RegistryFederation.md
• schemas/capability.schema.yaml

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.