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

docs: define hub-core absorption plan
Some checks failed
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / pytest-smoke (push) Failing after 3s
Details

Browse source
This commit is contained in:
tegwick 2026-08-21 10:57:13 +02:00
parent 5802d6f799
commit 4a9df801c3
7 changed files with 216 additions and 25 deletions
Download patch file Download diff file Expand all files Collapse all files

15
INTENT.md
View file

@ -42,13 +42,14 @@ The framework must be usable by humans and agents. Human operators need a stable
| Repo | Role |
| --- | --- |
| `hub-core` | Shared library — models, router factories, utils (`hub_core.utils`) |
| `hub-core` | Surviving framework/runtime — contracts, ports, package, and primary image |
| `state-hub` | Dev coordination — file-first workplans, dev MCP |
| `core-hub` | Production service — `/api/v2`, hubs, manifests, operator console |
Canon: `/home/worsch/the-custodian/docs/hub-ecosystem-architecture.md`
**Naming:** `core-hub` = core *framework runtime*. `hub-core` = core *primitives library*.
**Transition naming:** `core-hub` remains the current production service and
rollback authority while `hub-core` becomes the surviving framework/runtime.
## Current State
@ -63,7 +64,9 @@ This delivers the practical Gen3 production reset, but not the whole product
intent. Messaging, progress/work projections, several durable evidence and
decision resources, and a single extension runtime remain outside Core Hub or
only partially represented. `CORE-WP-0010` tracks absorption into hub-core and
repository archive; it is blocked on the runtime packaging, minimal-port, and
joint-plan decisions in `HUB-WP-0004`. The healthy service remains the
production and rollback authority until dual-run consumer gates prove a
replacement. See `STATE.md` for current operational truth.
repository archive. Hub-core's packaging, contract, port, and conformance
foundations are complete, and the joint route-group migration design is
recorded. Execution now waits on a published immutable hub-core revision, a
durable PostgreSQL backend, and an internal candidate deployment. The healthy
service remains the production and rollback authority until dual-run consumer
gates prove a replacement. See `STATE.md` for current operational truth.