coulomb/core-hub
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

feat: prepare Core Hub production relocation
Some checks failed
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / pytest-smoke (push) Failing after 1s
Details
Build and Publish Container Image / build-and-push (push) Successful in 1m3s
Details

Browse source
This commit is contained in:
tegwick 2026-08-20 22:46:41 +02:00
parent d7627dabf5
commit 881c87905f
7 changed files with 230 additions and 17 deletions
Download patch file Download diff file Expand all files Collapse all files

20
SCOPE.md
View file

@ -8,17 +8,23 @@ Core Hub is the 3rd-generation production interaction framework for Coulomb / He
## Core Idea
Core Hub replaces the Haskell/IHP Inter-Hub implementation with a contract-first Python/FastAPI/Postgres framework for cross-domain state, agent coordination, evidence, registry facts, workplans, and operator interaction surfaces.
Core Hub is the contract-first Python/FastAPI/Postgres framework that replaced
the Haskell/IHP Inter-Hub implementation for cross-domain state, agent
coordination, evidence, registry facts, workplans, and operator interaction
surfaces.
## In Scope
- Core Hub intent, research, specs, and implementation workplans
- Contract/IR definition for hubs, manifests, widgets, events, tasks, progress, messages, decisions, and registry facts
- FastAPI/Postgres implementation planning and eventual service code
- Inter-Hub `/api/v2` compatibility where existing consumers depend on it
- Data migration and production cutover planning from Inter-Hub
- Maintaining the production `/api/v2` compatibility contract inherited from
Inter-Hub
- Relocating the current Core Hub runtime across production hosts without
coupling continuity to future framework consolidation
- Operator UI and whynot-design aligned component/adaptor planning
- Haskell/IHP retirement planning after replacement evidence exists
- Evidence-preserving maintenance of the completed Inter-Hub migration and
Haskell/IHP retirement record
## Out of Scope
@ -26,13 +32,13 @@ Core Hub replaces the Haskell/IHP Inter-Hub implementation with a contract-first
- Owning every downstream domain hub implementation
- Storing or vending secrets directly
- Rewriting unrelated consumers before the Core Hub compatibility contract exists
- Retiring production Inter-Hub before migration and smoke evidence exists
- Reintroducing the retired Inter-Hub runtime as an active production path
## Ecosystem position
| Repo | Boundary |
| --- | --- |
| `hub-core` | Library — core-hub imports utils; framework models stay in `core_hub` |
| `hub-core` | Shared library today; any permanent host is an explicit future architecture decision |
| `state-hub` | Dev coordination canonical owner for workplans/tasks until ADR says otherwise |
| `core-hub` | This repo — `/api/v2`, framework tables, operator console |
@ -44,3 +50,5 @@ See `/home/worsch/the-custodian/docs/hub-ecosystem-architecture.md`.
- Bind the UI contract to React or any single frontend framework
- Make State Hub disappear before Core Hub proves a compatible replacement path
- Duplicating hub-core router factories or dev-hub workplan tables locally
- Making the unresolved hub-core library-vs-thin-host decision merely to meet
a host-decommission deadline