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

docs: reconcile core hub state and intent
Some checks failed
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / pytest-smoke (push) Failing after 2s
Details

Browse source
This commit is contained in:
tegwick 2026-08-21 08:49:15 +02:00
parent a7adc40c2f
commit c7b1ebb560
7 changed files with 239 additions and 23 deletions
Download patch file Download diff file Expand all files Collapse all files

16
INTENT.md
View file

@ -52,4 +52,18 @@ Canon: `/home/worsch/the-custodian/docs/hub-ecosystem-architecture.md`
## Current State
Production serves Core Hub at `hub.coulomb.social` since 2026-07-03. Haskell Inter-Hub is retired (`CORE-WP-0007`). Ecosystem consolidation with hub-core and state-hub is tracked under `CUST-WP-0057` / `CORE-WP-0009`.
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`).
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.