| capability.infotech.core-hub |
Core Hub Production Interaction Framework |
Contract-first framework for cross-domain state, agent coordination, evidence, registries, workplans, and operator interaction surfaces. |
core-hub |
draft |
infotech |
| interaction-framework |
| state-hub |
| inter-hub-successor |
| agent-coordination |
| registry |
| api |
|
| discovery |
availability |
| current |
target |
confidence |
rationale |
| D3 |
D5 |
medium |
Intent, scope, lineage research, and initial specs are documented. Detailed API and data contracts are planned but not yet implemented.
|
|
| current |
target |
confidence |
rationale |
| A1 |
A5 |
medium |
The repo is currently a planning/specification home. Production availability starts after the FastAPI/Postgres implementation, migration, and cutover workplans land.
|
|
|
| completeness |
reliability |
| level |
confidence |
basis |
satisfied_expectations |
broken_expectations |
out_of_scope_expectations |
| C1 |
medium |
initial_spec_seed |
| intent and scope documents |
| lineage and platform reset research artifact |
| specification map |
| staged workplans |
|
| runtime implementation is not yet present |
| compatibility test harness is not yet present |
|
| direct secret custody |
| owning every downstream domain hub implementation |
|
|
| level |
confidence |
basis |
known_reliability_risks |
| R1 |
medium |
no_runtime_yet |
| 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 |
|
|
|
| intent |
includes |
excludes |
assumptions |
use_cases |
research_memos |
| 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.
|
| 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 |
|
| direct credential vending |
| unrelated downstream app runtimes |
| retiring Inter-Hub before compatible replacement evidence exists |
|
| 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 |
|
| publish domain hub manifests and capabilities |
| emit interaction and evidence events |
| coordinate agent-visible workplans and progress |
| expose operator console surfaces |
|
| docs/research/2026-06-27-core-hub-lineage-and-platform-reset.md |
|
|
| current_level |
target_level |
current_artifacts |
consumption_modes |
| A1 |
A5 |
| INTENT.md |
| SCOPE.md |
| docs/specs/README.md |
| workplans/ |
|
|
|
| depends_on |
supports |
related_to |
| capability.statehub.workstream-coordinate |
|
| capability.registry.register |
|
| capability.inter-hub.framework |
| capability.whynot-design.system |
|
|
| documentation |
tests |
| INTENT.md |
| SCOPE.md |
| docs/research/2026-06-27-core-hub-lineage-and-platform-reset.md |
| docs/specs/README.md |
|
|
|
| recommended_for |
not_recommended_for |
known_limitations |
| planning new domain hub integrations |
| replacing Inter-Hub Haskell/IHP consumers through a compatibility layer |
| centralizing agent/operator interaction contracts |
|
| production cutover before compatibility and migration evidence exists |
| secret custody or credential handoff flows |
|
| implementation is not yet present |
| compatibility contract is seeded but not frozen |
|
|