implement ops hub extension contract

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a053ff-1d6f-7fe2-ac1c-a6eb40a42a0c

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

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