From a1c77688ab8cb638ea6f32cde10e6349f0234355 Mon Sep 17 00:00:00 2001 From: jochen Date: Wed, 11 Nov 2026 22:00:25 +0100 Subject: [PATCH] A-23 names the trace operation, as built Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ --- 03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 978dffdd..c8f97d42 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 @@ -91,7 +91,7 @@ names the principle that settles it, and is cited as "design 47 G A-n". module's own check interval; a field the contract's `Finding` lacks (`resolved`, and its words in every module, the watchman's included) is dropped, the keeper saying a clear in its own words; an id is escaped as a name, and a `ref` goes into the id only where two findings of one kind share an id; old keys are cleared by the writer's first statement. mesh-sdk keeps no old `views.Finding` or `FindingWriter` beside the generic writer. -- **A-23** (§81, §132; principle 7) The gate's `recovery` marks the delivery record through its ordinary update, with one +- **A-23** (§81, §132; principle 7) The gate's `recovery` marks the delivery record through its ordinary update (the record type's `trace` set-fields operation), with one field `recovery` holding `by` (the proved caller), `why` and `commit`; no new operation. Then it says `recovery-merged`. - **A-24** (§431, §172, §592, §158; principles 7 and 4) Once the merge states go, `deliveries`, `show` and `groups` answer the delivery records as the gate keeps them (G-3 *The delivery record*), filtered by their arguments, with no line