ops-hub/registry/capabilities/capability.operations.ops-hub.md

id	name	summary	owner	status	domain	tags	maturity	external_evidence	discovery	availability	relations	evidence	consumer_guidance	promotion_history
capability.operations.ops-hub	Operations Hub Extension Contract	Versioned hub-extension package and bootstrap client for operational truth, service-catalog records, readiness evidence, and migration gates.	ops-hub	reviewed	operations	operations service-catalog readiness hub-extension	discovery availability current target confidence rationale D3 D4 high The owner boundary, versioned descriptor/manifest, hub-core ports, event families, compatibility bootstrap, and State Hub retirement handoff are explicit and tested. current target confidence rationale A1 A3 high The contract package and idempotent bootstrap client are available from source; the framework runtime is hosted by hub-core rather than this repo.	completeness reliability level confidence basis satisfied_expectations broken_expectations out_of_scope_expectations C1 medium scope_vs_intent_and_consumer_expectations versioned extension descriptor and manifest hub-core schema and event-catalog validation disposable Tier 2/3 conformance profile production compatibility API public gate independent framework runtime secret custody level confidence basis known_reliability_risks R1 high consumer_quality_signals authenticated re-bootstrap requires the attended high-risk access lane	intent includes excludes assumptions use_cases research_memos Let hub-core host an Ops Hub extension without transferring ownership of operational records or credentials into the framework. descriptor and capability manifest operations service-catalog declaration readiness evidence event boundary compatibility bootstrap client and public gate hub-core framework implementation credential storage or vending State Hub compatibility routes after cutover hub-core remains the surviving framework runtime register Ops Hub against hub-core publish and project service-catalog records attach non-secret readiness evidence	current_level target_level current_artifacts target_artifacts consumption_modes A1 A3 registry/hub-extension/v0.1.0/ops-hub.extension.json scripts/ops-hub-bootstrap-api.py scripts/hub-extension-check.py scripts/hub-core-conformance.py policy-bound unattended registration lane contract package command-line bootstrap	depends_on supports related_to capability.infotech.hub-core-library capability.operations.service-catalog	documentation tests consumer_feedback bug_reports incidents docs/hub-extension.md docs/bootstrap-runbook.md tests/test_extension_contract.py make hub-core-conformance RAPPCOREHUB-WP-0002-T04	recommended_for not_recommended_for known_limitations registering and validating the Ops Hub extension on hub-core migrating State Hub service-catalog consumers to an owner-backed contract treating ops-hub as another hub-core runtime retrieving or storing credentials C2, C7, C9, and C10 are not automated by hub-core contract version 0.1.0 authenticated live bootstrap requires the governed attended access lane	date dimension from to rationale author 2026-08-31 discovery D0 D3 Published the owner-side 0.1.0 package and conformance evidence. codex date dimension from to rationale author 2026-08-31 availability A0 A1 Published source-level validation and bootstrap consumers. codex

Operations Hub Extension Contract

The capability is the owner-side contract package and bootstrap client. Hub Core supplies the framework runtime; Ops Hub retains the operational vocabulary, service-catalog model, readiness evidence, and migration-gate ownership.

The package contains no credentials. Authenticated bootstrap follows docs/bootstrap-runbook.md and emits only non-secret identifiers and key prefixes as evidence.