From 0e35f84ad5f2f9397d76ffacb99f9973544f08ac Mon Sep 17 00:00:00 2001 From: tegwick Date: Mon, 31 Aug 2026 21:36:46 +0200 Subject: [PATCH] record ops hub retirement gate completion Assistant: codex Assistant-Model: gpt-5.6-sol Assistant-Session: 01a053ff-1d6f-7fe2-ac1c-a6eb40a42a0c --- docs/retirement-cutover-slice-plan.md | 6 ++--- .../STATE-WP-0079-retirement-strangler.md | 25 +++++++++++++------ 2 files changed, 20 insertions(+), 11 deletions(-) diff --git a/docs/retirement-cutover-slice-plan.md b/docs/retirement-cutover-slice-plan.md index 3f8bcd4..26a4e56 100644 --- a/docs/retirement-cutover-slice-plan.md +++ b/docs/retirement-cutover-slice-plan.md @@ -91,7 +91,7 @@ as State Hub cutover evidence by itself: | `repo-manager` | RMGR-WP-0005 finished deterministic identifier migration; RMGR-WP-0008 finished register/classification surfaces | Receiving-side identity and register gates are satisfied; each State Hub writer/read switch still needs its own parity and rollback receipt. | | `hub-core` | HUB-WP-0005 finished and its production runtime owns all declared hub-core route/writer groups with exercised rollback | Receiving runtime is available; B1-B5 are not complete until State Hub caller/route switches and counts are evidenced. | | `activity-core` | ACTIVITY-WP-0029 finished schedule, sweep, interaction-event, and execution-boundary work | The launch-request defect is retired; remaining C-slice caller switches still require explicit evidence. | -| `ops-hub` | OPS-WP-0003 remains `proposed`; 0/3 tasks done | D1 cannot move. Do not implement the missing owner contract here. | +| `ops-hub` | OPS-WP-0003 finished; owner package and implemented conformance profile pass | D1 receiving-side gate is satisfied. State Hub route/caller switch, count parity, rollback, and writer authorization remain cutover evidence. | | `fin-hub` | FIN-WP-0003 remains `proposed`; 0/3 tasks done | D2 cannot move. Do not implement the fabric authority contract here. | | `archive` | 2026-08-31 central meter: 6 newly retired, 9 legacy, 0 candidates | E2/E4 remain gated; live callers and volume-scaled quiet windows prohibit retirement. | @@ -294,11 +294,11 @@ carry the contract; messaging and telemetry are write paths; UI last. Both are `replace` — schedulers move to activity-core under a different contract. C2 must follow A2, since the consistency job writes work records. -## Wave D — remaining owners (25 items) · all gated +## Wave D — remaining owners (25 items) · fin-hub gated | Slice | Owner | Capabilities | Items | Gate | | --- | --- | --- | --- | --- | -| D1 | `ops-hub` | `service-catalog` (9), `service-catalog-ui` (2) | 11 | OPS-WP-0003 `proposed` | +| D1 | `ops-hub` | `service-catalog` (9), `service-catalog-ui` (2) | 11 | OPS-WP-0003 `finished`; receiving contract ready, cutover receipt pending | | D2 | `fin-hub` | `fabric-graph` (10) | 10 | FIN-WP-0003 `proposed` | | D3 | `the-custodian` | `kaizen-agents` (2) | 2 | none — can go anytime | diff --git a/workplans/STATE-WP-0079-retirement-strangler.md b/workplans/STATE-WP-0079-retirement-strangler.md index 663c01d..2c69f01 100644 --- a/workplans/STATE-WP-0079-retirement-strangler.md +++ b/workplans/STATE-WP-0079-retirement-strangler.md @@ -376,14 +376,23 @@ They establish receiving-side readiness only. They do not, by themselves, prove that State Hub callers and route families have switched or that the required parity, rollback, and production receipts exist. -The remaining move/replace slices are not executable in State Hub. OPS-WP-0003 -is still `proposed` with all three tasks `todo`, and FIN-WP-0003 is still -`proposed` with all three tasks `todo`; they own the service-catalog and fabric -authority cutovers. State Hub's freeze policy forbids implementing those owner -surfaces here. T04 is therefore `wait` on those two live owner workplans, the -remaining hub-core/activity-core 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. +**D1 receiving contract completed 2026-08-31.** OPS-WP-0003 is finished with +all three tasks done. Ops Hub now publishes the reviewed +`capability.operations.ops-hub` and +`capability.operations.service-catalog` owner package, passes hub-core's +schemas/catalog and all eight implemented conformance checks, and passes the +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. ## Retire legacy surfaces