From 8884fc9ee729639bf36318c14b61586dcddd2967 Mon Sep 17 00:00:00 2001 From: jochen Date: Tue, 17 Nov 2026 11:17:23 +0100 Subject: [PATCH] G-23: the faults met on 2026-11-17, so none is lost before G is delivered --- .../47-milestones/G-23-after-delivery.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-23-after-delivery.md b/03-DESIGN/01-to-be/47-milestones/G-23-after-delivery.md index e410468e..63e45955 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-23-after-delivery.md +++ b/03-DESIGN/01-to-be/47-milestones/G-23-after-delivery.md @@ -180,3 +180,20 @@ deals with it, which is how the list is kept true. - **Design 47's main file and G-22 are split** (playbook 02, *The shape of a design*). The main file is about 250 KB against its 80 KB bound, and G-22 about 165 KB against a milestone file's 60 KB. The operator decided at 10:31 CET on 2026-11-17 that the split comes after G, as a separate amendment. + +## Faults met on the way (2026-11-17; note each on the issue that covers it) + +- **The assigner's long line, met a second time.** On 2026-11-17 from 11:02 CET the assigner on the stable node logs, + several times a minute, that "the manifest of the running build of" about 100 modules "cannot be read, so what the + module graph says they serve is counted as served". Cause not yet known: nearly every module is named, so the + assigner reads the running builds' manifests where none is kept. Being the second meeting, its fix is folded into + G-24's assigner change once A1 to A7 are built. +- **The builder's and teller's integration tests fail only the 30 s setup bound under load**, and pass idle: the bound's + kind (a setup bound judged on a busy build node) is decided after G. +- The runner's journal floods with ends that name `pipeline ""`: the build seats' run asks are heard on the runner's + subjects. +- `TestAProposalIsAnsweredApprovedAndWritten` (assigner) fails on main; `TestTheNodeComposesItsWantsFromTheBus` + (node-engine) fails now and then. +- `mesh-enrolment` is placed on no node, so its composition step can never run and it never releases. +- `claude_code_wait`'s `said` refused a wait past its bound; `mesh_wait` cannot wait on the gate's `source-moved` nor on + the runner's events. -- 2.54.0