amadan
spec: zero-downtime deploys rev 13 accepted by Astra (round 13)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2 files changed,
+15
−1
docs/superpowers/specs/2026-10-07-zero-downtime-deploys-design.md+6 −1docs/superpowers/specs/CODEX-FINDINGS-ZERO-DOWNTIME-R13.md+9 −0
CI passed — run details
diff --git a/docs/superpowers/specs/2026-10-07-zero-downtime-deploys-design.md b/docs/superpowers/specs/2026-10-07-zero-downtime-deploys-design.md| index 8f1cff8b3..d00b1e02f 100644 |
| --- a/docs/superpowers/specs/2026-10-07-zero-downtime-deploys-design.md |
| +++ b/docs/superpowers/specs/2026-10-07-zero-downtime-deploys-design.md |
| @@ -1,6 +1,6 @@ |
| # Zero-downtime deploys: overlap swaps and paced rollout |
| -Status: draft rev 13, 2026-10-07. Discussions #231 (deploy pickup) and #230 |
| +Status: rev 13, 2026-10-07. **Accepted by Astra in round 13** (`CODEX-FINDINGS-ZERO-DOWNTIME-R13.md`). Awaiting Paul's review. Discussions #231 (deploy pickup) and #230 |
| (per-app restart pace, first-route health step) feed into this. Astra |
| rejected rev 1 with 17 findings, rev 2 with 12 new ones, rev 3 with 7, rev 4 |
| with 3 and rev 5 with 4. The findings files are |
| @@ -1075,3 +1075,8 @@ answer for each. |
| |---|---------|--------| |
| | 1 | Retained mode overrides a later app-level `hold` | §4.2, §8.5: the release's own demand is retained, not the effective mode; recovery is `hold` if either that or the current app policy says so | |
| | 2 | Mandatory `hostguard.With` breaks claims-off boxes | §7.4: checks go through `hostwrite`, with explicit claims-off and claims-on paths; a failed claims-on check never falls through to the claims-off path | |
| + |
| +### Round 13 |
| + |
| +ACCEPT. Both round-12 findings are closed, no earlier finding reopened, |
| +and there are no new findings. |
diff --git a/docs/superpowers/specs/CODEX-FINDINGS-ZERO-DOWNTIME-R13.md b/docs/superpowers/specs/CODEX-FINDINGS-ZERO-DOWNTIME-R13.md| new file mode 100644 |
| index 000000000..ce0bb7d8c |
| --- /dev/null |
| +++ b/docs/superpowers/specs/CODEX-FINDINGS-ZERO-DOWNTIME-R13.md |
| @@ -0,0 +1,9 @@ |
| +ACCEPT |
| + |
| +R12-1: **CLOSED** — §§4.2 and 8.5 retain the release’s own demand and combine it with current app policy for recovery. This covers replacements that reread configuration at [internal/activator/backend_exec.go:849](/home/paulca/amadan.net/carlos/platform-design-zero-downtime-deploys/internal/activator/backend_exec.go:849). |
| + |
| +R12-2: **CLOSED** — §7.4 explicitly separates claims-off admission from claims-on validation, matching [internal/hostwrite/write.go:33](/home/paulca/amadan.net/carlos/platform-design-zero-downtime-deploys/internal/hostwrite/write.go:33), without permitting fallback after failed claim validation. |
| + |
| +No earlier in-scope CLOSED finding reopened: fallback without repointing, channel-installed failure holds, cold-sleeper recovery, `GoodVersion` versus `PrevVersion`, and stage-trigger retransmission remain covered. |
| + |
| +No new in-scope findings meeting the requested concrete-failure threshold. |
| \ No newline at end of file |