Core Hub

Core Hub is the 3rd-generation Production Interaction Framework for Coulomb / Helixforge.

It carries forward the lessons from State Hub and Inter-Hub: workplans and progress need to be durable, domains need typed ways to publish state and evidence, operators need a coherent console, and agents need APIs that are predictable enough to automate against. The rebuild moves that intent onto a lighter production platform.

Generations

• Gen 1: state-hub - file-backed workplans, tasks, progress, messages, and read-model synchronization.
• Gen 2: inter-hub - the integrated hub framework idea: manifests, widgets, registries, events, API consumers, and a shared UI, implemented in Haskell/IHP.
• Gen 3: core-hub - the same framework ambition rebuilt contract-first on the natural Coulomb stack.

Initial Stack Direction

• Python 3.12
• FastAPI and Pydantic v2
• SQLAlchemy async, Alembic, asyncpg, Postgres
• pytest and contract fixtures
• OpenAPI and JSON Schema for public contracts
• whynot-design aligned UI components/adapters where operator UI is needed
• Docker/Kubernetes/ArgoCD on the normal Railiance platform path

Key Documentation

• INTENT.md - purpose, lineage, principles, and platform direction
• SCOPE.md - repo boundary
• Research artifact - what we learned from State Hub, Inter-Hub, Haskell/IHP, and whynot-design
• Specs index - contract and implementation specification map
• Workplans - staged implementation plan using ADR-001 workplan files

Immediate Work

1. Freeze the Core Hub contract and IR.
2. Build the FastAPI/Postgres foundation.
3. Preserve critical Inter-Hub /api/v2 compatibility for current consumers.
4. Migrate data and cut over production traffic.
5. Retire the Haskell/IHP build lane only after replacement evidence exists.