From c96d5d6c6d2a91808ce0fd7adc220cded8df1e74 Mon Sep 17 00:00:00 2001 From: jochen Date: Wed, 11 Nov 2026 23:25:22 +0100 Subject: [PATCH] Answer A-90: every watched branch is taken in by the trunk's take-in 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 db84c24c..c7555817 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 @@ -347,3 +347,7 @@ names the principle that settles it, and is cited as "design 47 G A-n". - **A-89** (§37, §700, A-74; principle 7, one way for every asker) The runner reads its approval ask's warrant from the router's record of its ask, through the seat `operator-channel` as A-74 has it, never from the decided event's body; the decided event only wakes it. +- **A-90** (§13, §14, §291, ADR 0666 §6, A-85; principle 7) A non-first branch's revision is made by the same take-in as + 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.