Answer A-222: a failed adopted event is asked again; runs taken up at start

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 09:41:28 +01:00
parent ae6407fb71
commit 4fff5cdfab
1 changed files with 4 additions and 0 deletions
@@ -167,3 +167,7 @@ the principle that settles it, cited as "design 47 G A-n".
 - **A-221** (§509, A-208; principle 8, one word per thing) On every forge message `branch` names the watched branch
  the move changed, on `merged` as on `pushed`; a merged pull request's own branch is kept as `head` (a group is
  known by its head branch); `pushed`'s head before is `before`.
+- **A-222** (A-193, A-199, §350, A-77; principles 2 and 3) An adopted event whose handler fails is asked again by
+  the bus, not acknowledged; at its start the runner reads, for each run pipeline with no steps yet, its candidate's
+  revision through `revision`, so a placing lost while it was down is taken up. A run's rerun asks with the
+  candidate's catalog half. An unanswered drop is said `call-unanswered` on a five-minute bound key's expiry.