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

record fabric retirement gate readiness
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a053ff-1d6f-7fe2-ac1c-a6eb40a42a0c
This commit is contained in:
tegwick 2026-08-31 22:26:51 +02:00
parent 0e35f84ad5
commit 903a2fb090
1 changed files with 18 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

26
workplans/STATE-WP-0079-retirement-strangler.md
View file

@ -385,14 +385,24 @@ post-cutover public `/api/v2` gate. Framework checks absent from contract 0.1.0
are live owner residual `HUB-WP-0009` / State Hub UUID
`0d6e94f3-fd15-5f57-af41-60f0b862da5e`; they do not return D1 ownership here.
The remaining move/replace slices are not executable in State Hub. FIN-WP-0003
is still `proposed` with all three tasks `todo` and owns the fabric authority
cutover. State Hub's freeze policy forbids implementing that owner surface
here. T04 is therefore `wait` on FIN-WP-0003, the remaining
repo-manager/hub-core/activity-core/ops-hub State Hub route-switch receipts,
and explicit authorization for any production writer cutover. It must resume
from a fresh owner-readiness and caller scan, not from the obsolete 2026-08-20
snapshot.
**D2 receiving contract completed 2026-08-31.** FIN-WP-0003 is finished with
all three tasks done. `railiance-fabric` revision `113445d` now publishes the
direct `financial-fabric-v1` authority export, deterministic accepted-snapshot
revision provenance, graph edge/summary reads, and regression coverage.
Fin-hub revisions `debe67e` / `5fe943d` publish the consumer contract and
executable schema/content-hash/count/provenance gate. Retirement-project
revision `1812170` corrects all ten Fabric items from `fin-hub/move` to
`railiance-fabric/replace`; hub-core projection is explicitly deferred.
The receiving contract is ready, but the production cutover is not. The first
gate run correctly returned no-go: the authority has 131 nodes / 117 edges,
while State Hub has 49 / 58, with a different content hash and null source
revision/path/export time. T04 therefore remains `wait` on selecting and
refreshing one authority snapshot into the dual-read window, obtaining a green
`finhub fabric-cutover-check`, recording route-switch/rollback receipts for the
remaining repo-manager/hub-core/activity-core/ops-hub families, and explicit
authorization for production writer changes. It must resume from a fresh
caller scan, not from the obsolete 2026-08-20 snapshot.
## Retire legacy surfaces