From 03813cce783cab6917fc6b7e01580a9d6cff80e0 Mon Sep 17 00:00:00 2001 From: jochen Date: Wed, 11 Nov 2026 23:26:00 +0100 Subject: [PATCH] Answer A-91: the warrant in the router's record, unnamed steps, the runner's asking half Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md index c7555817..2fee1462 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md @@ -351,3 +351,7 @@ names the principle that settles it, and is cited as "design 47 G A-n". the trunk's, taken per watched branch: `sourceFollow` takes `source.` for every watched branch, and the source path (`ApplySource`, the catch-up, the heads' take-in) runs with the branch as its argument, writing that branch's revision; the trunk is each registration's first branch, not a constant. +- **A-91** (§26, §37, §700, Q-RN8; principle 7) The router's record value carries its `warrant` as §700 says: the + operator-channel contract's `AsksByAskerIDValue` gains the field. A step the module's policy does not name is no step + of its pipeline, so `Status` has no open question for it. The runner places a pipeline's steps when it starts it and + asks each build seat for its step, as its asking half; that half is built in G.