54 lines
2.1 KiB
Markdown
54 lines
2.1 KiB
Markdown
# SCOPE
|
|
|
|
> Boundary for agents and contributors working in Core Hub.
|
|
|
|
## One-Liner
|
|
|
|
Core Hub is the 3rd-generation production interaction framework for Coulomb / Helixforge.
|
|
|
|
## Core Idea
|
|
|
|
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
|
|
- 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
|
|
- Evidence-preserving maintenance of the completed Inter-Hub migration and
|
|
Haskell/IHP retirement record
|
|
|
|
## Out of Scope
|
|
|
|
- Continuing to act as a generic repo template
|
|
- Owning every downstream domain hub implementation
|
|
- Storing or vending secrets directly
|
|
- Rewriting unrelated consumers before the Core Hub compatibility contract exists
|
|
- Reintroducing the retired Inter-Hub runtime as an active production path
|
|
|
|
## Ecosystem position
|
|
|
|
| Repo | Boundary |
|
|
| --- | --- |
|
|
| `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 |
|
|
|
|
See `/home/worsch/the-custodian/docs/hub-ecosystem-architecture.md`.
|
|
|
|
## Non-Goals
|
|
|
|
- Recreate IHP abstractions in Python
|
|
- 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
|