coulomb/core-hub
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
core-hub/STATE.md
tegwick 4a2d4fa981
Some checks failed
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / pytest-smoke (push) Failing after 3s
Details
docs: align absorption plan with hub-core
2026-08-21 10:59:39 +02:00

3.7 KiB
Raw Blame History

STATE — core-hub

Updated: 2026-08-21
Domain: infotech · Repo: core-hub · Owner: codex

One-line posture

Core Hub is the verified production /api/v2 runtime on railiance01; the joint hub-core absorption plan is recorded, and Slice 0 waits on a published hub-core runtime with durable PostgreSQL storage.

Production truth

Surface Current state
Public endpoint https://hub.coulomb.social → 92.205.62.239
Runtime railiance01, Helm revision 4, chart 0.3.2
Package rapp-core-hub, verified and bound to reef-railiance
Image Forgejo digest sha256:0db6f7c646c6d4c1fbc844dc266fcf883584637e1c1f47802efe1c6a98558d3c
Database railiance01 platform-pg, database core_hub, schema core_hub
TLS Let's Encrypt certificate Ready through 2026-11-18
Consumers ops-hub gate and activity-core resolver/evidence sink verified
Source fallback CoulombCore production and staging Deployments at zero replicas; source DB read-only

The relocation and retirement evidence is in docs/evidence/core-hub-railiance01-stabilization-2026-08-21.md. Deployment packaging and rollout truth lives in the rapp-core-hub repository.

Workplans

Workplan Status Result / next gate
CORE-WP-0001–CORE-WP-0009 finished / archived Gen3 runtime, contracts, persistence, consumer gates, and hardening delivered
CORE-WP-0011 finished Production relocated to railiance01 and active CoulombCore runtime retired
CORE-WP-0010 blocked Dual-run design done; Slice 0 publication/storage gates remain

Open work

Task Status Dependency
CORE-WP-0010-T01 inventory done Inventory recorded in docs/specs/runtime-absorption-inventory.md
CORE-WP-0010-T02 dual-run design done Route-group plan recorded in docs/specs/runtime-absorption-plan.md
CORE-WP-0010-T03 absorption slices wait Published hub-core revision/image, durable backend, candidate deployment
CORE-WP-0010-T04 production cutover wait Absorption evidence and operator approval
CORE-WP-0010-T05 archive wait Cutover complete and residual ownership recorded

Intent position

The operational reset promised by INTENT.md is real: the service is small, containerized, contract-tested, credential-safe, observable, and deployed on ordinary Kubernetes/PostgreSQL infrastructure. The larger Gen3 product intent is only partly realized. Core Hub does not yet own the fleet's messaging, progress/work projections, durable decision/deployment/outcome resources, or a single extension runtime. Those gaps are not a reason to disturb the healthy production runtime; they are inputs to the hub-core consolidation decision.

Verify

make test
make lint
curl -fsS https://hub.coulomb.social/healthz
curl -fsS https://hub.coulomb.social/readyz

Known conditions

  • CORE-WP-0011 is finished but has no State Hub UUID; the registrar warning is retained rather than inventing an identifier.
  • .custodian-brief.md is generated and may lag file-backed workplan truth.
  • Hub-core T01–T06 are complete in its workplan and State Hub, but Slice 0 must pin a committed source revision and immutable image before implementation.
  • make lint currently reports seven baseline style findings in unchanged Python files (two import-order findings and five long lines); make test passes all 24 tests.
  • The stopped CoulombCore workloads and read-only source database are retained only as controlled fallback evidence.
  • Do not archive this repository before CORE-WP-0010 completes.