Answer A-157: warranted asked again on the holder heard; call-unanswered on a bound key

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 09:41:28 +01:00
parent b054da9141
commit 4020ff8b70
1 changed files with 5 additions and 0 deletions
@@ -585,3 +585,8 @@ names the principle that settles it, and is cited as "design 47 G A-n".
  driver takes "every build module" as the modules that claim a build seat (`node-build-*`) in the catalog half it
  follows, the one source A-82 gives; the holder's own per-verb `Allowed` checks go with the list, since §610's class
  defaults are applied where the call is read, and the refusal of an unproven caller is that reader's.
+- **A-157** (design 46 approval mark §16, §19, ADR 0668 §1, A-77; principles 1 and 3) Each try of `warranted` is a
+  `DoKept`; past its bound the call is made again when the hand-act seat's holder is heard again (the seat-holders
+  view the runner follows) and at each start; `call-unanswered` is raised on the expiry of a five-minute bound key per
+  ask, not a timer. A failed read or write of `approvals` is made again at the next marked call and at the next
+  membership change the runner hears.