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

docs: record hub-core production cutover
Some checks failed
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / pytest-smoke (push) Failing after 1s
Details

Browse source
This commit is contained in:
tegwick 2026-08-21 21:07:09 +02:00
parent 6d6611fa69
commit f97b793af8
5 changed files with 142 additions and 65 deletions
Download patch file Download diff file Expand all files Collapse all files

39
INTENT.md
View file

@ -38,36 +38,35 @@ The framework must be usable by humans and agents. Human operators need a stable
## Ecosystem position
`core-hub` is the **production framework layer** in the three-repo hub stack:
`core-hub` is the **previous production service and temporary rollback** in the
three-repo hub stack:
| Repo | Role |
| --- | --- |
| `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 |
| `core-hub` | Previous production service retained through cutover stabilization |
Canon: `/home/worsch/the-custodian/docs/hub-ecosystem-architecture.md`
**Transition naming:** `core-hub` remains the current production service and
rollback authority while `hub-core` becomes the surviving framework/runtime.
**Transition naming:** `hub-core` is the production service and surviving
framework/runtime. `core-hub` is the tested rollback until archive.
## Current State
Core Hub is the verified production `/api/v2` runtime at
`hub.coulomb.social`, now running on railiance01 through the `rapp-core-hub`
package. The 2026-08-21 relocation preserved the public contract and durable
data, reverified ops-hub and activity-core consumers, and retired the active
CoulombCore runtimes and obsolete tunnel. Haskell Inter-Hub remains retired
(`CORE-WP-0007`).
Hub-core is the verified production `/api/v2` runtime at
`hub.coulomb.social`, running on railiance01 through the `rapp-core-hub`
package. The 2026-08-21 cutover preserved the public contract and exact durable
data, reverified ops-hub and activity-core consumers, enforced one writer per
group, and exercised rollback to Core Hub plus forward recovery. Core Hub is
still deployed with no writer groups through the seven-day stabilization
window; the active CoulombCore runtimes and obsolete tunnel remain retired.
Haskell Inter-Hub remains retired (`CORE-WP-0007`).
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. Hub-core's packaging, contract, port, and conformance
foundations are complete, and the joint route-group migration design is
recorded. Hub-core revision `7e1ec03` publishes that foundation, so S0 is
active: durable PostgreSQL storage, legacy auth/health compatibility, an
immutable image, and an internal candidate deployment come next. The healthy
service remains the production and rollback authority until dual-run consumer
gates prove a replacement. See `STATE.md` for current operational truth.
intent. Fleet development coordination remains in state-hub; progress/work
projections and several durable evidence, decision, deployment, and outcome
resources are still external or only partially represented. `CORE-WP-0010`
now tracks only stabilization, residual-owner handoff, and read-only archive.
Hub-core revision `055cf49` is the production implementation. See `STATE.md`
for current operational truth.