From 92929d55efdf6d06820b64ea6ca9e93e901bd24e Mon Sep 17 00:00:00 2001 From: jochen Date: Tue, 17 Nov 2026 01:22:00 +0100 Subject: [PATCH] Correct A-459a: rule 7 follows composed through the read the assigner's manifest declares --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index bce9c9fd..f021cb34 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -1396,10 +1396,11 @@ the principle that settles it, cited as "design 47 G A-n". no version or parts, `entry-missing` or "want names no digest", and a want was rewritten only after a passed pipeline, which waited on A-458.) - **A-459a** (A-459; principles 1, 10 and 3) Rule 7 learns "composed" per module from the node-engine's `composed` - for `..` (its digest a composition, a refusal not composed), heard on the node-engine's per-node - `mesh-host.composed` events the assigner follows in its pass as it follows the haves, never by reading the - node-engine's bucket; the module's own have is not the source, since none names a fingerprint before its want does. - (From the develop of A-459: `composed(node, module, fp)` read only `.node`.) + for `..` (its digest a composition, a refusal not composed), followed per node as the assigner + follows the haves, through the read its manifest already declares (`reads`: `mesh-host.composed`); the module's own + have is not the source, since none names a fingerprint before its want does. (From the develop of A-459: + `composed(node, module, fp)` read only `.node`. Corrected 2026-11-17: the first wording said "never by + reading the node-engine's bucket", which contradicted the declared read the haves already use.) - **A-462a** (A-462; principles 7, 9 and 3) "A build that has no entry" is a fingerprint the catalog half the assigner follows holds no entry for on any watched branch. The assigner asks the indexer nothing for it: taking a build in is the indexer's own work on its pending state, and its tool `indexer_take_in_pending` takes the indexer's own keys,