Set up Core Hub framework planning

registry/README.md

@@ -1,12 +1,12 @@
 # Capability Registry
 
-Markdown-first capability index for federation and reuse planning.
+Markdown-first capability index for Core Hub federation and reuse planning.
+
+Core Hub publishes its framework capability here so reuse-surface and related discovery tools can understand what this repo is meant to provide.
 
 ## Authoring
 
-1. Copy a capability entry template (see reuse-surface `templates/capability-entry.template.md`).
-2. Add the row to `indexes/capabilities.yaml`.
-3. Run `reuse-surface validate` from a checkout with the CLI installed.
-4. Merge to `main` and verify publish with `reuse-surface establish --publish-check`.
-
-Federation contract: reuse-surface `docs/RegistryFederation.md`.
+1. Add or update a capability entry under `registry/capabilities/`.
+2. Add the row to `registry/indexes/capabilities.yaml`.
+3. Run `reuse-surface validate --root .` from a checkout with the CLI installed.
+4. Keep capability docs aligned with `INTENT.md`, `SCOPE.md`, and `docs/specs/`.

registry/capabilities/capability.infotech.core-hub.md

@@ -0,0 +1,128 @@
+---
+id: capability.infotech.core-hub
+name: Core Hub Production Interaction Framework
+summary: Contract-first framework for cross-domain state, agent coordination, evidence, registries, workplans, and operator interaction surfaces.
+owner: core-hub
+status: draft
+domain: infotech
+tags:
+  - interaction-framework
+  - state-hub
+  - inter-hub-successor
+  - agent-coordination
+  - registry
+  - api
+
+maturity:
+  discovery:
+    current: D3
+    target: D5
+    confidence: medium
+    rationale: >
+      Intent, scope, lineage research, and initial specs are documented. Detailed
+      API and data contracts are planned but not yet implemented.
+  availability:
+    current: A1
+    target: A5
+    confidence: medium
+    rationale: >
+      The repo is currently a planning/specification home. Production availability
+      starts after the FastAPI/Postgres implementation, migration, and cutover workplans land.
+
+external_evidence:
+  completeness:
+    level: C1
+    confidence: medium
+    basis: initial_spec_seed
+    satisfied_expectations:
+      - intent and scope documents
+      - lineage and platform reset research artifact
+      - specification map
+      - staged workplans
+    broken_expectations:
+      - runtime implementation is not yet present
+      - compatibility test harness is not yet present
+    out_of_scope_expectations:
+      - direct secret custody
+      - owning every downstream domain hub implementation
+  reliability:
+    level: R1
+    confidence: medium
+    basis: no_runtime_yet
+    known_reliability_risks:
+      - Inter-Hub compatibility must be proven before cutover
+      - data migration and API auth semantics require careful operator evidence
+      - Haskell retirement must wait until replacement runtime is live
+
+discovery:
+  intent: >
+    Provide the third-generation production interaction substrate for Coulomb,
+    preserving the valuable State Hub and Inter-Hub semantics while replacing the
+    Haskell/IHP implementation path with a lighter contract-first platform.
+  includes:
+    - framework contract and IR documentation
+    - API and event model specs
+    - workplan, progress, task, message, and decision coordination model
+    - operator UI and component surface planning
+    - migration and compatibility planning
+  excludes:
+    - direct credential vending
+    - unrelated downstream app runtimes
+    - retiring Inter-Hub before compatible replacement evidence exists
+  assumptions:
+    - existing consumers can tolerate stable `/api/v2` compatibility during transition
+    - State Hub remains available while Core Hub is built
+    - workplans remain canonical in repo files until Core Hub intentionally changes that model
+  use_cases:
+    - publish domain hub manifests and capabilities
+    - emit interaction and evidence events
+    - coordinate agent-visible workplans and progress
+    - expose operator console surfaces
+  research_memos:
+    - docs/research/2026-06-27-core-hub-lineage-and-platform-reset.md
+
+availability:
+  current_level: A1
+  target_level: A5
+  current_artifacts:
+    - INTENT.md
+    - SCOPE.md
+    - docs/specs/README.md
+    - workplans/
+  consumption_modes:
+    - informational
+    - planning
+
+relations:
+  depends_on:
+    - capability.statehub.workstream-coordinate
+  supports:
+    - capability.registry.register
+  related_to:
+    - capability.inter-hub.framework
+    - capability.whynot-design.system
+
+evidence:
+  documentation:
+    - INTENT.md
+    - SCOPE.md
+    - docs/research/2026-06-27-core-hub-lineage-and-platform-reset.md
+    - docs/specs/README.md
+  tests: []
+
+consumer_guidance:
+  recommended_for:
+    - planning new domain hub integrations
+    - replacing Inter-Hub Haskell/IHP consumers through a compatibility layer
+    - centralizing agent/operator interaction contracts
+  not_recommended_for:
+    - production cutover before compatibility and migration evidence exists
+    - secret custody or credential handoff flows
+  known_limitations:
+    - implementation is not yet present
+    - compatibility contract is seeded but not frozen
+---
+
+# Core Hub Production Interaction Framework
+
+Core Hub is the third-generation interaction framework for Coulomb / Helixforge. It keeps the State Hub and Inter-Hub lessons while moving the implementation path to a practical contract-first platform.

registry/indexes/capabilities.yaml

@@ -1,14 +1,14 @@
 version: 1
-updated: '2026-06-24'
+updated: '2026-06-27'
 domain: infotech
 capabilities:
-  - id: capability.infotech.repo-template
-    name: Coulomb Repository Template
-    summary: Bootstrap new git repositories with agent instructions, registry scaffold, and State Hub onboarding conventions.
-    vector: D3 / A3 / C2 / R2
+  - id: capability.infotech.core-hub
+    name: Core Hub Production Interaction Framework
+    summary: Contract-first framework for cross-domain state, agent coordination, evidence, registries, workplans, and operator interaction surfaces.
+    vector: D3 / A1 / C1 / R1
     domain: infotech
     status: draft
-    owner: repo-seed
-    path: registry/capabilities/capability.infotech.repo-template.md
-    tags: [template, bootstrap, state-hub, onboarding]
-    consumption_modes: [git clone, informational]
+    owner: core-hub
+    path: registry/capabilities/capability.infotech.core-hub.md
+    tags: [interaction-framework, state-hub, inter-hub-successor, agent-coordination, registry, api]
+    consumption_modes: [informational, planning]