Answer A-155: restic's put-off wait is a bound key on the bus

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 09:41:28 +01:00
parent 79d8ec7a52
commit 95e47c2776
1 changed files with 4 additions and 0 deletions
@@ -577,3 +577,7 @@ names the principle that settles it, and is cited as "design 47 G A-n".
 - **A-154** (design 46 approval mark §4, §16, §19; principles 7 and 8) The approval mark's three findings take scope
  `machine` and the id `<node>.<module>`, `<node>.<ask id>` or `<node>.approvals`, escaped as a key's name, with the
  subject of the tool runner on that machine, as the runner's first-view findings already do.
+- **A-155** (§561, §563, §302, A-77; principles 1, 2 and 3) restic's put-off wait for a restore is a bound key in a
+  state of its own on the bus, bounded by the setting `put-off-bound`: the key is the put-off record `backed-up` reads,
+  its expiry raises `backup-waits` and ends the wait, so the night never holds its lock without a bound and no file
+  or timer keeps it. BKP7 is not built: §555 gives `restore` its class's default with no own-item limit.