From 81bfb037123d97287c024fdab407404253233a1a Mon Sep 17 00:00:00 2001 From: Meta Vens Date: Mon, 19 Oct 2026 20:11:10 +0200 Subject: [PATCH] route-continuity-target invariant 5: the continuity yields to a deployment awaiting the handover Co-Authored-By: Claude Opus 5.5 --- docs/route-continuity-target.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/route-continuity-target.md b/docs/route-continuity-target.md index c4d3bc8..c014a2a 100644 --- a/docs/route-continuity-target.md +++ b/docs/route-continuity-target.md @@ -57,7 +57,10 @@ web app and service through Idunn v2. The live evidence is on Yggdrasil: incumbent. A continuity past its deadline is left to the operator (operator-required incident) and retries its phase forward on a capped backoff, because aborting it would stop the only running copy of the admitted - body (ruling post-fence-forward-retry). A stateful deployment is left to the + body (ruling post-fence-forward-retry), until a deployment awaits the + handover of its target: then it yields through its own post-fencing abort, + and the deployment fences what is admitted (ruling + continuity-yields-to-deploy). A stateful deployment is left to the operator. 6. **The admitted receipt describes the running incarnation.** Continuity commits update the admitted generation atomically, so the rollback path never