coulomb/core-hub
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
core-hub/docs/deployment/stabilization-signoff.md
tegwick 7a95a8345c
Some checks failed
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / pytest-smoke (push) Failing after 2s
Details
Build and Publish Container Image / build-and-push (push) Successful in 19s
Details
docs: prepare core-hub archive closeout
2026-08-21 21:23:57 +02:00

2.5 KiB
Raw Permalink Blame History

hub-core production stabilization

This is the stabilization and closeout gate for CORE-WP-0010-T05 after hub-core replaced Core Hub as the public production runtime.

Window

  • Start: 2026-08-21T20:49:50+02:00
  • Earliest closeout: 2026-08-28T20:49:50+02:00
  • Public endpoint: https://hub.coulomb.social
  • Production package: rapp-core-hub chart 0.4.0, Helm revision 20 at start
  • Rollback: Core Hub remains Ready with no writer groups

The July Core Hub/Inter-Hub activities in activity-definitions/ are retained as historical evidence. They must not be treated as the schedule for this window. Current fleet-side observation is owned by activity-core under ACTIVITY-WP-0029; this repository's manual gate is authoritative for archive closeout until that projection is confirmed.

Daily/manual gate

Run from this repository:

make stabilization-check

The command fails closed unless all of the following pass:

  • public health reports runtime version 0.2.0;
  • readiness identifies hub-core, production PostgreSQL, database and authorization health, all four candidate writer groups, and no legacy writer group;
  • the public widget-type contract has at least 26 entries;
  • an unauthenticated protected request returns 401;
  • the ops-hub public consumer gate passes; and
  • the deployment package verifies both immutable workloads, routing, writer ownership, credential metadata, policies, and authentication.

The protected deployed smoke is optional because it needs an approved token file. If it is used, the value must remain outside Git, State Hub, logs, and chat.

Closeout gate

After the earliest closeout time, require all of these before archive:

  1. The manual stabilization gate passes.
  2. The activity-core resolver/evidence path passes against the public host.
  3. No unexplained data, contract, authorization, or writer-ownership drift is open.
  4. The final source/target comparison or retained reverse-export evidence has matching counts, identities, and canonical hashes.
  5. The runtime/database credential rotation observations in RAPP-POSTGRES-WP-0004-T03 and RAILIANCE-WP-0023-T02 are resolved or carry an explicit live residual owner.
  6. The operator approves rollback retirement and repository archive.

Record the decision and final progress against workplan f5a90aa2-e63f-4f94-b052-8be0d0ee55ea, task 16525001-f85e-4dae-9dc4-d36cb1eb4fbe.

The complete procedure and residual ownership map are in docs/deployment/archive-closeout.md.