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

Advance CUST-WP-0025: close T16/T17, add canon and fin-hub bootstrap

Browse Source 
- Mark T16/T17 done with cutover evidence and decision coupling doc
- Add business-model-canvas and bootstrap-protocol canon (T20/T21)
- Record Core Hub readiness-summary evidence stubs
- Refresh fos-hub-bootstrap-sequence-status and core-hub-replacement-evidence
This commit is contained in:
codex
2026-07-08 00:50:28 +02:00
parent 72fe10e076
commit a272f5fcda
11 changed files with 582 additions and 39 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
docs/core-hub-replacement-evidence.md
View File

@@ -35,24 +35,20 @@ old Inter-Hub-first ops-hub path:
compact whynot-aligned first-screen backlog. The UI should not start by
recreating every old Inter-Hub screen.
No live deployed smoke report was available in this session. Therefore there
are no deployed Core Hub smoke ids/counts to claim yet. The next live report
should record only non-secret fields: `runId`, hub id/slug/status, manifest
id/status, API consumer id/status/key prefix, widget count, interaction event
id/type, and hub-registry containment booleans.
**2026-07-02/03 update:** Deployed evidence now exists. Staging smoke
`20260702143544-6c8f18`, production smoke `20260702235645-59bf1e`, activity-core
sink event `ae43db56-902d-411a-a495-25acd464fdd8`, and migration import (28
records, idempotent) are documented in `docs/evidence/` and aggregated via
`readiness-summary` (`readyForCutover: true` on 2026-07-08).
## 0047 And 0049 Decision
`CUST-WP-0047-T05` should remain `wait` as the legacy Inter-Hub evidence record.
Do not close it from local Core Hub evidence alone. It can close later through a
Core Hub deployed compatibility/evidence smoke or an explicit supersede
decision that states the legacy production widget activation is no longer
required.
**Superseded 2026-07-03:** `CUST-WP-0047-T05` and `CUST-WP-0049-T06` are
cancelled in their workplans. Core Hub production cutover plus deployed smoke
evidence replaced the legacy Inter-Hub widget activation and bootstrap access
lane. Inter-Hub remains rollback-only through `CORE-WP-0007` stabilization.
`CUST-WP-0049-T06` should remain `wait` as the legacy/fallback access routine.
Do not request Inter-Hub operator keys or new ops-warden work for the preferred
replacement lane. Use it only if the operator deliberately chooses legacy
Inter-Hub bootstrap or rollback validation.
See `docs/core-hub-cutover-decision-coupling.md` for the full decision record.
## CUST-WP-0025 Phase 3 Reset Recommendation