From e88cce45dd6eec86d10b754eff217e547f1be986 Mon Sep 17 00:00:00 2001 From: jochen Date: Tue, 17 Nov 2026 11:04:04 +0100 Subject: [PATCH] Answer A-468..A-469s: G-24's 14 design questions and 20 design-meets-code entries, so its develop can start --- .../47-milestones/G-22-lead-answers-2.md | 74 +++++++++++++++++++ 1 file changed, 74 insertions(+) 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 186ddcb7..f5b2d18c 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 @@ -1622,3 +1622,77 @@ the principle that settles it, cited as "design 47 G A-n". and why it was not judged: a machine away (the watchman's machine-away) is still not asked and still said as a warning, but a step whose every machine is away, or whose machines are none, judged nothing and never ends `passed`. (From the review of A-467.) +- **A-468** (G-24 DQ-1; §719 `readers`; principle 7) A reader in `readers` is the composition step's `meshwants.StepRun` + with its ask id, so the assigner says each reader's `step-ended` after a restart or at the bound from the key alone. +- **A-468a** (G-24 DQ-2; §720, A-467; principles 3 and 7) A run whose composer answered ends `passed` with its verdict, + `not judged` machines included; each reading step judges a `not judged` machine `could not run` as A-467 says, so one + run per candidate and machine holds, and a `rerun` (§727) starts a new run for such a machine. +- **A-468b** (G-24 DQ-3; §719, §720, §725, A-465b; principles 1 and 11) `composition-runs-kept` and `test-runs-kept` are + swept as `inputs` is; `run-untaken-bound` is a second bound key per run with its own time to live, written at + `started` and heard on expiry as §720's clock is, so a candidate with no later step still ends an untaken run. +- **A-468c** (G-24 DQ-4; §420, A-465b; principles 1 and 9) `composition-runs` and `test-runs` are not declared in the + seats' `states`: only their owner and its tools read them. +- **A-468d** (G-24 DQ-5; §729; principle 7) The runner's `step-ended` of a composition step carries `mesh-wants`' `shared` + list as it came, under the same name; `asked-by` is a test step's alone. +- **A-468e** (G-24 DQ-6; §729, §731; principles 4 and 7) `shared` is a field of `StepResult`, so the pipeline key, + `pipeline-ended`'s `steps`, `show` and `stands` all name it. +- **A-468f** (G-24 DQ-7; §733 test 109; principle 10) Test 109 runs in mesh-delivery with a fixture build seat holder, + as the runner's integration test does today; mesh-catalog is not a member of G-24. +- **A-468g** (G-24 DQ-8; §727; principle 1) The assigner reads a step's last per-machine verdicts from the + `composition-runs` keys of the step's candidate whose `readers` name it: its own state. +- **A-468h** (G-24 DQ-9; §733 composer; test budget) The composer's test is table cases in `cmd/mesh-compose`'s + existing test, running `run()` in process (unit level): nothing is started, and `mesh-host` adds no test function. +- **A-468i** (G-24 DQ-10; §721; principles 3 and 11) A request with no `blame-tries` gets no search: the composer blames + only what its composition holds or refuses (§721 *What it names*, A-469k), never a bound of its own. +- **A-468j** (G-24 DQ-11; §730, §732; principles 3 and 4) Yes: the watchman raises `pipeline-stands` for every seeded step + that stands; the lead cancels the pipelines that can no longer end with `runner_cancel` before G-24 is delivered. +- **A-468k** (G-24 DQ-12; §730; principle 3) On `Resume` a running step whose result names no `shared` keeps its own ask + and ends by the path it was asked under. +- **A-468l** (G-24 DQ-13; §721; principle 3) The node-engine's path-owner check answers its pairs structured, and both + owners are blamed from it with the path, outside the search. +- **A-468m** (G-24 DQ-14; §721, A-466u over A-466g; principle 7) No order between the node-engine and the assigner: + mesh-delivery's `composer` package is published before both build (an edge of kind 1), and the group's members merge + in one pass. +- **A-469** (G-24 DMC-1; §732; principle 3) Built as §732 says: the watchman's manifest gains `mesh-wants.step-progress` + in `consumes`, and its clock times composition steps. +- **A-469a** (G-24 DMC-2; §726, §729, §732; principle 3) The runner says `step-started` for each step at every place it + asks one (`Start`, `Resume`, placing a waiting step, `PlaceRun`, `rerun`, `ask-again`). +- **A-469b** (G-24 DMC-3; §720, §725, §732, A-466y; principle 3) The runner says a test run's reading steps `waiting for a + build node` from the run's ask until the holder's `ask-taken`; the assigner says `wait-held` on `mesh-wants` with `on: + build node` for a composition run's readers until its ask's `ask-taken`. +- **A-469c** (G-24 DMC-4; §724; principle 7) The share digest is the sha256 of the module's build-input fingerprint, the + level, the step's status in the policy and the step's fetch (directory and paths): what the runner holds, so two + artifacts with one fetch meet and two with different fetches do not. +- **A-469d** (G-24 DMC-5; §719, §725; principle 11) The manifest's `max-mib` is the ceiling, and the process refuses a + write at its setting's value (`composition-runs-cap-mib`, `test-runs-cap-mib`), as `inputs`' cap is judged. +- **A-469e** (G-24 DMC-6; §725; principle 7) `test-runs-objects` is the state's own object store, made with the state + and declared nowhere; an object there lives until the runner deletes it with its key. +- **A-469f** (G-24 DMC-7; §728; principles 4 and 7) The four are seat verbs, of `mesh-wants` and `mesh-pipeline-runner`, + their class and callers in the seat definitions as `cancel` and `rerun` are; each module's tool of §728's name calls + its verb. +- **A-469g** (G-24 DMC-8; §728, A-107; principle 12) `runner_test_runs_drop`'s verb is answered by the runner's process, + the only writer of `pipelines`. +- **A-469h** (G-24 DMC-9; §721; principle 3) `blamed` is always written, `[]` when it blames none, so an old composer's + absent field stays tellable. +- **A-469i** (G-24 DMC-10; §729; principle 8) The request's field is `blame_tries`, in the shape's own snake case. +- **A-469j** (G-24 DMC-11; §721; principle 7) `blamed` is `ComposeSent`'s set of modules held and not held before, + answered structured; §721's bounded search runs only where a machine fails with no module held, `blame_tries` there + replacing `maxCulprits`. One search, not two. +- **A-469k** (G-24 DMC-12; §721; principle 7) A changed module is one placed on the machine whose case manifest's + content digest differs from `ComposedHow.Manifests`, or that it lacks. +- **A-469l** (G-24 DMC-13; §727; principle 3) A moved step's end is marked `rerun` and names the new run in `shared`; the + runner reopens an ended step on an end naming a newer run than the one it read, and takes a redelivered end as today. +- **A-469m** (G-24 DMC-14; §726, §731; principle 7) A reading test step keeps no ask of its own: the run's ask is named + in `shared` alone, and the run's `step-ended` reaches its readers through the `test-runs` key. +- **A-469n** (G-24 DMC-15; §723; principle 1) The assigner removes a pipeline's composition steps from `readers` on the + runner's `pipeline-ended` of outcome superseded or cancelled, which it consumes already. +- **A-469o** (G-24 DMC-16; §732; principle 8) The watchman's key is `//`, the artifact empty + for a module's step; its queued key takes the same form. +- **A-469p** (G-24 DMC-17; §731, §732; principle 1) Built with §732: the watchman's manifest gains the `invokes` entry + `seat:mesh-pipeline-runner.stands`, and it seeds its open steps from it at start. +- **A-469q** (G-24 DMC-18; §729; principle 7) Both runner events carry one `shared` object `{run, ask, asked-by}`, + `asked-by` optional and left out on `step-started`. +- **A-469r** (G-24 DMC-19; §729, §731; principle 7) `ask` and `shared` are optional fields of `Wait`, left out where they + do not apply. +- **A-469s** (G-24 DMC-20; §720; principle 1) The assigner's manifest gains the `invokes` entry `seat:node-build-go.drop` + beside §720's `consumes` entries. -- 2.54.0