61 lines
3 KiB
Markdown
61 lines
3 KiB
Markdown
# Core Hub
|
|
|
|
Core Hub is the 3rd-generation Production Interaction Framework for Coulomb / Helixforge.
|
|
|
|
## Hub stack glossary
|
|
|
|
| Name | Role |
|
|
| --- | --- |
|
|
| **hub-core** | Production runtime and shared framework/library |
|
|
| **state-hub** | Dev coordination — file-first workplans, agent MCP |
|
|
| **core-hub** | This repo — previous `/api/v2` runtime, retained as rollback until archive |
|
|
|
|
Ecosystem architecture: `/home/worsch/the-custodian/docs/hub-ecosystem-architecture.md`
|
|
|
|
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](INTENT.md) - purpose, lineage, principles, and platform direction
|
|
- [STATE.md](STATE.md) - current production truth, open work, and known conditions
|
|
- [SCOPE.md](SCOPE.md) - repo boundary
|
|
- [Research artifact](docs/research/2026-06-27-core-hub-lineage-and-platform-reset.md) - what we learned from State Hub, Inter-Hub, Haskell/IHP, and whynot-design
|
|
- [Specs index](docs/specs/README.md) - contract and implementation specification map
|
|
- [Workplans](workplans/) - staged implementation plan using ADR-001 workplan files
|
|
|
|
## Current Work
|
|
|
|
The contract, FastAPI/Postgres foundation, Inter-Hub migration, Haskell/IHP
|
|
retirement, relocation from CoulombCore, and production absorption into
|
|
hub-core are complete. Hub-core revision `055cf49` is public authority. This
|
|
repository remains a no-writer rollback through the stabilization window
|
|
ending no earlier than 2026-08-28T20:49:50+02:00. New product work belongs in
|
|
hub-core; the only open local task is the prepared read-only archive closeout
|
|
in [`docs/deployment/archive-closeout.md`](docs/deployment/archive-closeout.md).
|
|
|
|
Operational migration bundles are emitted without raw key material:
|
|
|
|
```bash
|
|
core-hub-ops migration export --source-revision "$(git rev-parse HEAD)" \
|
|
--output core-hub-export.json
|
|
```
|
|
|
|
`CORE_HUB_V2_WRITE_GROUPS` controls legacy write authority for `registry`,
|
|
`credentials`, `interaction`, and `deferred`. The deployment package must
|
|
remove a group here before enabling the matching hub-core writer.
|