From f7eb5bfd1fdc0c4ed85fe1293b02bb682be0767a Mon Sep 17 00:00:00 2001 From: tegwick Date: Fri, 4 Sep 2026 21:40:46 +0200 Subject: [PATCH] docs: rebaseline predecessor deployment workplan Assistant: codex Assistant-Model: gpt-5.6-sol Assistant-Session: 01a06d83-1cbc-71f2-b0dc-e0f48cedae43 --- ...0002-predecessor-and-deployment-reality.md | 47 ++++++++++++++----- 1 file changed, 36 insertions(+), 11 deletions(-) diff --git a/workplans/SHR-WP-0002-predecessor-and-deployment-reality.md b/workplans/SHR-WP-0002-predecessor-and-deployment-reality.md index 1ed8168..5a6760e 100644 --- a/workplans/SHR-WP-0002-predecessor-and-deployment-reality.md +++ b/workplans/SHR-WP-0002-predecessor-and-deployment-reality.md @@ -4,11 +4,11 @@ type: workplan title: "Generation 3 serves from the host being decommissioned" domain: infotech repo: prj-state-hub-retirement -status: proposed -owner: unassigned +status: active +owner: codex topic_slug: state-hub-retirement created: "2026-08-20" -updated: "2026-08-20" +updated: "2026-09-04" state_hub_workstream_id: "53f42c0c-3a35-53b0-99c8-8eaee7b17354" --- @@ -43,6 +43,15 @@ The lesson is the opposite of the one first drafted: **generation 2 was retired well.** What nobody checked was whether the successor's runtime was standing on durable ground. +## Re-baseline — 2026-09-04 + +The immediate runtime risk has been resolved. `CORE-WP-0011` moved Core Hub to +railiance01, its tasks are complete, and the project decision record documents +the corrected generation-2 history and the CoulombCore exit. The project must +still finish the cross-generation inventory and guardrails: the generation-2 +disposition file and repository-reality ledger do not yet exist, `G-GEN` has not +been adopted, and live legacy package/access references remain. + ## What was observed, 2026-08-20 | Generation | Position | Observed | @@ -86,7 +95,7 @@ identifier. ```task id: SHR-WP-0002-T01 -status: todo +status: done priority: high state_hub_task_id: "8c54ea9b-8a92-55bc-80ce-8425678f3efe" ``` @@ -96,10 +105,8 @@ production cutover gates on 2026-07-03; `CORE-WP-0007` retired the Haskell/IHP infrastructure by 2026-07-08 with operator approval and a stabilization window. The `0/0` rollback deployment is the designed end state. -Remaining sub-task: record this in `DECISIONS.md` **with the correction**, so -the project's own record shows that the first reading was wrong and why. A -retirement project that misreads a completed retirement as an attrition should -keep the evidence trail for the next reader. +**Completed 2026-09-04.** `DECISIONS.md` records the correction and its evidence, +so the project's own record shows that the first reading was wrong and why. ```task id: SHR-WP-0002-T02 @@ -124,7 +131,7 @@ estate intended to have, does not have, and has not decided to do without. ```task id: SHR-WP-0002-T03 -status: todo +status: done priority: high state_hub_task_id: "06119690-312f-5d14-aee0-2fc4dac1e89e" ``` @@ -177,6 +184,12 @@ Eleven days. See `DECISIONS.md`. On that constraint the project recommends the interim move — an architecture decision plus a production migration inside eleven days is not a plan. The choice remains core-hub's. +**Completed 2026-09-04.** Core Hub chose and completed the interim move under +`CORE-WP-0011`. Production now runs on railiance01, the CoulombCore Deployments +were scaled to zero after stabilization, and the sequence and disposition are +recorded in `DECISIONS.md`. `CORE-WP-0010` remains historical context, not the +vehicle that ultimately resolved this task. + ```task id: SHR-WP-0002-T04 status: todo @@ -196,7 +209,7 @@ files from here — the project's authority is the ledger, not the prose. ```task id: SHR-WP-0002-T05 -status: todo +status: progress priority: medium state_hub_task_id: "c2957182-4bb3-5aa9-9940-656956cfe52d" ``` @@ -216,6 +229,11 @@ jobs whose subject is a retired or lapsed generation. Route retirements to owner record the sweep here so the next generation change has a checklist rather than a memory. +**Progress 2026-09-04.** The sweep has enumerated SSH, registry, credential, and +runner lanes, but closure is incomplete. In particular, +`inter-hub-bootstrap-ssh` remains an active high-risk catalog lane and needs an +owner decision rather than silent deletion. + ```task id: SHR-WP-0002-T06 status: todo @@ -236,7 +254,7 @@ decision route rather than adding it unilaterally. ```task id: SHR-WP-0002-T07 -status: todo +status: progress priority: high state_hub_task_id: "a89cf85d-d613-5434-92cb-11f850889b08" ``` @@ -252,6 +270,13 @@ Nothing breaks on decommission day, because running pods already hold their images. It breaks at the next restart, reschedule or scale-up, as `ImagePullBackOff`. +**Progress update 2026-09-04.** `REUSE-WP-0020` and `KAIZEN-WP-0010` are +finished, and Core Hub has moved. Closure is still blocked by live legacy +surfaces: the `whynot-design-npm-publish` lane targets the old npm registry, +`issue-core` retains its legacy Gitea PyPI upload target, and the platform ArgoCD +bootstrap allow-list still admits Gitea repositories. Route and verify those +residuals before marking this task done. + **The two are not equally urgent** (corrected 2026-08-20 after checking each reference's liveness):