Answer A-207: the runner's recoveries state; widens from revision and grants-for

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 09:41:28 +01:00
parent 18ecf1c47f
commit 456a1eae45
1 changed files with 6 additions and 0 deletions
@@ -109,3 +109,9 @@ the principle that settles it, cited as "design 47 G A-n".
  `ask-again`, its tool `runner_release`; the bound's expiry writes the finding `pipeline-waits` (scope `module`, id
  `<branch>.<id>.<module>`); the wait's `on` gains the value `runner version`; its `clock-from` is the `build.ended`
  of the awaited fingerprint, heard as A-181 says.
+- **A-207** (§86, §81, §415, §71, §275, §335, §441; principles 1, 2 and 7) The runner keeps a state `recoveries`
+  (commit to why) written when it hears the mesh-delivery seat's `recovery-merged`, read at a pipeline's start and
+  resume; a recovery heard after its pipeline started asks nothing again. `widens` is computed from two reads: the
+  catalog seat's `revision` of the candidate against the branch's newest (the serving parts' entries and fingerprints,
+  found by holder from the seat list; the acting rules `step`, `on` and `bound` and the credentials the entries
+  declare), and the grants part's `grants-for` (the permissions); no other verb.