Answer A-247: a validation says it was accepted; its answer comes in step-ended

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 09:41:28 +01:00
parent c80b5eedd2
commit 41b2345ba4
1 changed files with 4 additions and 0 deletions
@@ -260,3 +260,7 @@ the principle that settles it, cited as "design 47 G A-n".
 - **A-246** (§376, §498, A-211; principles 2 and 4) A dependent's delivery wait is kept in a state of its own,
  `delivery-waits` (key the module, value the `wait-held` said), read by `assigner_waits` beside the others;
  `assigner_release` {module, step: delivery} writes the hand-act log first and ends the wait `released`.
+- **A-247** (§713, A-232; principles 1, 2 and 7) The pending value's `validation` gains `accepted` (the seq it was
+  accepted at), so a revision held for another indexer is never asked again; `validation` sits on the newest pending
+  value of the revision alone. The answer is read from the `step-ended` event's own output and output object, never
+  through the build seat's `steps`; the ask is put through the delivery SDK's `buildrun.Asker`.