From cc7408eaa32a3e59057efe20b77f38949762fc48 Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 22 Nov 2026 00:16:02 +0100 Subject: [PATCH] Design 47 H2: lead answers use the glossary's words --- 03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md index c1ce3700..d501685f 100644 --- a/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md @@ -17,7 +17,7 @@ The lead's one-line answers to the questions H2's develop and review raise (impl and the other build nodes have 0711; the node-engine's composition on ace says "unchanged, equal to the composition the node runs". So the node-engine applies a directory entry's mode when it makes the directory and never when the directory exists with another mode, and its judgement reads what it wrote, not the disk. Fix in the node-engine - (mesh-host, H2's E lines): applying a directory entry sets its owner and mode when they differ on disk, and the + (`mesh-host`, H2's E lines): applying a directory entry sets its owner and mode when they differ on disk, and the composition's diff names a directory whose mode on disk differs. Test: a directory that exists with another mode is set to the declared one at apply. Recovery tonight: the mode set through the files seat's chmod verb on ace with this answer as its reason; the engine's next apply must leave it. P-mesh-owns-the-truth, P-failure-loud. @@ -56,7 +56,7 @@ The lead's one-line answers to the questions H2's develop and review raise (impl binding when bound. S8 in mesh-sdk is done by what exists: no refusal in the writer, no exported constants (a manifest is text the SDK's constants cannot reach). The one place that holds the numbers is §814's manifest validator in mesh-catalog (the finding-events binding's cap 8 MiB, drop-oldest, the setting findings-max-age with - its 7-day default), and the catalogue's module.json rows carry them. The mesh-catalog developer builds the validator + its 7-day default), and the catalog's module.json rows carry them. The mesh-catalog developer builds the validator rule with the rows; the mesh-sdk developer closes S8 as built. A rule states how it is checked (hq), P9. - **H-A-379 (an install's end is a step-ended naming the step install, 00:00)** H-A-367 (4) and §800 give the Node build seat an install whose end carries the archive object's name; the build-step part's step enum knows lint, unit @@ -155,7 +155,7 @@ The lead's one-line answers to the questions H2's develop and review raise (impl it does today. The edge the delivery plan derives: the node-engine's manifest states the declaration Version it reads (`declaration-reads`, beside its manifest reads of ADR 0614) and the composer's manifest the Version it writes (`declaration-writes`); the plan orders the writer of a Version after every node's engine reads it. Built: the field - and the two manifest words in mesh-sdk (its developer), the engine's word and reader (mesh-host), the composer's word + and the two manifest words in mesh-sdk (its developer), the engine's word and reader (`mesh-host`), the composer's word and writer and the plan's edge (mesh-delivery, with A1-A6). Until the plan reads the edge, the milestone plan names the order by hand: node-engine before the assigner. design-it-as-it-should-be, P3, ADR 0614. - **H-A-389 (a validate step judging a candidate that changes a seat's form, 00:26)** The mesh-catalog developer found