Design 47 G: a test run asked again moves every step that reads it; two items after G

The coordinator's answers of 2026-11-17: a step left reading a failed result would say what
is no longer true, so a rerun of a test run moves all its readers; the node-engine's
differing input bytes and the split of design 47's main file wait until after G.
This commit is contained in:
2026-11-17 10:25:15 +01:00
parent 31cd62aeec
commit 77318ca60e
2 changed files with 21 additions and 4 deletions
@@ -220,9 +220,12 @@ Each line is a choice within ADR 0666 §7, §8 and §17, settled by the principl
it (§24, §419).
- **Dropped only with its last reader.** A step that is superseded or cancelled leaves `readers`, and the run's ask
is dropped (§119) only when no reader is left.
- **Asked again.** A `rerun` of a test step joins a run of its key while that run is running, or reads one that
started after the step's last end, and otherwise asks a new run, replacing the ended key by compare-and-set. A
sibling step with the same key moves only by its own rerun, which then reads that run.
- **Asked again, for every reader.** A `rerun` of a test step joins a run of its key while that run is running, or
reads one that started after the step's last end, and otherwise asks a new run, replacing the ended key by
compare-and-set. The new run's end moves every pipeline step that read the key's former run and did not pass: each
says `step-ended` again with the new outcome, marked as a rerun with the caller of the step asked again (§73). A
step left reading a failed result would say what is no longer true (principles 3 and 7; the coordinator,
2026-11-17).
- §727 **The tools.** (§83; ADR 0666 §25; principle 4) Two for each new state, in §83's table:
- `assigner_compositions` takes a candidate, a machine, or neither, and answers each composition run with its
program, input digest, ask, readers, outcome and verdict, and the state's fill against its cap.
@@ -242,7 +245,8 @@ Each line is a choice within ADR 0666 §7, §8 and §17, settled by the principl
blamed by name, and two modules owning one path are both blamed.
- Whole (runner and Go build module): a module whose program and bundle test one directory asks one unit step and
one integration step. Both artifacts' steps end with that result and `shared`, a failing test fails once, and
`pipeline-ended` counts the module's tests once.
`pipeline-ended` counts the module's tests once. A rerun of one artifact's failed step that passes moves the other
artifact's step to passed too.
- Live: in the first publish after G's delivery, the composition run asks of each revision number at most its
machines, and each module's test steps run once per level.
@@ -167,3 +167,16 @@ deals with it, which is how the list is kept true.
glossary word in their place.
- A composition that passes on every machine as "not judged: the composer was handed no seat list" is reported as
passed: a composition step that judged nothing must fail or say so (principle 3).
## From the composition runs of 2026-11-17
- **The node-engine answers `compose-candidate` with different bytes for one candidate.** Within 30 seconds the
assigner kept twelve inputs of exactly 1,491,623 bytes with different digests for the same revision. The bytes differ
in the node-engine's answer, not in the assigner's request; a guess, not checked: a slice whose order changes between
asks, perhaps `ComposedHow.Running`. Under design 47 G §718 one composition run per candidate and machine asks each
node once, so this no longer multiplies anything and stays out of G (principle 7; the coordinator, 2026-11-17). After
G: find it by comparing two kept inputs of one node, read by digest through `mesh-wants`' `input`, and decide whether
the answer must be the same bytes while the node is unchanged.
- **Design 47's main file is split into milestone parts** (playbook 02, *The shape of a design*). It is about 250 KB
against its 80 KB bound. The split is a separate amendment after G's delivery, never folded into a line of G (the
coordinator, 2026-11-17).