From 5b54cfdad14099437d369904df74863bf4204071 Mon Sep 17 00:00:00 2001 From: jochen Date: Wed, 11 Nov 2026 22:45:57 +0100 Subject: [PATCH] Answer A-58: an owner change is its own change value 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 dda442e5..edb1f33d 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 @@ -223,3 +223,7 @@ names the principle that settles it, and is cited as "design 47 G A-n". `resolved` and `toolchain` from the step's result (`dependencies`, §673), `branch` the watched branch of the catalog revision whose entry the build came from, and `source` that revision, both kept on the build's reservation from the candidate it built. +- **A-58** (§540, §685, §8; principle 8, one word per thing) An owner change is said as `condition-changed` with a new + `change` value `owner`, added to the seat `mesh-conditions`' enum in mesh-contracts; `words` stays for a change of the + text. `seed-waits` waits on the operator through the finding's own `waiting-on`, which the indexer sets and the keeper + copies, with no rule of the keeper's for that kind.