docs(mesh): program tracking — Phase 1 plan already exists from the design session; surface its deploy-seal decision gate

2026-07-22 08:12:57 -04:00
parent 9af935f237
commit e7311f11a6
1 changed files with 1 additions and 1 deletions
@@ -193,7 +193,7 @@ resource sizing on the site VMs should be checked once both products run the ful
 | 0a downing strategy | DONE 2026-07-21 (live gate → Phase 7) |
 | 0b oldest-Up election | DONE 2026-07-21 |
 | Prereq: selfform-fallback + manual-failover plan | plan written 2026-07-22, not executed |
-| 1 ClusterNode columns + DB ack set | not started — plan to be written |
+| 1 ClusterNode columns + DB ack set | **detailed plan ALREADY WRITTEN** (`2026-07-21-per-cluster-mesh-phase1.md`, from the design session — do NOT write a new one), not executed. ⚠ Carries a decision gate: DB-derived expected-ack set changes deploy-seal semantics (a stopped-but-enabled node now FAILS the deploy at the apply deadline instead of sealing green without it; escape hatch = `ClusterNode.Enabled=0`) — confirm with the owner before its Task 3. |
 | 2 ClusterClient transport | not started |
 | 3 fetch-and-cache | not started |
 | 4 cut driver ConfigDb | not started |