Design 47 H: section 10, finding 182

This commit is contained in:
2026-11-21 20:31:01 +01:00
parent 113eb3a9ce
commit 84e8cb4c38
@@ -698,3 +698,4 @@ Added by the lead at 21:30 CET, from the run of 19:50 to 21:30; a row met again
| Forty minutes after proof 2 (row 172) the home server's tool runner dropped out of discovery: its node-engine restarts it every 20 to 50 seconds, because the composition key for the tool runner at its new fingerprint alternates between two digests written in turn by two composition runs, one resource (the runtime process) differing; the mesh MCP server on the operator's desktop dropped at 20:16 too, and the control-node's tool runner missed a round of discovery, so the other machines' keys are being read; the stale writer is being found and dropped with the assigner's own tool, as the recovery of the moment; the holder of the seat mesh-wants (`mesh-delivery-assigner`), the node-engine and the tool runner (`node-tools`). The same read found the pipeline of 856 steps (row 178) not stalled: its validate run took 25 minutes, and its last test steps passed at 20:15; and a tool fault: the build seats' steps read tool answered empty on every node while steps ran (rows 172, 176 and 178). Owed, by H-A-302: a composition key written by the newest run only; a run whose pipeline ended writes nothing more; the node-engine applies only a newer write and names it; and the steps read tool answers the steps state. | open (the flapping); H2 (the rule, the tool) |
| Row 179's cause was not a stale run: no second composition run writes the key; on three of four machines the node-engine composes the tool runner's self-want itself, and while the grants part does not answer ("withheld unknown") every compose differs in the runtime process, so the node-engine writes a new revision and restarts the tool runner at each compose (every 20 to 50 seconds on the home server, slower on the operator's desktop and the control-node; the laptop, whose compose got the grants answer, is steady); the control-node's tool runner serves the grants answer, which closes the loop; the node-engine and the tool runner (`node-tools`). Settled by H-A-303, which amends H-A-302 (a withheld part keeps the running composition's part and writes no revision; the node-engine applies only a difference in a part it could read; the withheld part is said once), in build in the node-engine; the recovery of the moment, a held put of the tool runner on the home server through the assigner's tool, is being tried. Beside this, the operator decided at 20:24 (the relaying session wrote 20:35), through the session on their desktop, that the packet filter module gets standing control verbs on the seat node-packet-filter (allow, disallow and allowed, with an optional expiry) beside the ports derived from declarations, so design 08 §4 and the seat's verbs change (H-A-304; the decision record amending ADR 0170 is proposed; its first use is tcp 8000 on the LAN interfaces of the operator's desktop); its build runs beside H1's tail (rows 172, 176 and 179). | open (the flapping); other (the packet filter's verbs) |
| The mechanism of row 180's loop, read in the node-engine's code and the home server's journal: the self-compose never asks the seat mesh-grants; what goes unanswered is a module's entry or its registry versions, and a module held for that is composed as a stand-in whose slice of the tool runner's runtime process is rebuilt from what runs without its fingerprint and files words, so the process's module list and words differ from pass to pass and the node-engine restarts the tool runner each time ("restarted because its unit's Environment MESH_TOOL_MODULES changed"); the node-engine and the tool runner (`node-tools`). Settled by H-A-306, which amends H-A-303 (a withheld part is every input a compose asks and does not get; a held module's slice is copied verbatim from the running process; a withheld part is said once), in build in the node-engine. The recovery of the moment works: a held put of the tool runner on the home server through the assigner's tool at 20:22 stopped the loop (one restart at 20:26, then steady); the same hold goes on the operator's desktop and the control-node, to be released when the node-engine's fix is delivered (rows 172, 179 and 180). Owed: a read of composed values by resource. | open (the fix in build); H2 (the read) |
| The pipeline of 856 steps of the SDK's re-pin (rows 178 and 179) ended passed at 20:15, twenty-nine minutes after its placing, its validate run alone twenty-five of them; the catalog repository's pipeline of 36 movers (row 175) was placed in the same second with eleven steps, and runs. The packet filter's build (row 180) met two facts the lead's map had wrong and one design question: the seat's definition lives in the networking repository's contracts module, not in the contracts repository, so the group is three repositories (the networking repository, the catalog repository and the node-engine's); a definition that carries an event must be whole (every verb's answer form, the event's family, generated packages); and what the node-engine does when the holder's allowed verb does not answer as it composes the filter, settled by H-A-307 (it refuses to compose the filter and keeps the loaded one, said once; allowances only on a converged node's own table) (rows 175, 178 and 180); the pipeline runner (`mesh-delivery-pipeline`), the packet filter module and the node-engine. | other (the packet filter); H1 (recorded) |