tegwick
bf2b8f08ce
T01 executed and disproved the workplan's own first draft. core-hub's archive shows CORE-WP-0005 closed the production cutover gates on 2026-07-03 and CORE-WP-0007 retired the Haskell/IHP infrastructure by 2026-07-08, with a stabilization window and explicit operator approval to retire the Inter-Hub rollback deployment. The 0/0 Deployment on railiance01 is that rollback standby at its designed end state, not a lapse. The surviving finding is sharper and more urgent: hub.coulomb.social resolves to 92.205.130.254 — CoulombCore — so Core Hub's production runtime, in service since July, sits on the host being decommissioned, with no core-hub presence on railiance01 and hub-core still a package rather than a service. The workplan is retitled and re-centred on that. DECISIONS.md records the correction and why it generalises: the live documents described a retirement that had already happened while the completed evidence sat in an archived workplan, so a reader checking current files reaches the wrong conclusion. That requirement applies directly to the State Hub retirement this project is planning. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
1.7 KiB
1.7 KiB
Work Records — prj-state-hub-retirement
Generated by
statehub fix-consistency(CUST-WP-0061-T04, work-record stage 3). Do not edit by hand — edit the source file/block listed for each record and re-run fix-consistency to refresh this index. Archived workplans are omitted; closed decisions/intakes/engagements stay listed so recently-resolved work is still visible. [auto]
| Kind | ID | Status | Lane | Source |
|---|---|---|---|---|
| workplan | SHR-WP-0001 | finished | — | workplans/SHR-WP-0001-foundation.md |
| workplan | SHR-WP-0002 | proposed | — | workplans/SHR-WP-0002-predecessor-and-deployment-reality.md |
| task | SHR-WP-0001-T01 | done | — | workplans/SHR-WP-0001-foundation.md |
| task | SHR-WP-0001-T02 | done | — | workplans/SHR-WP-0001-foundation.md |
| task | SHR-WP-0001-T03 | done | — | workplans/SHR-WP-0001-foundation.md |
| task | SHR-WP-0001-T04 | done | — | workplans/SHR-WP-0001-foundation.md |
| task | SHR-WP-0001-T05 | done | — | workplans/SHR-WP-0001-foundation.md |
| task | SHR-WP-0001-T06 | done | — | workplans/SHR-WP-0001-foundation.md |
| task | SHR-WP-0002-T01 | todo | — | workplans/SHR-WP-0002-predecessor-and-deployment-reality.md |
| task | SHR-WP-0002-T02 | todo | — | workplans/SHR-WP-0002-predecessor-and-deployment-reality.md |
| task | SHR-WP-0002-T03 | todo | — | workplans/SHR-WP-0002-predecessor-and-deployment-reality.md |
| task | SHR-WP-0002-T04 | todo | — | workplans/SHR-WP-0002-predecessor-and-deployment-reality.md |
| task | SHR-WP-0002-T05 | todo | — | workplans/SHR-WP-0002-predecessor-and-deployment-reality.md |
| task | SHR-WP-0002-T06 | todo | — | workplans/SHR-WP-0002-predecessor-and-deployment-reality.md |