From 8f0667d8ff855f9ca80dea84aadf4a1c4b488342 Mon Sep 17 00:00:00 2001 From: tegwick Date: Mon, 31 Aug 2026 20:07:51 +0200 Subject: [PATCH] close rename plan and restate retirement gates Assistant: codex Assistant-Model: gpt-5.6-sol Assistant-Session: 01a053ff-1d6f-7fe2-ac1c-a6eb40a42a0c --- WORK-RECORDS.md | 12 ++--- docs/retirement-cutover-slice-plan.md | 21 +++++++++ .../STATE-WP-0079-retirement-strangler.md | 45 ++++++++++++++++--- ...85-repository-lineage-preserving-rename.md | 34 +++++++++++--- 4 files changed, 95 insertions(+), 17 deletions(-) diff --git a/WORK-RECORDS.md b/WORK-RECORDS.md index f2c3c88..03a1b93 100644 --- a/WORK-RECORDS.md +++ b/WORK-RECORDS.md @@ -50,13 +50,13 @@ | workplan | STATE-WP-0076 | finished | — | workplans/STATE-WP-0076-definition-of-ready-and-comprehension.md | | workplan | STATE-WP-0077 | finished | — | workplans/STATE-WP-0077-dox-assessment-recording-and-soft-visibility.md | | workplan | STATE-WP-0078 | finished | — | workplans/STATE-WP-0078-ops-run-read-projection.md | -| workplan | STATE-WP-0079 | active | — | workplans/STATE-WP-0079-retirement-strangler.md | +| workplan | STATE-WP-0079 | blocked | — | workplans/STATE-WP-0079-retirement-strangler.md | | workplan | STATE-WP-0080 | finished | — | workplans/STATE-WP-0080-register-project-flavor-awareness.md | | workplan | STATE-WP-0081 | proposed | — | workplans/STATE-WP-0081-cluster-self-sufficiency-and-registrar.md | | workplan | STATE-WP-0082 | finished | — | workplans/STATE-WP-0082-multi-owner-review-contracts-and-receipts.md | | workplan | STATE-WP-0083 | finished | — | workplans/STATE-WP-0083-forge-derived-projection-reset.md | | workplan | STATE-WP-0084 | finished | — | workplans/STATE-WP-0084-forge-read-for-private-repositories.md | -| workplan | STATE-WP-0085 | active | — | workplans/STATE-WP-0085-repository-lineage-preserving-rename.md | +| workplan | STATE-WP-0085 | finished | — | workplans/STATE-WP-0085-repository-lineage-preserving-rename.md | | workplan | STATE-WP-0086 | finished | — | workplans/STATE-WP-0086-fast-forge-projection-reconcile.md | | task | STATE-WP-ADHOC-2026-06-04-T01 | done | — | workplans/ADHOC-2026-06-04.md | | task | STATE-WP-ADHOC-2026-07-01-T01 | done | — | workplans/ADHOC-2026-07-01.md | @@ -288,9 +288,9 @@ | task | STATE-WP-0079-T01 | done | — | workplans/STATE-WP-0079-retirement-strangler.md | | task | STATE-WP-0079-T02 | done | — | workplans/STATE-WP-0079-retirement-strangler.md | | task | STATE-WP-0079-T03 | done | — | workplans/STATE-WP-0079-retirement-strangler.md | -| task | STATE-WP-0079-T04 | progress | — | workplans/STATE-WP-0079-retirement-strangler.md | -| task | STATE-WP-0079-T05 | progress | — | workplans/STATE-WP-0079-retirement-strangler.md | -| task | STATE-WP-0079-T06 | todo | — | workplans/STATE-WP-0079-retirement-strangler.md | +| task | STATE-WP-0079-T04 | wait | — | workplans/STATE-WP-0079-retirement-strangler.md | +| task | STATE-WP-0079-T05 | wait | — | workplans/STATE-WP-0079-retirement-strangler.md | +| task | STATE-WP-0079-T06 | wait | — | workplans/STATE-WP-0079-retirement-strangler.md | | task | STATE-WP-0080-T01 | done | — | workplans/STATE-WP-0080-register-project-flavor-awareness.md | | task | STATE-WP-0080-T02 | done | — | workplans/STATE-WP-0080-register-project-flavor-awareness.md | | task | STATE-WP-0080-T03 | done | — | workplans/STATE-WP-0080-register-project-flavor-awareness.md | @@ -333,7 +333,7 @@ | task | STATE-WP-0085-T06 | done | — | workplans/STATE-WP-0085-repository-lineage-preserving-rename.md | | task | STATE-WP-0085-T07 | done | — | workplans/STATE-WP-0085-repository-lineage-preserving-rename.md | | task | STATE-WP-0085-T08 | done | — | workplans/STATE-WP-0085-repository-lineage-preserving-rename.md | -| task | STATE-WP-0085-T09 | wait | — | workplans/STATE-WP-0085-repository-lineage-preserving-rename.md | +| task | STATE-WP-0085-T09 | done | — | workplans/STATE-WP-0085-repository-lineage-preserving-rename.md | | task | STATE-WP-0086-T01 | done | — | workplans/STATE-WP-0086-fast-forge-projection-reconcile.md | | task | STATE-WP-0086-T02 | done | — | workplans/STATE-WP-0086-fast-forge-projection-reconcile.md | | task | STATE-WP-0086-T03 | done | — | workplans/STATE-WP-0086-fast-forge-projection-reconcile.md | diff --git a/docs/retirement-cutover-slice-plan.md b/docs/retirement-cutover-slice-plan.md index 35de3b1..3f8bcd4 100644 --- a/docs/retirement-cutover-slice-plan.md +++ b/docs/retirement-cutover-slice-plan.md @@ -80,6 +80,27 @@ would be new permanent ownership in the component being retired, which `repo-manager` workplan; RMGR-WP-0004 (standards conformance) and RMGR-WP-0005 (registrar consolidation) do not cover them. +### Owner readiness refresh (2026-08-31) + +The original readiness table is retained above as planning history. Current +workplan status changes which owners can receive a slice, but it does not count +as State Hub cutover evidence by itself: + +| Owner | Current owner evidence | State Hub cutover consequence | +| --- | --- | --- | +| `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. | +| `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. | + +Accordingly, `STATE-WP-0079-T04` is waiting on the missing owner workplans, +the still-unrecorded State Hub route-switch receipts, and explicit production +writer-cutover authorization. `T05` waits on fresh central meter evidence, and +`T06` cannot begin while State Hub remains the healthy, active `railiance01` +primary. + ## Adapter mechanism Wave A reuses the dual-run strangler proven in RMGR-WP-0002/0003 rather than diff --git a/workplans/STATE-WP-0079-retirement-strangler.md b/workplans/STATE-WP-0079-retirement-strangler.md index d091af6..663c01d 100644 --- a/workplans/STATE-WP-0079-retirement-strangler.md +++ b/workplans/STATE-WP-0079-retirement-strangler.md @@ -4,7 +4,7 @@ type: workplan title: "State Hub retirement strangler and disposition execution" domain: infotech repo: state-hub -status: active +status: blocked owner: codex topic_slug: infotech created: "2026-08-09" @@ -116,7 +116,7 @@ registration suite passes (`20 passed`). ```task id: STATE-WP-0079-T04 -status: progress +status: wait priority: high state_hub_task_id: "3a454438-1955-547f-a491-8eab7cd25710" ``` @@ -365,11 +365,31 @@ the daily filename unchanged. A regression test covers the filename/id pairing. This prevents new collisions without making State Hub the long-term convention owner. +**Owner-gate reconciliation 2026-08-31.** The previously open receiving-side +gates have advanced materially: RMGR-WP-0005 finished the deterministic +identifier migration, HUB-WP-0005 put all hub-core route and writer groups into +production ownership with exercised rollback, and ACTIVITY-WP-0029 finished +the schedule, consistency-sweep, interaction-event, and execution-boundary +handoffs. Those are durable owner records and no longer block this task. + +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. + ## Retire legacy surfaces ```task id: STATE-WP-0079-T05 -status: progress +status: wait priority: medium state_hub_task_id: "f6cf8c01-eb59-5ca8-a541-23928d4a000c" ``` @@ -459,13 +479,21 @@ live SBOM callers, live `GET /tasks/?workstream_id`, the three high-volume workstream reads still inside their 60-day quiet window, and two workstream mutations still inside 30 days. Evidence: `docs/evidence/legacy-meter-weekly-review-20260831.json`. T05 remains -`progress`; T06 must not start. +`wait`; T06 must not start. + +The nine held interfaces are explicitly owned by this task until the meter +allows retirement; they are not untracked prose residuals. Three SBOM reads and +`GET /tasks/?workstream_id` still had calls in the seven-day review window. +Three high-volume workstream reads have only 9 of 60 required quiet days, while +the two workstream mutations have 14/30 and 15/30 quiet days. A future review +must recapture central-primary evidence and apply the existing volume ladder; +calendar passage alone is not retirement evidence. ## Stabilization window and archive prep ```task id: STATE-WP-0079-T06 -status: todo +status: wait priority: high state_hub_task_id: "9230c99b-af58-5794-9291-452e619a30fa" ``` @@ -473,6 +501,13 @@ state_hub_task_id: "9230c99b-af58-5794-9291-452e619a30fa" With T06 gates: zero normal read/write window, final dump, backup/restore evidence, stop service, archive repo read-only. Residuals → live owners. +**Blocked 2026-08-31.** The sole `railiance01` primary is healthy and remains +the active coordination service, the legacy meter has live callers, and T04 +still has owner-side cutovers. A freeze, final dump/restore rehearsal, service +stop, or repository archive would therefore interrupt normal work and destroy +the evidence needed by T05. T06 remains `wait` until T04 and T05 are done and a +fresh central meter demonstrates the required zero normal read/write window. + ## Acceptance - [x] Freeze policy documented diff --git a/workplans/STATE-WP-0085-repository-lineage-preserving-rename.md b/workplans/STATE-WP-0085-repository-lineage-preserving-rename.md index e83003c..03907af 100644 --- a/workplans/STATE-WP-0085-repository-lineage-preserving-rename.md +++ b/workplans/STATE-WP-0085-repository-lineage-preserving-rename.md @@ -4,7 +4,7 @@ type: workplan title: "Lineage-preserving repository rename workflow and adoption-plan generator" domain: infotech repo: state-hub -status: active +status: finished owner: codex topic_slug: infotech created: "2026-08-28" @@ -15,6 +15,14 @@ reviewed_against_commit: "41d80429a77ffeb640f4b34091ebee5c91585373" quality_dor: DoR-Ok quality_dor_at: "2026-08-28" quality_dor_by: codex +quality_dod: DoD-Ok +quality_dod_at: "2026-08-31" +quality_dod_by: codex +quality_dod_note: >- + The generic capability, recovery contract, operator documentation, and + target-workplan generator are tested and deployed. FLEX-WP-0020 is committed, + pushed, registered, DoR-Ok, and retains the signing and human approval gates + for the deliberately out-of-scope live rename. related: - CUST-ADR-012 - STATE-WP-0083 @@ -565,7 +573,7 @@ one existing async cancellation warning remain outside T08. ```task id: STATE-WP-0085-T09 -status: wait +status: done priority: high state_hub_task_id: "df34f6ec-d137-52d0-93c4-3756a821097f" ``` @@ -605,8 +613,8 @@ committed, and registered proposed plan `FLEX-WP-0020` / State Hub UUID `99a661a8-b36c-5c1c-b78b-1e8930bcd0a9` (`flex-auth` commits `8d61ac9` and `8ea8644`). The plan is deliberately repository-only, names every reviewed verification owner, retains runtime/product `flex-auth` surfaces, and preserves -the human cutover gate. T09 remains in progress because live preflight correctly -reports `preflight_signing_unavailable`; provisioning was handed to +the human cutover gate. At that point T09 was held because live preflight +correctly reported `preflight_signing_unavailable`; provisioning was handed to `railiance-platform` in message `cd52ba10-de41-46ce-aa8b-9b44050da8f7`. No Forgejo rename, State Hub rebind, clone removal, consumer edit, or runtime deployment was performed. @@ -615,8 +623,22 @@ deployment was performed. registered, `proposed`, and DoR-Ok. The deployed State Hub still has no repository-rename preflight signing configuration, and platform handoff `cd52ba10-de41-46ce-aa8b-9b44050da8f7` remains unread. This is an external -provisioning gate, so the task is `wait`, not active implementation. No rename -or consumer mutation was performed. +provisioning gate for the later live cutover, so the task was held at `wait` +while its completion boundary was checked. No rename or consumer mutation was +performed. + +**Completed 2026-08-31.** T09 ends at the reviewed repository-owned adoption +plan, not at an executable live-rename token. `FLEX-WP-0020` is clean and +pushed at `8ea8644`, registered as State Hub workplan +`99a661a8-b36c-5c1c-b78b-1e8930bcd0a9`, and records DoR-Ok plus the explicit +human cutover gate. Its captured preflight proves the existing State Hub UUID, +Forge repository ID `42`, and matching local/origin/Forge source commit. The +missing signing configuration remains a fail-closed prerequisite of +`FLEX-WP-0020-T05` and the platform handoff above; it is not a prerequisite for +generating or reviewing the plan. Moving it into this workplan's completion +gate would incorrectly make an out-of-scope live-rename prerequisite part of +the generator delivery. No State Hub, Forgejo, checkout, deployment, or +consumer mutation was performed during closeout. ## Workplan completion