From 3bb90da11cb25c90eced7efc866022e7edebb3c3 Mon Sep 17 00:00:00 2001 From: codex Date: Mon, 27 Jul 2026 03:55:04 +0000 Subject: [PATCH] docs(prd): require cleanup execution integrity --- docs/prds/0082-authoritative-failure-boundaries.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/docs/prds/0082-authoritative-failure-boundaries.md b/docs/prds/0082-authoritative-failure-boundaries.md index d615668b..4d3429ac 100644 --- a/docs/prds/0082-authoritative-failure-boundaries.md +++ b/docs/prds/0082-authoritative-failure-boundaries.md @@ -45,6 +45,12 @@ misleading behavior: 8. Firecracker artifact downloads and registry publication have no network deadline, so an unresponsive registry can hold setup or release work indefinitely. +9. Authenticated secret blobs select the unauthenticated legacy decoder when + their in-band version prefix is changed, allowing storage tampering to + bypass tag verification. +10. Cleanup executes the entire post-confirmation snapshot rather than the + intersection with what the operator saw, and mutation failures are not + reflected in the command result. These are one design problem: state used to authorize deletion, replacement, or resource allocation must be authoritative at the point of use. @@ -73,6 +79,12 @@ or resource allocation must be authoritative at the point of use. as completion while preserving diagnostics for unexpected failures. - Artifact pull, existence-check, and publication requests use explicit network deadlines. +- Persisted secrets accept only the authenticated format. The schema migration + intentionally clears legacy rows; local agents are reprovisioned rather + than retaining a ciphertext-controlled downgrade path. +- Cleanup executes only resources present in both the displayed and current + authoritative plans, attempts every approved mutation, and returns failure + when any mutation does not complete. - Unit tests cover PID/path reuse, partial backend enumeration, transient policy resolution failure, slow bodies, concurrency saturation, and stream closure races. @@ -146,6 +158,8 @@ reported through the supervisor's normal diagnostic channel. 7. Gateway shutdown log-pump closure handling. 8. Lossless Firecracker process identities, authoritative Docker cleanup queries, and bounded Firecracker artifact transfers. +9. Mandatory authenticated secret storage, shared cleanup-plan intersection + and mutation accounting, and contained Git backend process failures. ## Open questions