coulomb/the-custodian
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Refresh stabilization checkpoint after Core Hub reset

Browse Source
This commit is contained in:
Bernd Worsch
2026-06-27 23:06:15 +02:00
parent d03ddcd9fb
commit 225f3a7834
2 changed files with 39 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files

31
workplans/CUST-WP-0051-infrastructure-stabilization-metaplan.md
View File

@@ -438,16 +438,20 @@ mega-hub pattern.
Recommended order:
1. Finish identity foundations: NK-WP-0001, NK-WP-0002, then the IAM profile
integration test.
2. Create the standalone ops-hub repo from hub-core and ingest the inventory
artifacts from `CUST-WP-0047`.
3. Add ops models, MCP tools, Railiance integration, dev-hub coupling, dashboard,
and MCP registration.
4. Only then start the fin-hub/business-model tasks.
1. Keep `CUST-WP-0025-T03` as the remaining identity integration gate, targeting
the current IAM Profile v0.2 contract and local-identity or KeyCape issuer.
2. Execute the rewritten Core Hub Phase 3 lane: ops evidence contract/read-model
gaps, deployed Core Hub smoke, activity-core Core Hub sink smoke,
migration/cutover readiness, and whynot-aligned first UI screens.
3. Keep `CUST-WP-0047-T05` and `CUST-WP-0049-T06` as legacy/fallback Inter-Hub
records until deployed Core Hub evidence or an explicit supersede decision
closes them.
4. Start fin-hub/business-model tasks only after identity and Core Hub ops-hub
evidence are proven enough to demonstrate the multi-hub pattern.
Done when `CUST-WP-0025` has no open foundational identity or ops-hub tasks and
fin-hub work is either started on a stable scaffold or deliberately deferred.
fin-hub work is either started on a stable Core Hub pattern or deliberately
deferred with a dated condition.
Progress 2026-06-27:
@@ -473,6 +477,17 @@ Progress 2026-06-27 Core Hub reset:
dual-run smokes, cutover evidence, and Haskell retirement approval remain
open.
Progress 2026-06-27 CUST-WP-0052 closeout:
- `CUST-WP-0052` is finished. It closed the Core Hub reframe, rewrote
`CUST-WP-0025-T13` through `T19`, aligned the build/release lane with
HelixForge/Railiance Forge practice, and posted non-secret State Hub
requirements to `railiance-apps` and `railiance-forge`.
- The remaining T07 gates are execution gates, not sequencing ambiguity:
`CUST-WP-0025-T03` identity integration, `T14` Core Hub ops evidence contract
gaps, `T16/T17` deployed evidence/cutover waits, and `T18` Core Hub operator
UI first screens.
## Task: Create The Stable Pickup Checkpoint
```task