Compare commits

...
Author SHA1 Message Date
jschoubben 571bb261d0 Design 47 H2: H-A-483 second addendum, the builder retires its class durables 2026-11-22 18:14:16 +01:00
jschoubben cc125479a3 Design 47 H2: H-A-483 addendum, one consumer per holder 2026-11-22 18:13:32 +01:00
jschoubben 4333c3d8c2 Design 47 H2: H-A-483, one consumer for the publishes; H-A-473 withdrawn 2026-11-22 18:11:43 +01:00
jschoubben c2712b5cd1 Design 47 H2: H-A-481 transfers finish or are taken over; H-A-482 a missing output is said 2026-11-22 17:02:11 +01:00
jschoubben 364552d2b2 Design 47 H2: H-A-479 third addendum, a reopening never builds beside an open pipeline 2026-11-22 16:26:12 +01:00
jschoubben 5bbe18d56b Design 47 H2: H-A-479 second addendum, withdraw own movers only; no again bound; no side-by-side build 2026-11-22 16:17:29 +01:00
jschoubben abd562e40a Design 47 H2: H-A-478 second addendum, kept grants keyed by the inputs' digest 2026-11-22 16:10:47 +01:00
jschoubben 10627efcbd Design 47 H2: H-A-480 addendum, the clear of a mark 2026-11-22 16:01:54 +01:00
jschoubben 17346cccf3 Design 47 H2: H-A-478 addendum, the tools program keeps what it composed 2026-11-22 15:59:57 +01:00
jschoubben 218c40206e Design 47 H2: H-A-480, a rank wait is never overwritten by the composer's hold 2026-11-22 15:58:05 +01:00
jschoubben ac7654bc72 Design 47 H2: H-A-479 addendum, the again key; a reopened pipeline pins its revision again 2026-11-22 15:55:39 +01:00
jschoubben 0f71246646 Design 47 H2: H-A-479, a failed mover is started again at the head 2026-11-22 15:52:04 +01:00
jschoubben 60f426471f Design 47 H2: H-A-478, grants-for answers from what the pass composed 2026-11-22 15:44:38 +01:00
jschoubben f2d0ecd11b Design 47 H2: H-A-477 addendum, no engine code for the stale resolve now 2026-11-22 15:37:18 +01:00
jschoubben 59bc826d6f Design 47 H2: H-A-477, a setting's word is never a bundle's own 2026-11-22 15:29:46 +01:00
jschoubben 646c2c3cd8 Design 47 H2: H-A-476, a test reads a state after the work that writes it 2026-11-22 14:56:37 +01:00
jschoubben 33ba181557 Design 47 H2: H-A-474 held version by the artifact's digest; H-A-475 a failed step keeps its error's head 2026-11-22 14:45:06 +01:00
jschoubben f6b0a843b2 Design 47 H2: H-A-473 third addendum, the again side waits for a live item in flight 2026-11-22 14:27:46 +01:00
jschoubben 9c0e90231c Design 47 H2: H-A-473 second addendum, an idle dispatch keeps no waiting pull 2026-11-22 14:25:45 +01:00
jschoubben bf02dc3a44 Design 47 H2: H-A-472 third addendum, remove only an orphan; one bound as a setting 2026-11-22 14:21:16 +01:00
jschoubben 947dbb590e Design 47 H2: H-A-473 addendum, the done builds take the level bound, the hang part a short one 2026-11-22 14:15:12 +01:00
jschoubben 2e1a6688ec Design 47 H2: H-A-473, the publish dispatch pulls live first 2026-11-22 14:10:44 +01:00
jschoubben cb1b717638 Design 47 H2: H-A-471 second addendum, plain merges need a read view 2026-11-22 14:09:11 +01:00
jschoubben e520f4a5a1 Design 47 H2: H-A-472 second addendum, the composer's reading of the twins 2026-11-22 14:08:00 +01:00
jschoubben 8ae2aab29f Design 47 H2: H-A-472 addendum, the composer makes only the twin a process reads 2026-11-22 14:05:13 +01:00
jschoubben 4f9c6410e9 Design 47 H2: H-A-472, orphaned durables are removable and ignored by the behind check 2026-11-22 13:55:01 +01:00
jschoubben 8fd62a2495 Design 47 H2: H-A-471 addendum, the note and merge-called 2026-11-22 13:54:05 +01:00
jschoubben 3eb01ece44 Design 47 H2: H-A-471, the merge verb merges a repository of no module plainly 2026-11-22 13:43:07 +01:00
jschoubben d42904e533 Design 47 H2: H-A-468 third addendum, every composed worker is created 2026-11-22 13:02:53 +01:00
jschoubben 38070a4f75 Design 47 H2: H-A-470 third addendum, a covered subject is replaced 2026-11-22 12:59:57 +01:00
jschoubben 1e985bac5c Design 47 H2: H-A-470 second addendum, the seed's warrant 2026-11-22 12:40:10 +01:00
jschoubben 0abe9589d2 Design 47 H2: H-A-470 addendum, the unwritten registration's end state and finding 2026-11-22 12:35:23 +01:00
jschoubben 743b2c53c1 Design 47 H2: H-A-470, a source-only registration's history subject 2026-11-22 12:33:30 +01:00
jschoubben c975e5b39a Design 47 H2: H-A-469 addendum, the whole-catalog test fails on keys only 2026-11-22 11:46:15 +01:00
jschoubben e9192d7c7e Design 47 H2: H-A-468 second addendum, SeatQueue is the one derivation 2026-11-22 11:35:19 +01:00
jschoubben dd758d6e5f Design 47 H2: H-A-468 addendum, the holder's advisory subscribe is granted 2026-11-22 11:34:53 +01:00
jschoubben 0db5b941de Design 47 H2: H-A-469, the composer strips every manifest-only process key 2026-11-22 11:34:37 +01:00
jschoubben 0dbcb115f9 Design 47 H2: H-A-468, the grants part makes a seat's one shared worker 2026-11-22 11:29:29 +01:00
jschoubben 1ea623bf1e Design 47 H2: H-A-467 addendum, the list row gains source, revision and counts 2026-11-22 11:09:46 +01:00
jschoubben 0058f2671c Design 47 H2: H-A-467, the delivery view shows the pipelines (issue 1983) 2026-11-22 11:08:36 +01:00
jschoubben e104dae99c Design 47 H2: H-A-466, the node-engine composes nothing of a package artifact 2026-11-22 04:27:41 +01:00
jschoubben aa4bd831b7 Design 47 H2: H-A-465, the take-in's manifest read sets an unknown word aside 2026-11-22 04:05:59 +01:00
jschoubben 5fd71bf9a2 Design 47 H2: H-A-464 addendum, the grants fact corrected 2026-11-22 04:04:06 +01:00
jschoubben b2d54d567f Design 47 H2: H-A-464, the builder's process stays on the module's account 2026-11-22 03:51:15 +01:00
jschoubben cbf3d8acb3 Design 47 H2: H-A-463, the test budget is a loose ceiling 2026-11-22 03:37:49 +01:00
jschoubben 60b653cbcc Design 47 H2: H-A-462, the builder's health judgement in the shared package 2026-11-22 03:24:50 +01:00
jschoubben 32d1aef305 Design 47 H2: H-A-461, mesh-delivery's review round 1 answers 2026-11-22 03:20:14 +01:00
jschoubben fb09134ba4 Design 47 H2: H-A-460, a record-too-large finding names its record 2026-11-22 03:07:53 +01:00
jschoubben dc8796cdb0 Design 47 H2: H-A-459, a view act holds the record's summary 2026-11-22 02:55:43 +01:00
jschoubben 0b0760adab Design 47 H2: H-A-458 addendum, one contracts commit at form 4 2026-11-22 02:45:30 +01:00
jschoubben 7f0b70df75 Design 47 H2: H-A-458, the node-engine's review round 1 answers 2026-11-22 02:44:02 +01:00
jschoubben c5e4c2e1da Design 47 H2: H-A-457, the gate keeps no old act operation 2026-11-22 02:42:41 +01:00
jschoubben 5b45d8f92b Design 47 H2: H-A-454 third addendum, the whole test runs without composed grants 2026-11-22 02:40:25 +01:00
jschoubben c18e113c7e Design 47 H2: H-A-454 second addendum, the builder's process gets a bus of its own 2026-11-22 02:38:54 +01:00
jschoubben 4e534ae0cd Design 47 H2: H-A-456, RG3 is proven where each act lives 2026-11-22 02:38:04 +01:00
jschoubben 0477e04643 Design 47 H2: H-A-455, the gate's owed acts are entries of their own 2026-11-22 02:33:45 +01:00
jschoubben 3679bec24a Design 47 H2: H-A-454 addendum, the builder's process keeps the module's account 2026-11-22 02:26:40 +01:00
jschoubben 5aa3b4b8c4 Design 47 H2: H-A-454, publishes in the old section, read by a seat verb 2026-11-22 02:25:19 +01:00
jschoubben 93039639e5 Design 47 H2: H-A-453, mesh-catalog's review round 1 answers 2026-11-22 02:22:57 +01:00
jschoubben 9553ce0e83 Design 47 H2: H-A-452, the shared test seat list gains the group's definitions 2026-11-22 02:21:14 +01:00
jschoubben c4cfceefa9 Design 47 H2: H-A-451, the tool runner's review round 1 answers 2026-11-22 02:17:20 +01:00
jschoubben e098ffdef5 Design 47 H2: H-A-450, a source-only registration of a repository with a manifest 2026-11-22 02:12:52 +01:00
jschoubben ee2e2bc438 Design 47 H2: H-A-449, a verb's description from the generated contract 2026-11-22 02:09:59 +01:00
jschoubben 50a890676c Design 47 H2: H-A-445 addendum, the nodes counted as having the need 2026-11-22 02:09:25 +01:00
jschoubben 96b8f0c293 Design 47 H2: H-A-448, publishes is a work-queue template in requires; the duplicates window 2026-11-22 02:06:03 +01:00
jschoubben 86b9b25c39 Design 47 H2: H-A-447, the seat list is written at the indexer's start 2026-11-22 02:03:40 +01:00
jschoubben ea6d9aa8fe Design 47 H2: H-A-446, build_current's holders; publishes and its consumers 2026-11-22 02:00:29 +01:00
jschoubben 1324d2183d Design 47 H2: H-A-445, how a declined step reaches the runner and is placed again 2026-11-22 01:56:29 +01:00
jschoubben e67a8f1bae Design 47 H2: H-A-444, a not-needed act is ended, not refused 2026-11-22 01:55:54 +01:00
jschoubben 2e2f1072ee Design 47 H2: H-A-443, the seat-list verb hands the bytes; a revision's own definitions stay 2026-11-22 01:54:43 +01:00
jschoubben 7485c2cb29 Design 47 H2: H-A-442, a source-only check says run-started 2026-11-22 01:52:32 +01:00
jschoubben 24c678418f Design 47 H2: H-A-441, the seat-list object and how the validator takes it 2026-11-22 01:51:14 +01:00
jschoubben fb218be9c7 Design 47 H2: H-A-440, the publishes queue's consumers and the publish items 2026-11-22 01:48:03 +01:00
jschoubben ecc590da57 Design 47 H2: H-A-435 second addendum, the manifest's health stays kind unit 2026-11-22 01:45:36 +01:00
jschoubben 7df293752f Design 47 H2: H-A-439, the vault value keeps the token's scopes 2026-11-22 01:42:28 +01:00
jschoubben ad98ab82f7 Design 47 H2: H-A-438, a source-only registration's module word 2026-11-22 01:39:52 +01:00
jschoubben 3f62a62d09 Design 47 H2: H-A-437, a cap is set above the live fill 2026-11-22 01:38:01 +01:00
jschoubben e1af8b445c Design 47 H2: H-A-435 addendum, builder_health in the runner's form 2026-11-22 01:33:34 +01:00
jschoubben 608b72247e Design 47 H2: H-A-436, the settle bound is a key with a TTL 2026-11-22 01:32:12 +01:00
jschoubben 04fb9e7499 Design 47 H2: H-A-435, the builder's health is a tool 2026-11-22 01:31:39 +01:00
jschoubben 66f96ba36b Design 47 H2: H-A-373 addendum, the SDK refuses an empty version for packages and every bundle 2026-11-22 01:31:14 +01:00
jschoubben 1b1f7b6925 Design 47 H2: H-A-434, the objects template gains max-age-days 2026-11-22 01:30:52 +01:00
jschoubben 720e7e7870 Design 47 H2: H-A-433, performed-keep is the bucket's TTL 2026-11-22 01:29:34 +01:00
jschoubben f2f7330c75 Design 47 H2: H-A-432, an owed act's record, precondition and when it is checked 2026-11-22 01:27:37 +01:00
jschoubben c951849dfc Design 47 H2: H-A-431, CatalogEntry carries class; mesh-networking joins the group 2026-11-22 01:26:23 +01:00
jschoubben c1a5b310fe Design 47 H2: H-A-430; words of H-A-429 2026-11-22 01:25:27 +01:00
jschoubben 3b29f26c77 Design 47 H2: H-A-427, where the install archive's tree lies 2026-11-22 01:22:12 +01:00
jschoubben 13e53e498c Design 47 H2: H-A-426, the forge's tokens' vault names; a note on §819's check 2026-11-22 01:20:59 +01:00
jschoubben bc56c7db9c Design 47 H2: H-A-425, the unbuildable list lives in a builder state 2026-11-22 01:19:49 +01:00
jschoubben 65d7ee37d9 Design 47 H2: H-A-424, I4's four points 2026-11-22 01:19:25 +01:00
jschoubben 5d9b701de7 Design 47 H2: H-A-423, a paged read's total 2026-11-22 01:16:13 +01:00
jschoubben a5fa22a4b8 Design 47 H2: H-A-422, the forge's tokens through the vault, a name per mint 2026-11-22 01:15:13 +01:00
jschoubben 6de57ebb11 Design 47 H2: H-A-415 second addendum, (2) withdrawn 2026-11-22 01:14:47 +01:00
jschoubben e853f9a4e7 Design 47 H2: H-A-419 to H-A-421; the H-A-415 addendum's words 2026-11-22 01:14:09 +01:00
jschoubben 4ecf9e2206 Design 47 H2: H-A-412 third addendum, the run text goes only to the outputs object 2026-11-22 01:11:23 +01:00
jschoubben 702f226920 Design 47 H2: H-A-415 to H-A-418 2026-11-22 01:11:00 +01:00
jschoubben d78897ee1d Design 47 H2: H-A-412 second addendum, the level's text and no-longer-kept 2026-11-22 01:06:03 +01:00
jschoubben 1db1271e27 Design 47 H2: H-A-412 addendum, the read verb answer for an oversized step end 2026-11-22 01:04:47 +01:00
jschoubben ea92464a46 Design 47 H2: H-A-414, two readings of §786 confirmed 2026-11-22 01:04:18 +01:00
jschoubben bf39c5ae3f Design 47 H2: H-A-413 addendum, dry-runs keeps packages only 2026-11-22 01:03:17 +01:00
jschoubben 6daefe666f Design 47 H2: H-A-413 a dry run's kept stores; H-A-410 second addendum 2026-11-22 01:01:10 +01:00
jschoubben 4d8c853f46 Design 47 H2: H-A-410 addendum, a nak'd ask is listed as waiting again 2026-11-22 00:59:37 +01:00
jschoubben 9ca54b463e Design 47 H2: H-A-412, a run's output and an oversized answer are two things 2026-11-22 00:59:06 +01:00
jschoubben 199b8e9631 Design 47 H2: answers' times read from the clock 2026-11-22 00:58:16 +01:00
jschoubben 66c70e6627 Design 47 H2: H-A-407 addendum, blakejs beside tweetnacl; src/seal 2026-11-22 00:57:56 +01:00
jschoubben 2ba6b946f0 Design 47 H2: H-A-411, M1's store rows and the validator's home 2026-11-22 00:57:16 +01:00
jschoubben f987fbe3f2 Design 47 H2: H-A-409 a running take-in's waiting-on; H-A-410 a holder's asks tool reads its queue via SDK and runtime 2026-11-22 00:55:23 +01:00
jschoubben 7dca93c025 Design 47 H2: H-A-407 TypeScript seals in mesh-sdk; H-A-408 a source-only check's step-ended 2026-11-22 00:54:28 +01:00
jschoubben 7a7a1ffea5 Design 47 H2: H-A-406, a rerun build that passes places again its dependents' steps 2026-11-22 00:53:33 +01:00
jschoubben 15ef740ef5 Design 47 H2: H-A-405, a kept chunked call in mesh-sdk; the compose-candidate ask id 2026-11-22 00:52:44 +01:00
jschoubben 3900d17bb1 Design 47 H2: H-A-404, a drop of an unpulled ask is kept in taken 2026-11-22 00:52:01 +01:00
jschoubben 531df30528 Design 47 H2: H-A-403, the install ask's form and the install archive's version 2026-11-22 00:51:39 +01:00
jschoubben e9bb740c7e Design 47 H2: three answers' times read from the clock 2026-11-22 00:49:10 +01:00
jschoubben 56deca5f34 Design 47 H2: H-A-402, forge_merged reads a range of numbers, paged 2026-11-22 00:48:14 +01:00
jschoubben d5fbf23107 Design 47 H2: H-A-401, a dropped ask's step ends could-not-run; B1's choices stand 2026-11-22 00:47:41 +01:00
jschoubben 9b981693df Design 47 H2: H-A-400, a taken key only for an act that acted; TypeScript reads the composed setting word 2026-11-22 00:47:02 +01:00
jschoubben c3246cfeb4 Design 47 H2: H-A-399, the SDK's step parts owner, the install archive via the artifact store, check-needs names seats 2026-11-22 00:43:18 +01:00
jschoubben decac6fc68 Design 47 H2: H-A-398, an unfinished mover is placed by the seat verb place-unfinished 2026-11-22 00:40:53 +01:00
jschoubben 9981bcbfc3 Design 47 H2: the lead answers' times read from the clock 2026-11-22 00:34:43 +01:00
jschoubben 270f469fa1 Design 47 H2: H-A-397, a start puts again only the asks no holder took 2026-11-22 00:32:44 +01:00
jschoubben 94f77b2dde Design 47 H2: H-A-396, gate_times names each class's newest delivery for the probe 2026-11-22 00:32:01 +01:00
jschoubben 1dbc2844dc Design 47 H2: H-A-394 addendum, class stays out of the baseline 2026-11-22 00:28:47 +01:00
jschoubben 51c636b91f Design 47 H2: H-A-395, the ask bound re-armed by progress, every seat 2026-11-22 00:21:59 +01:00
jschoubben 8d1f4ee027 Design 47 H2: H-A-394 uses the glossary's word 2026-11-22 00:21:32 +01:00
jschoubben 19e8535719 Design 47 H2: H-A-394 a module's class and the delivery time's start; H-A-388 addendum 2026-11-22 00:20:56 +01:00
jschoubben 28def7eae5 Design 47 H2: H-A-393, a version held at another digest is refused before the reservation is asked 2026-11-22 00:17:01 +01:00
jschoubben cc7408eaa3 Design 47 H2: lead answers use the glossary's words 2026-11-22 00:16:02 +01:00
jschoubben dfbca1458d Design 47 H: split the lead answers; H2's (H-A-373 on) in H2-lead-answers.md 2026-11-22 00:15:30 +01:00
jschoubben 6d90185f49 Design 47 H: H-A-391 the mover entries' index; H-A-392 what H-A-374 changes 2026-11-22 00:14:00 +01:00
jschoubben 149955dbd2 Design 47 H: H-A-388 to H-A-390, the have's run and the declaration's version; a validate step on a changed seat form; §799's shared parts 2026-11-22 00:13:25 +01:00
jschoubben 40ad6a10bf Design 47 H: H-A-387, the artifact registry takes a publish whose reservation names no digest yet 2026-11-22 00:11:30 +01:00
jschoubben ad5284889b Design 47 H: H-A-386, the keep's prefix is _keep/; the runtime's put answer carries the fill 2026-11-22 00:10:25 +01:00
jschoubben cc556c857a Design 47 H: H-A-385, the gate ledger's head and mover entries 2026-11-22 00:08:02 +01:00
jschoubben 48cff82289 Design 47 H: H-A-384, the comment cut with a count, the applied run in the have, drain-bound raises the form; H-A-379 addendum 2026-11-22 00:05:11 +01:00
jschoubben b6d44d1bd6 Design 47 H: H-A-383, the node-engine's taken state names its cap; the baseline gains state.max-mib 2026-11-22 00:04:26 +01:00
jschoubben e6c7bc1d06 Design 47 H: H-A-382, a page marks seen-again after the first page's sequence and hands each kept message 2026-11-22 00:03:45 +01:00
jschoubben d98e61a6e2 Design 47 H: H-A-381, a repeat of a taken ask answers the act's state; ask-taken-bound 2026-11-22 00:02:43 +01:00
jschoubben bc1c1561f3 Design 47 H: H-A-380, the prune helper in a process, the keep's home, the tools' names 2026-11-22 00:02:03 +01:00
jschoubben 032c4319f8 Design 47 H: H-A-378 and H-A-379 read the clock 2026-11-22 00:00:58 +01:00
jschoubben 80745b3e02 Design 47 H: H-A-379, an install's end names the step install 2026-11-22 00:00:32 +01:00
jschoubben 88ea67c7b4 Design 47 H: H-A-378, S8 changes no SDK code; the validator holds the finding events' numbers 2026-11-22 00:00:12 +01:00
jschoubben 781b614100 Design 47 H: H-A-377, drain-bound is a duration text like every time setting 2026-11-21 23:56:11 +01:00
jschoubben 4238e98f0d Design 47 H: H-A-376, the runner's list and show answer a short form by default 2026-11-21 23:52:12 +01:00
jschoubben 268b65e6db Design 47 H: H-A-373 to H-A-375 read the clock; the SDK's refusal is H2's 2026-11-21 23:42:54 +01:00
jschoubben 230d48c3f4 Design 47 H: H-A-373 to H-A-375, every publish names its version; a declared directory mode is applied to an existing directory; a step a node cannot run moves 2026-11-21 23:42:17 +01:00
jschoubben 9f7619d3c4 Design 47 H: H-A-371 and H-A-372, archive-only lanes without Go code; a bundle's publish names its version 2026-11-21 23:23:32 +01:00
jschoubben f59b63e3e2 Design 47 H: H-A-368 to H-A-370, the starved setup's line; a call after the stop; the one settings word 2026-11-21 23:22:24 +01:00
jschoubben b0f8d434e6 Design 47 H: H-A-367, the build-step part's forms 2026-11-21 23:19:53 +01:00
jschoubben 9dea4eefed Design 47 H: H-A-363 to H-A-366, bus test flakes; the node-engine takes once; the definition reader stays strict; a bundle purges 2026-11-21 23:15:26 +01:00
jschoubben 9c9342d8bf Design 47 H: H-A-361 and H-A-362, a pipeline ending failed after a hand-off; the queue settings in the definition 2026-11-21 23:12:51 +01:00
jschoubben b2f2ac7580 Design 47 H: H-A-359a, the bundle's create act exists already 2026-11-21 23:11:15 +01:00
jschoubben 64a927c144 Design 47 H: H-A-359 and H-A-360, a bundle takes once; a module-wide own secret's name and caller 2026-11-21 23:09:32 +01:00
jschoubben 415f28d73c Design 47 H: H-A-358, how drain-bound reaches the unit 2026-11-21 23:05:40 +01:00
jschoubben ee8a7e706a Design 47 H: H-A-357, the derived accept rules' comment 2026-11-21 23:04:50 +01:00
jschoubben ad7f141623 Design 47 H: H-A-355 and H-A-356, run's place, composition-diff's definition, a connection's busiest subscriptions 2026-11-21 23:04:18 +01:00
jschoubben befabda4d1 Design 47 H: H-A-354, where away lands among the seats' error kinds 2026-11-21 23:01:22 +01:00
jschoubben 00059d7325 Design 47 H: H-A-353, who keeps the bundles alive during the drain 2026-11-21 22:49:00 +01:00
jschoubben 6177ae66ac Design 47 H: H-A-352, the form of a seat definition 2026-11-21 22:47:30 +01:00
jschoubben 59864fc478 Design 47 H: H-A-351, how the ask id travels 2026-11-21 22:47:13 +01:00
jschoubben b1cef2c617 Design 47 H: H-A-349 and H-A-350, the H2 prepare's questions answered 2026-11-21 22:38:48 +01:00
jschoubben 9e6ca94df0 Design 47 H: section 10, finding 205 2026-11-21 22:28:41 +01:00
jschoubben bea4380a8b Design 47 H: H-A-348, a new node-engine's first pass restarts the tool runner for an unchanged secret 2026-11-21 22:27:59 +01:00
jschoubben b37cb3985d Design 47 H: H-A-347, the Node build module's tests and the toolchain fallback 2026-11-21 22:26:40 +01:00
jschoubben ad94daa421 Design 47 H: H-A-346, the packet filter group ships before trunk's test races are fixed 2026-11-21 22:23:37 +01:00
jschoubben 87ded62dd1 Design 47 H: H-A-345, the forge token's write verb 2026-11-21 22:18:11 +01:00
jschoubben fbd39168f4 Design 47 H: H-A-344, H2's part after the second look 2026-11-21 22:16:02 +01:00
jschoubben 47515b8730 Design 47 H: H-A-343, the runner's events are waited on by name 2026-11-21 22:11:53 +01:00
jschoubben f2dfc50f8d Design 47 H: section 10, row 204's pointers 2026-11-21 22:10:44 +01:00
jschoubben 05fac9854c Design 47 H: section 10, finding 204 2026-11-21 22:10:11 +01:00
jschoubben 3f9240f731 Design 47 H: H-A-342, a tool runner's restart kills calls in flight 2026-11-21 22:08:54 +01:00
jschoubben 70e333055c Design 47 H: H-A-341, H2's part after the health and events review 2026-11-21 22:06:06 +01:00
jschoubben acf3431207 Design 47 H: H-A-338 to H-A-340, H2's part after three reviews by domain 2026-11-21 22:05:35 +01:00
jschoubben eb5476d319 Design 47 H: H-A-337, a held module's share of merged words 2026-11-21 22:03:40 +01:00
jschoubben fea6f12ebb Design 47 H: H-A-336, a TypeScript bundle's mesh packages are edges before its first build 2026-11-21 22:02:57 +01:00
jschoubben e320b964a9 Design 47 H: section 10, finding 203 2026-11-21 22:01:35 +01:00
jschoubben d444ac1cde Design 47 H: H-A-335, the held-module rule covers every runtime's slice 2026-11-21 21:58:03 +01:00
jschoubben de9f20c0e1 Design 47 H: H-A-333 and H-A-334, journal lines at every said end; H2's part answers 2026-11-21 21:55:48 +01:00
jschoubben 04fb76dd53 Design 47 H: section 10, finding 202 2026-11-21 21:53:54 +01:00
jschoubben a293e235eb Design 47 H: H-A-332, hq merges like every other repository 2026-11-21 21:53:10 +01:00
jschoubben 8e37cfbb21 Design 47 H: section 10, finding 201 2026-11-21 21:49:27 +01:00
jschoubben 94e8564cc2 Design 47 H: section 10, finding 200 2026-11-21 21:45:05 +01:00
jschoubben 916bd46953 Design 47 H: section 10, finding 199 2026-11-21 21:37:07 +01:00
jschoubben f7d35dc1db Design 47 H: H-A-331, the published answer's time and digest are kept from now, absent before 2026-11-21 21:36:03 +01:00
jschoubben a07952e387 Design 47 H: H-A-330, the holder's converged bound stays a named value 2026-11-21 21:35:22 +01:00
jschoubben 3f6a73e0ba Design 47 H: section 10, finding 198 2026-11-21 21:31:22 +01:00
jschoubben e828d8a61f Design 47 H: H-A-329, a validator run by hand reads the seat list the mesh holds 2026-11-21 21:30:49 +01:00
jschoubben 5367dc409f Design 47 H: section 10, finding 197 2026-11-21 21:27:03 +01:00
jschoubben 9b9f528e35 Design 47 H: section 10, finding 196 2026-11-21 21:25:12 +01:00
jschoubben a6e8336958 Design 47 H: section 10, row 195's repository 2026-11-21 21:19:57 +01:00
jschoubben 05f12fce17 Design 47 H: H-A-328 corrected, the seat mesh-builds lives in the delivery repository 2026-11-21 21:19:33 +01:00
jschoubben 8a30d477f2 Design 47 H: section 10, finding 195 2026-11-21 21:19:01 +01:00
jschoubben 2226f10086 Design 47 H: H-A-328, the runner asks the build seat whether a package is published 2026-11-21 21:18:03 +01:00
jschoubben fc31df351a Design 47 H: section 10, finding 194 2026-11-21 21:17:55 +01:00
jschoubben 81734293da Design 47 H: H-A-327, two more module tests that sink a pipeline under load 2026-11-21 21:17:22 +01:00
jschoubben d90ca95119 Design 47 H: section 10, finding 193 2026-11-21 21:16:49 +01:00
jschoubben 775eefcfed Design 47 H: H-A-326, a mover waiting on a publish that already happened is placed at once 2026-11-21 21:15:50 +01:00
jschoubben a2e74c59a1 Design 47 H: H-A-325, the converged answer carries the node's links; a kept allowance names its outward link 2026-11-21 21:13:19 +01:00
jschoubben ed07ee982e Design 47 H: section 10, finding 192 2026-11-21 21:11:22 +01:00
jschoubben 92a2a0c27b Design 47 H: H-A-324, an allowance with no interface never opens an outward link 2026-11-21 21:10:05 +01:00
jschoubben aa0d201b22 Design 47 H: section 10, finding 191 2026-11-21 21:03:42 +01:00
jschoubben 84ed8145e2 Design 47 H: section 10, row 190's pointer 2026-11-21 20:55:55 +01:00
jschoubben adad095288 Design 47 H: section 10, finding 190 2026-11-21 20:55:24 +01:00
jschoubben 2752ed5094 Design 47 H: H-A-322, the stalled bound stays the mesh's five minutes 2026-11-21 20:52:23 +01:00
jschoubben 84757c9f84 Design 47 H: H-A-321, the composition answer's withheld-parts field; the converged answer's found field 2026-11-21 20:51:18 +01:00
jschoubben 0bbd7cc34b Design 47 H: section 10, finding 189 2026-11-21 20:51:00 +01:00
jschoubben edd6cc09a0 Design 47 H: H-A-320, a step's end and an ask's answer are journal lines; a work queue has a consumer; every build seat takes checks 2026-11-21 20:50:19 +01:00
jschoubben 4890b0d945 Design 47 H: section 10, finding 188 2026-11-21 20:49:35 +01:00
jschoubben 229a207faf Design 47 H: H-A-319, a port admitted only with a source match is a source-bound port 2026-11-21 20:49:32 +01:00
jschoubben c6fb61cfbc Design 47 H: H-A-318, allowed asks converged again when it holds no answer 2026-11-21 20:48:48 +01:00
jschoubben 05db1775e0 Design 47 H: section 10, finding 187 2026-11-21 20:47:12 +01:00
jschoubben 1f8d3cda53 Design 47 H: H-A-317, the allowances state's keys carry the node; the claim says the event 2026-11-21 20:45:53 +01:00
jschoubben 6a9b0e5d07 Design 47 H: section 10, finding 186 2026-11-21 20:44:04 +01:00
jschoubben 73b6f775be Design 47 H: section 10, finding 185 2026-11-21 20:42:50 +01:00
jschoubben 8430f78052 Design 47 H: H-A-315 and H-A-316, the packet filter's design after the security review; the converged read verb 2026-11-21 20:40:40 +01:00
jschoubben 012ff6ef62 Design 47 H: H-A-313 and H-A-314, the stalled pipeline's journal line; the packet filter's design after the seams review 2026-11-21 20:39:52 +01:00
jschoubben 76ad10f43d Design 47 H: H-A-312, allow refused on an adopted node; expired allowances removed at the holder's start 2026-11-21 20:38:50 +01:00
jschoubben 5e88a37c28 Design 47 H: section 10, finding 184 2026-11-21 20:37:41 +01:00
jschoubben 336b9024b8 Design 47 H: H-A-311, a placing cut by a concurrent write is done again; a late progress still places; a stalled pipeline is unhealthy 2026-11-21 20:36:57 +01:00
jschoubben 30fcc6f9af Design 47 H: section 10, finding 183 2026-11-21 20:35:40 +01:00
jschoubben 3dcf997d9e Design 47 H: H-A-310, a seat's new verbs are required from the start within one delivery group 2026-11-21 20:33:36 +01:00
jschoubben 46f34e10b2 Design 47 H: H-A-309, a tool's reader tolerates fields it does not know 2026-11-21 20:33:14 +01:00
jschoubben 79ecc2bda8 Design 47 H: H-A-308, an allowance's identity, its expiry, the verbs' answers 2026-11-21 20:32:16 +01:00
jschoubben 84e8cb4c38 Design 47 H: section 10, finding 182 2026-11-21 20:31:01 +01:00
jschoubben 113eb3a9ce Design 47 H: H-A-307, an unanswered allowed read keeps the loaded filter; allowances on converged nodes only 2026-11-21 20:29:27 +01:00
jschoubben 885b1c54fc Design 47 H: section 10, finding 181 2026-11-21 20:28:50 +01:00
jschoubben 713c0d3fba Design 47 H: H-A-306, a withheld part is every input a compose asks and does not get; a held module's slice is what runs 2026-11-21 20:27:54 +01:00
jschoubben 3a41a9aeea Design 47 H: the relayed decision's time 2026-11-21 20:27:39 +01:00
jschoubben 18971aaa85 Design 47 H: section 10, finding 180 2026-11-21 20:26:54 +01:00
jschoubben 77277f1c2d Design 47 H: H-A-305, one renderer: the node-engine renders the allowances it asks of the holder 2026-11-21 20:26:44 +01:00
jschoubben 492ac0ab28 Design 47 H: H-A-304, the packet filter's control verbs 2026-11-21 20:25:24 +01:00
jschoubben 8232c5e1d8 Design 47 H: H-A-303, a compose with a part withheld changes nothing 2026-11-21 20:20:47 +01:00
jschoubben b9e8aaa7af Design 47 H: section 10, finding 179 2026-11-21 20:19:50 +01:00
jschoubben a1b26fe7da Design 47 H: H-A-302, one composition per machine, module and fingerprint; an older run never overwrites a newer 2026-11-21 20:18:36 +01:00
jschoubben c27f280237 Design 47 H: section 10, finding 178 2026-11-21 20:04:00 +01:00
jschoubben 6837cc049a Design 47 H: H-A-301, a build whose source fetch meets the forge away is asked again 2026-11-21 20:03:01 +01:00
jschoubben ca30548c08 Design 47 H: section 10, finding 177 2026-11-21 19:52:42 +01:00
jschoubben cbe43334ee Design 47 H: H-A-300, an act that fails while a part is away is owed again 2026-11-21 19:50:06 +01:00
jschoubben be2610e816 Design 47 H: section 10, finding 176 2026-11-21 19:48:04 +01:00
jschoubben 916a8a5c5e Design 47 H: H-A-299, records and stores that outgrow the bus; the deliveries read 2026-11-21 19:47:06 +01:00
jschoubben 3a9385b772 Design 47 H: section 10, finding 175 2026-11-21 19:44:03 +01:00
jschoubben 1316151f07 Design 47 H: H-A-298, a module moves only when its own inputs change; a take-in says what it waits on 2026-11-21 19:42:54 +01:00
jschoubben ed35da552f Design 47 H: section 10, finding 174 2026-11-21 19:35:55 +01:00
jschoubben 9b66bddbb6 Design 47 H: H-A-297, the indexer's dry run writes nothing the trunk reads 2026-11-21 19:35:09 +01:00
jschoubben 2aa9a96990 Design 47 H: role names only (hq is public) 2026-11-21 19:33:29 +01:00
jschoubben ed30618ffc Design 47 H: section 10, findings 172 and 173; the freeze is lifted 2026-11-21 19:32:25 +01:00
jschoubben 81cb834991 Design 47 H: section 10, finding 171 2026-11-21 19:31:10 +01:00
jschoubben 7d2715aef9 Design 47 H: section 10, finding 170 2026-11-21 19:28:33 +01:00
jschoubben a339a34819 Design 47 H: H-A-296, no responders is a wait, not an end 2026-11-21 19:27:53 +01:00
jschoubben 8b7a5fc2c9 Design 47 H: H-A-295, the teller's ask-again for want of room stands until A-424 is built 2026-11-21 19:25:54 +01:00
jschoubben fb056e6551 Design 47 H: section 10, row 169's release 2026-11-21 19:23:32 +01:00
jschoubben 81fa1ee4e0 Design 47 H: section 10, finding 169 2026-11-21 19:23:01 +01:00
jschoubben ae4211ca48 Design 47 H: section 10, row 168's time 2026-11-21 19:17:48 +01:00
jschoubben 0672f6e215 Design 47 H: section 10, finding 168 2026-11-21 19:17:13 +01:00
jschoubben 33d2647985 Design 47 H: H-A-294, a test that needs tooling its step lacks says NOT RUN, and the need is declared 2026-11-21 19:15:38 +01:00
jschoubben 571a19c2de Design 47 H: section 10, finding 167 2026-11-21 19:14:28 +01:00
jschoubben b1d2384b50 Design 47 H: section 10, finding 166 2026-11-21 19:07:29 +01:00
jschoubben 27c77b6e5b Design 47 H: section 10, finding 165 2026-11-21 19:06:38 +01:00
jschoubben e8c3cc9db3 Design 47 H: section 10, read times in rows 163 and 164 2026-11-21 19:04:21 +01:00
jschoubben 169adbc8b0 Design 47 H: section 10, finding 164 2026-11-21 19:02:05 +01:00
jschoubben a2604d7c87 Design 47 H: section 10, finding 163 2026-11-21 19:00:36 +01:00
jschoubben f0bed6acc3 Design 47 H: section 10, finding 162 2026-11-21 18:55:44 +01:00
jschoubben 4a39cfc912 Design 47 H: H-A-293, a one-page read past its page answers capped; retire per series 2026-11-21 18:55:25 +01:00
jschoubben 6535facf51 Design 47 H: H-A-292, a module's own tool may read its own state in one page 2026-11-21 18:54:30 +01:00
jschoubben e7761a6b30 Design 47 H: section 10, finding 161 2026-11-21 18:50:05 +01:00
jschoubben 9e8bb7917d Design 47 H: section 10, finding 160 2026-11-21 18:29:47 +01:00
jschoubben 933ee50a41 Design 47 H: H-A-291, a start publishes only each module's newest reservation; a live enqueue cuts a start list short 2026-11-21 18:28:47 +01:00
jschoubben b105e606bc Design 47 H: section 10, the cancel's time in rows 156 and 159 2026-11-21 18:26:05 +01:00
jschoubben afc648dd18 Design 47 H: section 10, finding 159 2026-11-21 18:25:32 +01:00
jschoubben e469bb9a8b Design 47 H: section 10, finding 158 2026-11-21 18:17:36 +01:00
jschoubben 855c703f1d Design 47 H: H-A-290, the builder's publish queue: live asks first, no publish of a withdrawn build, one listing per pass 2026-11-21 18:16:31 +01:00
jschoubben 40cb4313f0 Design 47 H: section 10, finding 157 2026-11-21 18:15:36 +01:00
jschoubben b6a2296c71 Design 47 H: H-A-289, the end's write waits on no other part 2026-11-21 18:14:40 +01:00
jschoubben 9528063e4d Design 47 H: section 10, finding 156 2026-11-21 18:09:59 +01:00
jschoubben 949e4915ca Design 47 H: H-A-288, a pipeline with nothing left to do ends at once 2026-11-21 18:09:02 +01:00
jschoubben 422e2c7361 Design 47 H: section 10, finding 155 2026-11-21 18:05:20 +01:00
jschoubben 55828ceeec Design 47 H: section 10, finding 154 2026-11-21 18:03:05 +01:00
jschoubben 4f4914407f Design 47 H: H-A-287, a kept mover's validate ask joins the pipeline's validate run 2026-11-21 18:01:03 +01:00
jschoubben 5220fa2266 Design 47 H: H-A-286, a kept mover's ask ids and entry come from its kept revision 2026-11-21 17:54:00 +01:00
jschoubben 08cb26c6df Design 47 H: H-A-285, the kept revisions ride in the pipeline record 2026-11-21 17:41:35 +01:00
jschoubben 72fab0f717 Design 47 H: H-A-284, the kept mover's steps and its entry's revision 2026-11-21 17:39:19 +01:00
jschoubben acc94fb9c2 Design 47 H: section 10, finding 153 2026-11-21 17:36:56 +01:00
jschoubben 5f472c1f40 Design 47 H: H-A-283, a re-pin of the same source keeps a mover in its pipeline; its build is asked again there 2026-11-21 17:35:44 +01:00
jschoubben df434bb4f2 Design 47 H: section 10, finding 152 2026-11-21 17:06:11 +01:00
jschoubben f9baca9750 Design 47 H: section 10, finding 151 2026-11-21 16:55:32 +01:00
jschoubben 3a6689a378 Design 47 H: section 10, finding 150 2026-11-21 16:50:25 +01:00
jschoubben a1d073139b Design 47 H: section 10, finding 149 2026-11-21 16:43:48 +01:00
jschoubben 20fbb3acbc Design 47 H: H-A-280 and H-A-281, a published read once; the event hub pulls small batches and keeps slow handlers alive 2026-11-21 16:42:14 +01:00
jschoubben f34301e08d Design 47 H: section 10, finding 148 2026-11-21 16:14:06 +01:00
jschoubben da88594ae3 Design 47 H: section 10, findings 146 and 147 2026-11-21 15:59:41 +01:00
jschoubben 272fe8bdb5 Design 47 H: H-A-279, a build whose number a registry holds elsewhere is built again at the next free number 2026-11-21 15:53:36 +01:00
jschoubben d128521ae0 Design 47 H: H-A-278, a moved build's package whose content names its version is made again for the new number 2026-11-21 15:52:00 +01:00
jschoubben 8c79c3564c Design 47 H: H-A-277, a passed mover with no version yet holds its tier; the end said again for a passed pipeline only; a lost say said again 2026-11-21 15:50:46 +01:00
jschoubben a13f73c157 Design 47 H: section 10, finding 145 2026-11-21 15:47:29 +01:00
jschoubben 6f36356298 Design 47 H: H-A-274 to H-A-276, a held record ends a publish; a held number is never reserved; an out-of-range placement is said 2026-11-21 15:46:14 +01:00
jschoubben c6530b0686 Design 47 H: H-A-273, a mover whose version arrives late joins the tier progress at its tier 2026-11-21 15:41:45 +01:00
jschoubben b1b1281481 Design 47 H: H-A-272, the unheard bound: the builder's one durable, pending plus unacknowledged, a hundred 2026-11-21 15:34:21 +01:00
jschoubben 23813706c9 Design 47 H: H-A-271, the builder's index keys by digest and by version; no scan on a miss 2026-11-21 15:33:31 +01:00
jschoubben f5f0f843ab Design 47 H: section 10, finding 144 2026-11-21 15:32:57 +01:00
jschoubben 0d489ff1a7 Design 47 H: H-A-267 to H-A-270, the four faults behind proof 2's failed pipeline 2026-11-21 15:31:15 +01:00
jschoubben 0b6b20c18d Design 47 H: section 10, row 143 corrected 2026-11-21 15:22:32 +01:00
jschoubben 842f48a12e Design 47 H: section 10, finding 143 2026-11-21 15:21:58 +01:00
jschoubben 0b48f25e43 Design 47 H: section 10, finding 142 2026-11-21 14:36:14 +01:00
jschoubben c71dcfa94f Design 47 H: section 10, finding 141 2026-11-21 13:32:03 +01:00
jschoubben 69ec1108d2 Design 47 H: section 10, findings 139 and 140 2026-11-21 13:24:23 +01:00
jschoubben 103189b16d Design 47 H: H-A-266, the branch when the siblings' first watched branches differ 2026-11-21 13:15:25 +01:00
jschoubben 5785a8aea9 Design 47 H: H-A-265, registering at a kept revision: a pending proposal, the seed's left-out, the branch; the finding's end 2026-11-21 13:14:35 +01:00
jschoubben 2a430dd9af Design 47 H: H-A-264, register at every kept trunk revision and at start, only while registrations are held 2026-11-21 13:06:10 +01:00
jschoubben 6490702de2 Design 47 H: H-A-263, the policy a module entering the graph gets 2026-11-21 13:01:06 +01:00
jschoubben 00b76d16eb Design 47 H: section 10, finding 138 2026-11-21 12:59:39 +01:00
jschoubben 11ac7880fc Design 47 H: H-A-262, a module that enters the trunk's module graph is registered at its take-in 2026-11-21 12:58:22 +01:00
jschoubben e268980db1 Design 47 H: section 10, finding 137 2026-11-21 12:43:08 +01:00
jschoubben b8d2d2c174 Design 47 H: section 10, finding 136 2026-11-21 12:29:17 +01:00
jschoubben 0a9dc7de39 Design 47 H: section 10, findings 134 and 135 2026-11-21 12:27:30 +01:00
jschoubben 00e6123043 Design 47 H: H-A-261, no want before a revision is kept; the full-store verdict is the pass's own 2026-11-21 12:19:16 +01:00
jschoubben 811d7415ab Design 47 H: section 10, findings 132 and 133 2026-11-21 12:07:43 +01:00
jschoubben cabd0f760f Design 47 H: section 10, rows 125, 128 and 129 amended 2026-11-21 12:04:19 +01:00
jschoubben 867182bf73 Design 47 H: H-A-260, a pass that cannot judge its builds raises artifact-builds-unread 2026-11-21 12:03:54 +01:00
jschoubben 5f734d2958 Design 47 H: section 10, findings 130 and 131 2026-11-21 12:03:36 +01:00
jschoubben 43628f09a4 Design 47 H: H-A-259, the assigner's pass never waits on the keeping of revisions 2026-11-21 12:02:50 +01:00
jschoubben b727fb1bce Design 47 H: H-A-258, a build's end comes from the builder's log the pass already reads; an unread end holds the pass 2026-11-21 12:02:31 +01:00
jschoubben 71db57e072 Design 47 H: H-A-257, the followed view of the builds: its first view is the watch's handover; a re-watch replaces the view 2026-11-21 12:00:37 +01:00
jschoubben 7c266b396a Design 47 H: section 10, findings 127 to 129 2026-11-21 11:58:22 +01:00
jschoubben 441e62a01e Design 47 H: H-A-256, the assigner writes a pipeline's wants on its pipeline-ended event 2026-11-21 11:57:10 +01:00
jschoubben c2f14090df Design 47 H: H-A-255, the sweep reads the builds from a followed view, not pages; the cursor by sequence is H2 2026-11-21 11:56:49 +01:00
jschoubben d411be7291 Design 47 H: H-A-254, a paged read of a state continues from its cursor 2026-11-21 11:55:20 +01:00
jschoubben 535fdc99f5 Design 47 H: section 10, findings 125 and 126 2026-11-21 11:49:40 +01:00
jschoubben a346ea769d Design 47 H: H-A-253, a retired entry may name the scope its keys were written under 2026-11-21 11:49:35 +01:00
jschoubben e3db5eed6d Design 47 H: H-A-252, a validate end is matched by its ask alone and ends every mover's validate step 2026-11-21 11:48:17 +01:00
jschoubben cfeee0cf1d Design 47 H: H-A-250 and H-A-251, the artifact sweep reads once per pass; the tool runner binds a state once 2026-11-21 11:47:49 +01:00
jschoubben e1ab3f0c0b Design 47 H: section 10, findings 123 and 124 2026-11-21 11:45:35 +01:00
jschoubben 50d65aa554 Design 47 H: H-A-249, a retired entry may name the ids it once wrote under a kind another writer owns 2026-11-21 11:41:46 +01:00
jschoubben 525601d12b Design 47 H: H-A-248, a stale build past the withdrawn record's bound keeps the plain words 2026-11-21 11:37:21 +01:00
jschoubben ce8b413ba3 Design 47 H: H-A-247, the SDK parts' kinds are the writer's too; the daemon's unanswered calls get a kind of its own; a retired kind is cleared by its last owner 2026-11-21 11:36:53 +01:00
jschoubben 3886cb46bf Design 47 H: H-A-246, H-A-245 waits for the git seat's tags answer to carry each tag's commit (H2) 2026-11-21 11:34:06 +01:00
jschoubben 051132df3c Design 47 H: section 10, finding 122 2026-11-21 11:32:22 +01:00
jschoubben 8f66565ea8 Design 47 H: section 10, row 117 amended, findings 120 and 121 2026-11-21 11:30:05 +01:00
jschoubben 85345a7c05 Design 47 H: H-A-244 and H-A-245, a moved mover leaves a waiting pipeline; a tagged number is never reused 2026-11-21 11:29:40 +01:00
jschoubben 830850d40c Design 47 H: section 10, findings 118 and 119 2026-11-21 11:29:14 +01:00
jschoubben 89b5ac656a Design 47 H: H-A-243, a seat that says no first word: the ask is put again when its holder starts; one long silent bound 2026-11-21 11:28:14 +01:00
jschoubben 83d5655b81 Design 47 H: H-A-242, a held writer seeds only the kinds it owns; no manifest field 2026-11-21 11:25:08 +01:00
jschoubben 22cef506d2 Design 47 H: H-A-241, the bound is on the holder's first word, never on the work's length 2026-11-21 11:24:28 +01:00
jschoubben 5482efebf6 Design 47 H: section 10, finding 117 2026-11-21 11:22:33 +01:00
jschoubben e7db0df313 Design 47 H: H-A-240, a module declares every finding kind it raises, and a test holds the code to it 2026-11-21 11:21:28 +01:00
jschoubben d3e21dbc94 Design 47 H: section 10, findings 115 and 116 2026-11-21 11:12:13 +01:00
jschoubben 99c3081d9b Design 47 H: H-A-239, the warrant ask's expiry bounds; the router's standing is read, not waited for 2026-11-21 11:11:22 +01:00
jschoubben 9b23a021e5 Design 47 H: H-A-238, the bound on an ask: its setting, finding, first word, scope and keeping 2026-11-21 11:09:23 +01:00
jschoubben 8029dd90d6 Design 47 H: section 10, findings 112 to 114 2026-11-21 11:08:40 +01:00
jschoubben b8d5b03b20 Design 47 H: H-A-237, the keeper's warrant asks at approve level until a channel carries destroy; an ask the router holds is said 2026-11-21 11:07:36 +01:00
jschoubben 71548ccf77 Design 47 H: H-A-236, a rerun of the validate or composition step finds the shared ask 2026-11-21 11:05:57 +01:00
jschoubben 260e2c0efc Design 47 H: H-A-235, a step ask nobody answers within its bound is asked again, then ends could-not-run 2026-11-21 11:00:39 +01:00
jschoubben 73e4379734 Design 47 H: section 10, row 111 corrected 2026-11-21 03:36:25 +01:00
jschoubben 597d9a6266 Design 47 H: section 10, finding 111 2026-11-21 03:35:58 +01:00
jschoubben 12424178ed Design 47 H: H-A-234, the finding's scope is merge; the contract's comment waits 2026-11-21 02:52:10 +01:00
jschoubben 60300ed8aa Design 47 H: H-A-233, a failed publish raises the finding packages-not-published 2026-11-21 02:45:48 +01:00
jschoubben 6bd9158fc0 Design 47 H: section 10, findings 109 and 110 2026-11-21 02:43:22 +01:00
jschoubben e7921f9485 Design 47 H: H-A-232, a repository's packages are those in the merge's tree; a gone directory is said not-found 2026-11-21 02:42:24 +01:00
jschoubben 7f030aa4ae Design 47 H: section 10, row 106 takes in H-A-230 and H-A-231 2026-11-21 02:27:06 +01:00
jschoubben 9bf5b205de Design 47 H: section 10, finding 108 2026-11-21 02:26:29 +01:00
jschoubben 9d4a013f0f Design 47 H: H-A-231, the keeper keeps only the old-section entries it made 2026-11-21 02:18:05 +01:00
jschoubben dc1b2884af Design 47 H: H-A-230, every manifest's old-section entries are asked for; the keeper makes none of them 2026-11-21 02:16:37 +01:00
jschoubben d0babbc3b2 Design 47 H: section 10, findings 106 and 107 2026-11-21 02:14:29 +01:00
jschoubben dfbc7d8054 Design 47 H: H-A-229, a foundation part's old-section entry is asked for, not an orphan 2026-11-21 02:13:42 +01:00
jschoubben e678e6f25e Design 47 H: H-A-228, the receiver's fill sum lives in the kept transfer 2026-11-21 02:04:22 +01:00
jschoubben 345a7afbbf Design 47 H: section 10, finding 105, the glossary's word 2026-11-21 01:59:18 +01:00
jschoubben 6a519a2579 Design 47 H: section 10, finding 105 2026-11-21 01:59:04 +01:00
jschoubben 48c4a7e6ef Design 47 H: section 10, finding 104 2026-11-21 01:55:29 +01:00
jschoubben dfe0963bbf Design 47 H: H-A-227, a fill is read from the store's own figures, never by listing it 2026-11-21 01:54:46 +01:00
jschoubben b3561676c8 Design 47 H: section 10, finding 103 2026-11-21 01:52:55 +01:00
jschoubben 8ce66217cf Design 47 H: section 10, row 101 by H-A-226 2026-11-21 01:39:59 +01:00
jschoubben e7440e3dea Design 47 H: H-A-226, a withdrawn number stays a gap; the withdrawn list is bounded 2026-11-21 01:39:14 +01:00
jschoubben 60cb94a4f9 Design 47 H: section 10, row 101 by the builder's build 2026-11-21 01:38:04 +01:00
jschoubben 5d46e2f48b Design 47 H: section 10, finding 102 2026-11-21 01:33:30 +01:00
jschoubben 48c7e35bd1 Design 47 H: section 10, finding 101 2026-11-21 01:32:35 +01:00
jschoubben 0569f40699 Design 47 H: H-A-225, a reservation is kept for the same fingerprint; a taken-over build is withdrawn 2026-11-21 01:31:38 +01:00
jschoubben 9052e5e7e0 Design 47 H: section 10, finding 100 2026-11-21 01:24:44 +01:00
jschoubben 63dec8f1da Design 47 H: H-A-224, a same-repository module named only by a replace is a requirement 2026-11-21 01:24:08 +01:00
jschoubben 3304edcfa9 Design 47 H: section 10, row 86 both build modules 2026-11-21 01:21:56 +01:00
jschoubben b7c8f62fa5 Design 47 H: section 10, rows 97 and 99 2026-11-21 01:21:32 +01:00
jschoubben 99fb1beeed Design 47 H: section 10, finding 98 2026-11-21 01:17:46 +01:00
jschoubben 19b1437317 Design 47 H: section 10, finding 97 2026-11-21 01:12:53 +01:00
jschoubben d6f1fae71a Design 47 H: section 10, finding 96 2026-11-21 01:09:19 +01:00
jschoubben 3bd6442d46 Design 47 H: H-A-223, a moved mover leaves a running pipeline too 2026-11-21 01:08:36 +01:00
jschoubben 2e7269f1a1 Design 47 H: section 10, finding 95 2026-11-21 01:04:56 +01:00
jschoubben bb344445f7 Design 47 H: H-A-222, the revision verb answers the store; the builder's picture holds by number 2026-11-21 01:04:21 +01:00
jschoubben d34fa2f5d4 Design 47 H: section 10, finding 94 2026-11-21 01:00:34 +01:00
jschoubben 86df23d202 Design 47 H: section 10, finding 93 2026-11-21 00:46:07 +01:00
jschoubben 2be59f994d Design 47 H: section 10, finding 90 by H-A-221 2026-11-21 00:23:34 +01:00
jschoubben 0c25abad86 Design 47 H: H-A-221, the runner's subjects say the revision 2026-11-21 00:23:02 +01:00
jschoubben 1b8ab16b37 Design 47 H: section 10, finding 90 by H-A-220 2026-11-21 00:16:31 +01:00
jschoubben 2baf2f614e Design 47 H: H-A-220, a build started from the picture takes its revision from the picture 2026-11-21 00:15:39 +01:00
jschoubben 91d84ffa57 Design 47 H: section 10, finding 90 by H-A-219 2026-11-21 00:03:49 +01:00
jschoubben d7eae5e9ba Design 47 H: H-A-219, a step ask's revision is the catalog revision number 2026-11-20 23:58:32 +01:00
jschoubben 9613eedd78 Design 47 H: section 10, finding 90 by H-A-218 2026-11-20 23:56:15 +01:00
jschoubben 51a98841f7 Design 47 H: H-A-218, a publish names the revision it was built from 2026-11-20 23:55:29 +01:00
jschoubben 81de0c9e3b Design 47 H: section 10, finding 92 2026-11-20 23:49:22 +01:00
jschoubben 976f2942ad Design 47 H: H-A-217, every recompute that moves a fingerprint keeps a revision 2026-11-20 23:48:33 +01:00
jschoubben eb433bfcd6 Design 47 H: H-A-216, the assigner carries a pipeline's source 2026-11-20 23:41:20 +01:00
jschoubben c71469e73b Design 47 H: section 10, finding 90 by H-A-215 2026-11-20 23:41:04 +01:00
jschoubben e4d1874f74 Design 47 H: H-A-215, the call's kind is a field of its own 2026-11-20 23:40:32 +01:00
jschoubben 6b6a49c72e Design 47 H: H-A-214, the revision verb's source input 2026-11-20 23:39:31 +01:00
jschoubben 6d871ebecd Design 47 H: section 10, finding 91 2026-11-20 23:38:56 +01:00
jschoubben 2025673216 Design 47 H: H-A-214, a take-in again covers the trunk; pipeline-wanted names the revision 2026-11-20 23:37:48 +01:00
jschoubben d9ecb20c37 Design 47 H: section 10, finding 90 2026-11-20 23:21:26 +01:00
jschoubben 0e6b7f97be Design 47 H: H-A-213, revisions are the indexer's numbers; a release revision starts one pipeline 2026-11-20 23:20:39 +01:00
jschoubben d07dc5aad6 Design 47 H: H-A-212, the re-pin revision carries entries; the runner keeps starting a publish's pipelines 2026-11-20 23:17:07 +01:00
jschoubben 4463e40ac1 Design 47 H: section 10, finding 89 2026-11-20 23:17:02 +01:00
jschoubben 98f04757fd Design 47 H: the pin rule as a specification with its gap table (H1) 2026-11-20 23:15:37 +01:00
jschoubben e4c35b5799 Design 47 H: H-A-211, a re-pin is taken in as a catalog revision of the same source 2026-11-20 23:14:37 +01:00
jschoubben 30d83353ca Design 47 H: section 10, finding 88 by H-A-210 2026-11-20 23:12:20 +01:00
jschoubben d7d18ef084 Design 47 H: H-A-210, a take-in again recomputes the modules state as a re-pin does 2026-11-20 23:11:42 +01:00
jschoubben 2a5a741d72 Design 47 H: H-A-208, the glossary's word 2026-11-20 23:10:12 +01:00
jschoubben b951ffadca Design 47 H: H-A-209, a take-in again is an indexer-owned revision 2026-11-20 23:09:46 +01:00
jschoubben bb10849699 Design 47 H: section 10, finding 88, the glossary's word 2026-11-20 23:09:35 +01:00
jschoubben bab47e7e4a Design 47 H: section 10, finding 88 2026-11-20 23:09:19 +01:00
jschoubben a7b876c109 Design 47 H: H-A-208, a repository is taken in again by a tool 2026-11-20 23:08:12 +01:00
jschoubben dc55dea577 Design 47 H: section 10, finding 87 2026-11-20 23:05:24 +01:00
jschoubben 68f42b8e62 Design 47 H: H-A-207, a held test step takes the pins its build reports 2026-11-20 23:02:35 +01:00
jschoubben 7030acf5ff Design 47 H: section 10, findings 84-86 2026-11-20 22:56:46 +01:00
jschoubben f950b98524 Design 47 H: H-A-206, a test step waits for its pins as the build does 2026-11-20 22:56:04 +01:00
jschoubben 853396c547 Design 47 H: H-A-205, the builder's picture holds every kept revision 2026-11-20 22:55:37 +01:00
jschoubben eb9a6ef356 Design 47 H: section 10, findings 81-83 2026-11-20 22:55:29 +01:00
jschoubben f977c0e232 Design 47 H: H-A-204, an entry names every requirement, pinned or waiting; a publish re-pins every entry 2026-11-20 22:54:39 +01:00
jschoubben d3849e37ce Design 47 H: H-A-203, every step ask carries the entry's pins 2026-11-20 22:51:50 +01:00
jschoubben 4262ceca03 Design 47 H: section 10, findings 76-80 2026-11-20 22:35:33 +01:00
jschoubben 878d09cadb Design 47 H: H-A-202, the entry's form stays; the build module derives the same-repository tree 2026-11-20 22:26:32 +01:00
jschoubben 93b38cab6b Design 47 H: section 10, finding 75 2026-11-20 22:17:03 +01:00
jschoubben 3a9739da9a Design 47 H: section 10, findings 72-74 2026-11-20 22:14:10 +01:00
jschoubben 8105e2602b Design 47 H: H-A-201, the entry pins every requirement of the module graph 2026-11-20 22:13:13 +01:00
jschoubben 0e9f8751bf Design 47 H: H-A-200, hand-written helpers of a seat live in its client 2026-11-20 22:12:18 +01:00
jschoubben f67f738c27 Design 47 H: H-A-199, a step's paths may leave the module's directory, never the repository 2026-11-20 22:12:10 +01:00
jschoubben 382bfb7739 Design 47 H: H-A-198, a package artifact's tree holds its same-repository requirements 2026-11-20 22:08:24 +01:00
jschoubben 9925385b24 Design 47 H: H-A-197, every pull loop claims through the SDK 2026-11-20 22:05:49 +01:00
jschoubben b1fe11c6b1 Design 47 H: section 10, cause of 68 2026-11-20 22:01:27 +01:00
jschoubben 4bdc4983b8 Design 47 H: H-A-196, a process pulls a durable once 2026-11-20 22:00:48 +01:00
jschoubben 4866f7991d Design 47 H: H-A-195, what the grants holder keeps of the catalog 2026-11-20 21:46:32 +01:00
jschoubben c892f927f6 Design 47 H: H-A-194, the builder reads what is published before it waits 2026-11-20 21:45:43 +01:00
jschoubben 3c6b24fe0c Design 47 H: H-A-193, the grants holder learns the newest revision from the event 2026-11-20 21:40:39 +01:00
jschoubben 63975a67f8 Design 47 H: section 10, causes of 69 and 70 2026-11-20 21:35:20 +01:00
jschoubben d2ccf4f3bd Design 47 H: section 10, findings 62-71 2026-11-20 21:31:31 +01:00
jschoubben 9c61151f1f Design 47 H: H-A-192, the builder never computes a pin 2026-11-20 21:29:44 +01:00
jschoubben edc44abc20 Design 47 H: H-A-190 a step-log entry names its mover; H-A-191 list's counts 2026-11-20 21:19:16 +01:00
jschoubben 93c7714c0d Design 47 H: H-A-189, a mover's unlogged entries live under its mover key; list answers records 2026-11-20 21:17:57 +01:00
jschoubben a3c48b85d9 Design 47 H: H-A-188, a package artifact's series is its module's version series 2026-11-20 21:03:26 +01:00
jschoubben 2c2ab61963 Design 47 H: H-A-187, a pipeline's steps live one key per mover 2026-11-20 20:52:42 +01:00
jschoubben 1b71bebd65 Design 47 H: H-A-186, an imported mesh package is a declared artifact of its module 2026-11-20 20:49:46 +01:00
jschoubben 8d52383a9b Design 47 H: H-A-185, the series a module accepts is the manifest's 2026-11-20 20:11:39 +01:00
jschoubben 6570469aeb Design 47 H: H-A-184, the pin stays within the series the module accepts 2026-11-20 20:06:17 +01:00
jschoubben 0d66e02c72 Design 47 H: H-A-183, a pin is the version the registry published for that package path 2026-11-20 20:02:51 +01:00
jschoubben 1065d133d7 Design 47 H: section 10, findings of H1's live run (18:40 to 19:50) 2026-11-20 19:48:31 +01:00
jschoubben 71018a842a Design 47 H: H-A-182, performed's value names the act's pull request 2026-11-20 19:32:58 +01:00
jschoubben 28a28283c6 Design 47 H: H-A-181, performed keeps the outcome; the act stays in the gate's stream 2026-11-20 19:31:57 +01:00
jschoubben d05384d696 Design 47 H: H-A-180, a hold for a failed restore point whose cause is gone 2026-11-20 19:25:01 +01:00
jschoubben 6fe6d93fed Design 47 H: H-A-179, the composition step of a module no machine holds 2026-11-20 19:03:53 +01:00
jschoubben cf0ac158a7 Design 47 H: H-A-178, the restore point before the placements are read; the finding's id 2026-11-20 19:00:55 +01:00
jschoubben 7b96a256f2 Design 47 H: H-A-177, a restore point where no holder of the recovery seat is placed 2026-11-20 18:47:33 +01:00
jschoubben 4151bf1d17 Design 47 H: H-A-158 says the tool runner 2026-11-20 18:40:25 +01:00
jschoubben bc798a4af0 Design 47 H: section 10, findings of H1's live run (16:40 to 18:40) 2026-11-20 18:40:04 +01:00
jschoubben fa7709003d Design 47 H: H-A-176, what a cycle ends and how the pipeline then ends 2026-11-20 18:14:05 +01:00
jschoubben ca3680f4fc Design 47 H: H-A-175, a cycle among a pipeline's unplaced movers ends it failed 2026-11-20 18:09:59 +01:00
jschoubben 84e2514df5 Design 47 H: H-A-174, a tier-late pipeline-wanted frees nothing 2026-11-20 18:00:48 +01:00
jschoubben 21297155a4 Design 47 H: H-A-173, a release pin only for a released mover, freed only by a newer release of it 2026-11-20 17:55:58 +01:00
jschoubben 84feb62eda Design 47 H: H-A-172, pins are in every form's fingerprint 2026-11-20 17:45:47 +01:00
jschoubben f7c721a015 Design 47 H: H-A-171, a mover waiting on a publish at the end judgement 2026-11-20 17:45:33 +01:00
jschoubben 87b43ec8e2 Design 47 H: H-A-170, the release pin's record and what frees it 2026-11-20 17:42:36 +01:00
jschoubben 537327482d Design 47 H: H-A-169, the finding of an unhandled event 2026-11-20 17:41:03 +01:00
jschoubben 1858e92fa9 Design 47 H: H-A-168, a release pins the revision its entry lives in 2026-11-20 17:40:44 +01:00
jschoubben 95e9ae4e5b Design 47 H: H-A-167, a re-pin moves the fingerprint; the pin is always the newest release 2026-11-20 17:40:12 +01:00
jschoubben ad2ecbcc84 Design 47 H: H-A-166, a view reader hears an event on its bare subject too 2026-11-20 17:37:45 +01:00
jschoubben 541defcd78 Design 47 H: H-A-165, an unpinned package: the builder waits for its release, the indexer re-pins 2026-11-20 17:32:48 +01:00
jschoubben f0771e6f06 Design 47 H: H-A-164, end-again is a verb of the seat mesh-pipeline-runner 2026-11-20 17:31:13 +01:00
jschoubben 42e4d68e4a Design 47 H: H-A-163, a pipeline ends failed as soon as it can no longer pass 2026-11-20 17:29:45 +01:00
jschoubben c6dfd740af Design 47 H: H-A-162, a run's build step ask names no source 2026-11-20 17:26:59 +01:00
jschoubben f08d610999 Design 47 H: H-A-161, a package is pinned by its released version, never by a commit 2026-11-20 17:26:03 +01:00
jschoubben 8436603719 Design 47 H: H-A-160, every re-serve keeps unchanged subscriptions 2026-11-20 17:24:36 +01:00
jschoubben ce2dd49809 Design 47 H: H-A-159, the builder numbers nothing of its own 2026-11-20 17:22:46 +01:00
jschoubben 333f6f9798 Design 47 H: H-A-158, the tool runner re-serves a membership without dropping a call 2026-11-20 17:13:10 +01:00
jschoubben 9b9ced4fc2 Design 47 H: H-A-157, package edges come from go.mod requirements 2026-11-20 17:13:01 +01:00
jschoubben 084d12d0af Design 47 H: H-A-156, the builder's revision wait is revision-wait-minutes 2026-11-20 17:09:38 +01:00
jschoubben d4e90591a9 Design 47 H: H-A-155, a build waits for its revision, never a build without a version 2026-11-20 17:05:08 +01:00
jschoubben 01842bbeee Design 47 H: H-A-154, the catalog revision names its base 2026-11-20 16:55:48 +01:00
jschoubben abe42c4240 Design 47 H: H-A-151 to H-A-153 carry the clock's times 2026-11-20 16:45:41 +01:00
jschoubben 94f45529cd Design 47 H: H-A-153, the composition run value carries its unlisted set 2026-11-20 16:45:35 +01:00
jschoubben 291f12fc5f Define the hand-pack builder, so a hand pack is no longer briefed by hand 2026-11-20 16:45:22 +01:00
jschoubben 20ad27d67b Design 47 H: H-A-151 validate's base is the pinned newest kept revision; H-A-152 one set of unlisted assignments 2026-11-20 16:43:27 +01:00
jschoubben b4d6bf9bd0 Design 47 H: H-A-150, which failed fetch forgets a resolution 2026-11-20 16:31:57 +01:00
jschoubben fed78cceeb Design 47 H: H-A-149, the finding of an unlisted assignment 2026-11-20 16:27:29 +01:00
jschoubben 310f8955ba Design 47 H: H-A-148, an unlisted assignment does not fail the machine's composition 2026-11-20 16:26:50 +01:00
jschoubben 3e177edf69 Design 47 H: H-A-147, validate's base revision is pinned with the take-in 2026-11-20 16:23:37 +01:00
jschoubben 26f5505e39 Design 47 H: H-A-146, a resolution whose fetch failed is forgotten 2026-11-20 16:20:29 +01:00
jschoubben 0787704bba Design 47 H: H-A-145, a kept stream is brought to the definition's source filter in place 2026-11-20 15:37:55 +01:00
jschoubben 682bdb724c Design 47 H: H-A-144, a module with no registration held is unlisted 2026-11-20 15:32:53 +01:00
jschoubben ccc73e172a Design 47 H: H-A-143 said with role names (hq is public) 2026-11-20 15:20:39 +01:00
jschoubben 962e0af17f Design 47 H: H-A-143, a machine's composition across the watched branches 2026-11-20 15:19:20 +01:00
jschoubben 1c186e1a0e Design 47 H: H-A-142, an event said with a further part is declared with it 2026-11-20 15:12:01 +01:00
jschoubben 3d722934c0 Design 47 H: H-A-141, a reader hearing a revision below its picture asks its first view again 2026-11-20 15:01:13 +01:00
jschoubben b75d138622 Design 47 H: H-A-140, a login not handed is replaced by a newer lease of its own account 2026-11-20 14:47:00 +01:00
jschoubben e359911ecc Design 47 H: H-A-139, the handed login's successor is the same lineage with a later access expiry 2026-11-20 14:25:00 +01:00
jschoubben 800ec4621b Design 47 H: the findings of H1's live run, for H2 and H4 2026-11-20 14:21:09 +01:00
jschoubben 175ed320da Design 47 H: H-A-138, a lease older than a handed login is never written 2026-11-20 14:15:33 +01:00
jschoubben 268bbdb6bd Design 47 H: H-A-137, a root module's generated-from keeps the seats directory and its generated packages 2026-11-20 13:00:31 +01:00
jschoubben cf872d91d4 Design 47 H: H-A-136 reads the fetched commit's manifests; the key question goes to H2
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
2026-11-20 12:43:31 +01:00
jschoubben aca06fc312 Design 47 H: H-A-136, what a step's workspace holds (generated-from directories, same-repository zero-version packages)
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
2026-11-20 12:36:37 +01:00
jschoubben 40be107a7e Design 47 H: H-A-134 names delivery from new messages only
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
2026-11-20 12:20:18 +01:00
jschoubben 8d30cc4237 Design 47 H: H-A-134 names the ack wait and max deliver of the indexer's own durables
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
2026-11-20 12:13:51 +01:00
jschoubben 4b5066bc66 Design 47 H: H-A-135 names the earlier branch.* objects too
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
2026-11-20 12:10:29 +01:00
jschoubben 73685d41b6 Design 47 H: H-A-134 the indexer makes its own per-branch durables until H4b; H-A-135 old trunk revisions and current mark go
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
2026-11-20 12:06:31 +01:00
jschoubben 9f231e07a2 Design 47 H: H-A-133, the follower on a module's own runtime hears when its bundle subscribes
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
2026-11-20 11:31:58 +01:00
jschoubben 934f2c2bc0 Design 47 H: H-A-132, the tool runner binds a module's consumer once
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
2026-11-20 11:20:27 +01:00
jschoubben be0bf71651 Design 47 H: H-A-130 the start of a take-in read by the verb; H-A-131 a module-less repository and the gate
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
2026-11-20 10:32:23 +01:00
jschoubben 58ea7aece1 Design 47 H: H-A-129, the indexer reads a branch's source by the verb when its consumer is not bound
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
2026-11-20 10:30:14 +01:00
5 changed files with 3431 additions and 9 deletions
+55
View File
@@ -0,0 +1,55 @@
---
name: hand-pack-builder
description: Builds one hand pack of the Novox mesh - a folder holding one module's bundle (or a few), built from a repository commit the way the Go build module builds it, with SHA256SUMS, the build script and NOTES.md naming the exact placement steps - for a hand placement the lead says to the operator first. Places it on a node only when the caller asks for that in a later message. Never builds in a developer's worktree, never commits or pushes in a code repository.
tools: Read, Grep, Glob, Bash, Write, Edit, mcp__mesh__mesh_call, mcp__mesh__mesh_describe, mcp__mesh__mesh_search, SendMessage
model: opus
---
You build one hand pack for the lead who started you. A hand pack is a folder of built artifacts that a person puts on
a node by hand, a hand act, when the delivery cannot bring them: most often a circle, where the fix is the very bundle
the node-engine cannot fetch or the pipeline cannot pass without it. The handover names the module and its artifacts
(`<module>:<artifact>`), the repository and the commit, the node, the pack's folder, the pack it is built like, and the
read that confirms the cause.
**Confirm the cause first, read only.** Before you build, do the read the handover names: the seat's verb through the
mesh MCP server (`mesh_search` finds it), the store or the journal it names. Say what it answered, what that means, and
whether the pack answers that cause. When it does not, stop and report before building.
**Build like the earlier pack.** Read the earlier pack's NOTES.md and its build script or go.work files, and the pack it
points to. Then:
- Make your own worktree of the repository, detached at the named commit, under hq's `.work/` with the name the
handover gives; never build in a developer's worktree or a working copy's checkout. Siblings the build needs (the
mesh packages of other repositories) come from their `origin/main`, in worktrees of your own or in checkouts the
earlier pack used when they sit at `origin/main` and are clean; say each sibling's commit.
- Build as the Go build module builds: `CGO_ENABLED=0`, `GOFLAGS="-trimpath -buildvcs=false"`,
`-ldflags "-s -w -X main.builtFor=<system>"`, `GOTOOLCHAIN=local`, no version stamped, the mesh packages placed by a
go.work file kept in the pack. Run the unit tests of the packages the commit changed.
- Write the build as a script in the pack that refuses a worktree not at the commit and is loud on failure; run it
twice and say whether the sha256 is the same.
- Prove the artifact: a tools bundle answers `initialize` and `tools/list` over stdio (say the count and the tools the
fix concerns); a program carries what the fix adds (a string, a flag). When the delivery released the same commit
already, fetch the released artifact from the registry and compare: same source, and why the bytes differ if they do.
- Write `SHA256SUMS` over every file of the pack.
**NOTES.md says the placement whole**, so the lead can say it to the operator and a person can run it without asking:
- What each file is, from which repository, commit and directory, its size; the siblings and the toolchain.
- Why: the cause as read, with the digests or the lines read and the time read, and the circle the pack breaks.
- Where each file goes on the node, read from the unit or the tool runner's module list there (never assumed), with the
file's present sha256, owner and mode; the old file kept once beside it as `<file>.pre-h1`, the new one put with the
same owner and mode through a temporary name and a rename.
- Which units restart, in which order, and the check after each that must pass before the next step (a verb's answer,
a unit's state).
- How the node-engine's have of the module comes to the released fingerprint: read in the node-engine's code on main
whether it asks again on its own, on its verb `compose`, or only after a restart, and name the function that decides.
- The undo, and the notifications the steps may raise.
**Placing**, only when the caller asks for it in a later message, after the lead has said it to the operator: copy the
pack to the node, check `SHA256SUMS` there, run the steps of NOTES.md one by one and read each check; stop at the first
that fails and report it. Reading a node by a shell is allowed only on the days the operator allows it; otherwise
through the mesh MCP server alone.
Report in under 500 words: the cause's read and what it means, the pack's folder, its sha256 lines, the placement steps
in order, what you could not read or prove, and any finding (a fault the pack works around) for the lead to note on
the issue that covers it. Separate fact from guess, in the glossary's words.
@@ -61,14 +61,14 @@ per cent of the 527 rows judged (the rest belong to another part's code) (per pa
| symptom (live) | count | cause (from the gap tables) |
|---|---|---|
| wants held or failed on the four machines | 205 held, 66 failed | the catalog half holds no entry for their fingerprints; the node-engines compose nothing new |
| compositions fail on shanks | entries `asked` since 2026-11-18 03:09, unready answers seen from 2026-11-19 11:56 | an entry ask that failed in transport is never asked again; the node-engine's shadow waits on it without bound (the surveyor's reading); other compositions failed on the removed revision trunk.510 and on a call-token refusal |
| compositions fail on the operator's desktop | entries `asked` since 2026-11-18 03:09, unready answers seen from 2026-11-19 11:56 | an entry ask that failed in transport is never asked again; the node-engine's shadow waits on it without bound (the surveyor's reading); other compositions failed on the removed revision trunk.510 and on a call-token refusal |
| delivery records open, none ended | 833 open, 0 ended since 2026-11-14 | the gate hears only `take-in.taken`; nothing writes a record's trace, so its difference is never known |
| pipelines about to start at the next take-in | about 60 (reasoned from the sweep's rule; no tool reads the runner's waiting starts) | the runner's sweep starts a pipeline for every module whose fingerprint has none (b9c50ef0, 2026-11-16); no design line allows it |
| source revision moved twice | both paths on main | A-464 (per merged message) wins live over A-34 (on the take-in): a group's members become separate revisions; a pushed commit reaches the source only through the take-in or the gate's comparison at its next start |
| catalog revision removed while pipelines name it | trunk.510 at 22:51 | pins are judged at restart against a key written once; only the take-in pins pipelines |
| stale bus state | 753 merges, 6,951 owed, 898 asks, 1,256 pulls keys; 5 pipelines running since midday; 31 stale pin records | buckets of the pre-G model never dropped; no tool reads their contents |
| bus load | 98 slow consumers, 117 consumers behind; the watchman 39,037 events behind | mesh-config passes every 5 minutes and polls every minute on main (fixed on the held pull requests); the forge module polls every minute |
| hand-placed programs | every delivery module but the indexer, the image registry and the tool runner (on ace and g14) | G's live start of 2026-11-16 and after; 16 drop-in files under `/run/systemd/system` on the four machines (4 of them `.pre-g` copies), lost at a reboot |
| hand-placed programs | every delivery module but the indexer, the image registry and the tool runner (on the home server and the laptop) | G's live start of 2026-11-16 and after; 16 drop-in files under `/run/systemd/system` on the four machines (4 of them `.pre-g` copies), lost at a reboot |
**Every node, every module** (the assigner's assignments at revision 339, unchanged since 2026-11-18 02:08 UTC; the
node-engines' haves; read 00:47 to 00:54 CET):
@@ -247,8 +247,8 @@ Built 56, built otherwise 8, contradicts 9, missing 3, not judged 7 (of 83). Ass
A-478b's order waits on one machine stay (the order waits reshaped to order one machine's apply, not hold wants).
- **The assigner reads every have** whole and with history (§520 says it goes); wants are not written from the kept assignment graph revision. Medium each, H1. (The node-engine's read of
every node's record stays: it feeds the composer; H-A-60 corrects the earlier reading of §459.)
- **The shanks shadow fault**: the entries client leaves an entry `asked` after a transport failure and never asks
again; about 110 entries on shanks have stood `asked` since 2026-11-18 03:09. Ask again on failure, with a bound
- **The shadow fault on the operator's desktop**: the entries client leaves an entry `asked` after a transport failure and never asks
again; about 110 entries on the operator's desktop have stood `asked` since 2026-11-18 03:09. Ask again on failure, with a bound
(small). The surveyor's reading, to be confirmed by `entry-again` on one entry during the clean state.
- **The tool runner:** A-490m is ready on mesh-tools #77 (merge); it lacks a test that starts it whole.
- **Tests:** the node-engine has 1,719 unit tests against a budget of 500; every change to it shrinks that.
@@ -269,7 +269,7 @@ Built 56, built otherwise 11, contradicts 5, missing 11, not judged 9 (of 92).
retries twelve watches every 5 seconds; the forge module polls every minute; the build modules re-pull every 5
seconds when idle; mesh-sdk's view catch-up asks again on a timer. The gap table's section 5 has the table of
modules, functions and intervals. The fix belongs in mesh-sdk, for every module at once (fix-a-bug-met-twice).
- **`builder_stuck` times out** for a fixed cost, measured in the tool runner's journal on shanks: 1,010 values took
- **`builder_stuck` times out** for a fixed cost, measured in the tool runner's journal on the operator's desktop: 1,010 values took
52.5 seconds and 53 values took 44.5 seconds. Each call starts a tool process that lists every key of `builds` and of
every build seat's `steps`, then reads one value per request. The builder keeps its own index of what is building
and answers from it. Medium.
@@ -373,14 +373,14 @@ like any milestone, but its delivery is by hand, because the running system cann
the operator runs each pack one command at a time and says "done"; the lead checks each with the tools before the
next:
1. **Freeze.** No merge to any delivery repository but H1's own. The runner on novox is stopped through the service
1. **Freeze.** No merge to any delivery repository but H1's own. The runner on the control-node is stopped through the service
seat so no take-in starts a pipeline during the freeze; the assigner stays, so nothing moves.
2. **Merge H1's set to main**, in this order, each reviewed: mesh-contracts #16 and mesh-sdk #200 (held), then
mesh-catalog #708 and mesh-delivery #261 (held, mesh-config), mesh-tools #77 (held), and H1's own pull requests
(indexer take-in, runner, gate, bridge, assigner, node-engine). mesh-delivery #262 is closed as superseded. The
stopped runner starts nothing; the indexer takes the commits in and the gate follows, as the old programs still
running during the freeze do. The new programs take every head in once, at the seed (step 5.9).
3. **Build H1's programs from main** with the packs (the g-start phases, one per program), on shanks and novox as
3. **Build H1's programs from main** with the packs (the g-start phases, one per program), on the operator's desktop and the control-node as
before, from main's head after step 2 so that main is what runs.
4. **Take the stream snapshot that is the drop's rollback** (design 47 H §765) and test its restore; nothing is
dropped yet. The drop-ins are removed and the units the node-engine writes take their place as the wants compose.
@@ -414,7 +414,7 @@ next:
to main through a merge call (`merge-pull`, design 47 H §734), followed from `take-in.taken` through `pipeline-ended` to the node-engine's `running` and the gate's
ended record, with no hand act; then one two-module change along a dependency edge (mesh-sdk and a module that
requires it published), merged in one merge call, the same way. Each proof read with the tools and quoted with its times.
8. **Lift the freeze.** From here every merge is delivered by its pipeline; a hand pack is a breach the lead names.
8. **Lift the freeze.** From here every merge is delivered by its pipeline; a hand pack is a breach the lead names. Done at 19:31 on 2026-11-21 (section 10, row 173).
## 6. The milestones after the clean state
@@ -455,7 +455,7 @@ at the prepare, one developer per repository on the larger model for the indexer
- It does not merge the six held pull requests now; they merge in H1's step 2, and one (#262) is closed.
- It does not touch the controller, the vault or the recovery module beyond what the chain needs; the recovery
module is not placed and is a later milestone's.
- It does not change the catalog's module set or the build nodes (novox's build agent stays paused).
- It does not change the catalog's module set or the build nodes (the control-node's build agent stays paused).
- It leaves what the surveyors could not read as named guesses, each with how to check it, in the gap tables'
last sections; the prepare of each milestone checks them.
@@ -477,3 +477,248 @@ the one review (`mesh-code-reviewer`, at most three rounds).
The order between branches is the prepare's dependency table: contracts and copies first (published as the next
mesh-sdk and mesh-contracts versions at the clean state's step 5.2), then the modules; the runner-and-assigner branch
rebases onto the contracts commits before the review.
## 10. Findings of H1's live run, for H2 and H4 (the lead, 2026-11-20 14:22 CET)
Met while the clean state was placed and the first pipelines ran; none changes H1's scope. Each is a line for the
milestone named, written into its part before that milestone's prepare.
| finding | milestone |
|---|---|
| The indexer starts its take-in on a two-minute timer; the first branch take-in after a start waits that long. An event, not a timer (P1). | H2 |
| The readers' first views loop on "asked once more" when the verb's holder is slow; the loop is silent. | H2 |
| The composition step's validate reads "the branch's previous catalog revision" and could not run for the first revision after the seed (main.2 does not exist): a first revision validates against nothing, said so. | H2 |
| The node build module asks a `package-lock.json` of the artifact's path; mesh-contracts's TypeScript artifacts name `.`, where none is: either the artifact path or the module's check is wrong, read against ADR 0499. | H2 |
| The indexer's whole integration test took 32 s to set up on the build node, over the level's 30 s setup bound, so the step failed on time, not on behaviour. | H2 |
| The grants part composes no per-branch consumers. | H4b |
| The runner's publish is malformed on the earlier model's records (one journal line each). | H2 |
| `TakeInSource` has no check for a revision below the newest kept. | H2 |
| `mesh_wait` refuses the operator channel's events. | H2 |
| No bus snapshot on request (a tool of the bus module). | H2 |
| The keeper's orphan rule ignores state buckets. | H2 |
| An artifact's key against the workspace directories H-A-136 adds (ADR 0499 clause 4). | H2 |
| hq has no registration, so its pull requests are refused by the gate (H-A-131). | H2 |
| mesh-delivery-sdk and mesh-delivery-contracts publish as packages of their own. | H2 |
| The hand pack's `build-seats` phase carries the label of the build node only; every machine with a build runtime needs it. | H1, the runbook |
| The claude-code node side wrote a lease over a login the manager had not adopted (H-A-138); its fix is a small fix beside H1. | fixed in H1 |
Added by the lead at 18:40 CET, from the run of 16:40 to 18:40: the first delivery by pipeline landed (a module on the
desktop, with hand restarts), and these were met on the way. A row a lead answer settled says so; the rest are open.
| finding | milestone |
|---|---|
| Validate's base was read as the source number minus one, which names nothing where a take-in moved nothing (the seed, a merge with no mover); the indexer (`mesh-delivery-indexer`) and the assigner's validate. Settled by H-A-151 and H-A-154 (the catalog revision's field `base`), which settle the first-revision row above too. | settled in H1 |
| Compositions on the control-node failed on stale assignments (modules assigned that no watched branch lists); the assigner (`mesh-delivery-assigner`). Settled by H-A-152 and H-A-153 (the run value's field `unlisted`, in the seat mesh-wants), proven at main.24. | settled in H1 |
| A build ask reached the builder before its picture held the pipeline's revision, so it built with no version reserved (main.8, main.21, the first proof); the builder. Settled by H-A-155, H-A-156 (`revision-wait-minutes`) and H-A-162 (a run's ask names no source). | settled in H1 |
| 64 of 82 Go modules carried no package edge, because the indexer read mesh packages from go.sum, which names none at the zero version; the indexer. Settled by H-A-157 (edges from go.mod). | settled in H1 |
| The tool runner (`node-tools`) stopped every subscription on each membership and repair and dropped calls in the gap; the tool runner. Settled by H-A-158 and H-A-160 (make before break). | settled in H1 |
| The builder still numbered every trunk build in a `versions` state of its own and folded a reserved version into an older entry, so builds pinned an old package; the builder. Settled by H-A-159 (the reservation is the one numbering), which also makes a tool to drop or rewrite a versions entry moot. | settled in H1 |
| Packages were pinned by a commit (a pseudo-version of an old tree), so builds ran against pre-H1 packages (main.15, main.20, main.22, main.24); the indexer and the builder. Settled by H-A-161, H-A-165 (`package-wait-minutes`, a re-pin on version-released), H-A-167 and H-A-172 (pins in every form's fingerprint). | settled in H1 |
| A pipeline whose mover had no registration never ended (main.20, main.22), and no tool ended a pipeline by hand; the pipeline runner (`mesh-delivery-pipeline`). Settled by H-A-163, H-A-171 and H-A-164 (the seat verb `end-again` on mesh-pipeline-runner, the tool `runner_end_again`). | settled in H1 |
| The SDK's view reader heard an event only on `<subject>.>`, so the seat mesh-catalog's registration-changed on its bare subject reached no handler; mesh-sdk. Settled by H-A-166 and H-A-169 (the finding `event-unhandled`). | settled in H1 |
| The SDK's finding write for an unhandled event waits up to 3 s on the bus inside the event loop, per event, so a missing stream or a slow bus stalls the module: write it outside the loop, or once per change of the count; mesh-sdk. | H2 |
| The indexer dropped a passed pipeline's revision once the pipeline ended, so the want named an entry no longer kept and was held "entry-missing" (main.23, main.25); the indexer. Settled by H-A-168, H-A-170, H-A-173 and H-A-174 (release pins). | settled in H1 |
| A tier-late pipeline's release records are freed only by that module's next pipeline that ends running, so a module with no later pipeline keeps its revisions pinned; the indexer. | H2 |
| The indexer's `publishedAsBuilt` may read a package's imports at the wrong commit when the pin is not the newest of its series; the indexer. | H2 |
| A failed re-pin leaves a pending key behind; the indexer. | H2 |
| A build module's toolchain edge into the movers it is built from made a cycle the runner never broke, so pipelines held their turn with no step for an hour (main.26, main.28, main.30); the pipeline runner. Settled by H-A-175 and H-A-176 (the pipeline ends failed with why `cycle`). | settled in H1 |
| Integration tests pass alone and fail on the build node under load (the bridge, the grants part, the indexer, the assigner's setup at 38 s against 30 s, the tool runner's level at 72 s against 60 s), because a build node runs levels side by side; fixed per test for the indexer and the tool runner only; the Go build module (`mesh-build-go`) and each module's tests. | H2 |
| The Go build module runs builds at idle CPU priority, so a fixed bound in a test or a step can be outlasted by load alone; the Go build module. | H2 |
| The build node counts untagged tests into a module's integration count (156 against the budget of 50 for the pipeline runner); the Go build module. | H2 |
| Modules over the test budget: the node-engine (`mesh-host`) with 1716 unit tests against 500, the indexer with 538 integration tests and the assigner with 64, against 50; each shrinks with every change to its tests. | H2 |
| The Go build module reads failed on the control-node and on the laptop, and a third build node is paused, so one build node (the desktop) builds for the whole mesh. | H2 |
| The builder still starts delivery builds from the take-in path, flooding the one build node, where H §756 says a build is entered only by the runner's build step; the builder. | H2 |
| A newer pipeline withdraws an older pipeline's build of the same module, and the older pipeline then fails instead of that mover leaving it (main.27, withdrawn by main.30); the pipeline runner and the builder. | H2 |
| The step outputs store keeps 0 bytes, so the words of a failed test are lost and only the verdict remains; the pipeline runner. | H2 |
| The pipeline runner's `show` answers 150 KB with no filter, too large for a session to read; it needs a filter (a mover, a step, a state); the pipeline runner. | H2 |
| A run on request cannot place steps for a module that is not a mover; the pipeline runner. | H2 |
| `runner_start` refuses a head whose pipeline exists (H-A-52), so a package module is built again only by a new merge; the pipeline runner. | H2 |
| A required step that could not run has no hand twin: accepting it and running it again are both refused; the pipeline runner. | H2 |
| No tool places a pipeline's waiting movers again; only the runner's start does; the pipeline runner. | H2 |
| No tool shows the pins a build ask carried; the builder. | H2 |
| `builder_build_again` refuses a key that is done; the builder. | H2 |
| The seed registered not every package module (mesh-delivery-contracts, mesh-delivery-sdk) and made no mover of them, so they were registered by hand and nothing was published at H1's heads (H §758); the seed of the seat mesh-catalog. | H2 |
| A want is written only from a pipeline that passed whole (H §750, §751), so a dependent folded in (H §745) that fails blocks a fix of the module it depends on; the assigner. A design question: all or nothing, or per mover. | H2 |
| Packages in one repository carry no kind-1 edge between them (the sibling rule, H-A-136); a design question whether they should; the indexer. | H2 |
| A module (`feh:tools`) carries a required integration step with no integration test to run ("a step with nothing to run"); the seed's steps in the seat mesh-catalog. | H2 |
| The gate (`mesh-delivery-gate`) says old sources again on a restart. | H2 |
| A held take-in does not try again after a passing failure of the forge; the indexer. | H2 |
| The node-engine's early-pass words "reaches no artifact store" read as a fault while placements are not read yet; the node-engine. | H2 |
| The node-engine's resolve-again period is fixed in code, not a setting (P11); the node-engine. | H2 |
| A fetch made inside the node-engine's turn tells the composer nothing; the node-engine. | H2 |
| The node-engine's node-agent wiring has no test; the node-engine. | H2 |
| A bundle reload of the tool runner still unloads before it serves, so calls in the gap meet no responders (said, not silent), and the mesh MCP server's package takes 28 s to load; the tool runner. | H2 |
| The seat node-files has no verb that reads a file's sha256, and its `copy` refuses another node (issue 903), so hand packs were copied by the lead's shell; node-files. | H2 |
| The builder's unit written by hand on the desktop carries none of the manifest's setting variables, so its settings are the defaults; the builder's hand pack. | H1, the runbook |
| The clean proofs of the runbook's step 7 are still owed: the first proof failed on the version race (settled by H-A-155), the second ran for the publish of the SDK packages; the freeze is not lifted (step 8) (lifted at 19:31 on 2026-11-21, row 173). | H1 |
Added by the lead at 19:50 CET, from the run of 18:40 to 19:50; a row met again names the row of 18:40 it adds to.
| finding | milestone |
|---|---|
| The node-engine (`mesh-host`) asks the seat mesh-recovery for a restore point before it moves a data-holding module, and the recovery module is placed nowhere (H §456), so every such take-in was held for good; the node-engine. Settled by H-A-177 and H-A-178 (it moves without a point where no holder is placed and raises the finding `restore-point-missing`). | settled in H1 |
| A package module no machine holds (mesh-delivery-sdk) had a required composition step that could not run, so its pipeline could never pass (main.35, the second proof); the pipeline runner (`mesh-delivery-pipeline`). Settled by H-A-179 (the step ends `nothing to run`, ADR 0682 §8). | settled in H1 |
| A module held for a failed restore point kept the hold across the node-engine's start, and no operator's ask was raised for it, so the hold was for good; the node-engine. Settled by H-A-180 (the hold's cause is judged again at the start and on every change of placements). | settled in H1 |
| The forge bridge kept each owed event whole in its state `performed`, filling its kept data to 51 MB of the template's 64 MiB (19,530 keys, the condition "kept data is filling up"); the forge bridge. Settled by H-A-181 and H-A-182 (the outcome, when, and the act's pull request; the act stays in the gate's stream `owed`). | settled in H1 |
| The finding `restore-point-missing` did not reach the conditions after the first move without a point: the finding's wiring to the condition keeper; the node-engine. | H2 |
| The recovery module is placed nowhere, and the assigner derives no placement from the holder of the seat mesh-broker (G §554); the assigner (`mesh-delivery-assigner`). | H2 |
| A pipeline record with 112 or 129 movers exceeds the bus's 1 MiB message limit once its steps are placed, so two pipelines were cancelled; the record's shape (steps per mover key) and the limit as a setting; the pipeline runner. | H2 |
| A change to the SDK package folds in about 112 importers and a change in the catalog repository about 60, so the first re-pin of those repositories cannot run until the pipeline record is reshaped (the row above); the pipeline runner. | H2 |
| Met again on the tool runner's pipeline: a superseded build makes the older pipeline fail instead of its mover leaving it (the row of 18:40 on a withdrawn build); the pipeline runner and the builder. | H2 |
| The gate's owed acts run at about ten times the design's estimate (about 80 note acts per delivery record per pull request), and the gate's own stream `owed` takes the same rate; the gate (`mesh-delivery-gate`). | H2 |
| The forge bridge's `bridge_owed` by pull request still reads every key of its state in the tool runner's process; the forge bridge. | H2 |
| A refused consumer creation is tried again for longer than the tools' wait for an answer, so a person sees a timeout instead of the refusal; the bus module's tools. | H2 |
| Met again: the SDK's finding write for an unhandled event waits up to 3 s on the bus inside the event loop, seen as a 90 s test (the row of 18:40); mesh-sdk. | H2 |
| Met again: the build node counts untagged tests into a module's integration count (the row of 18:40); the Go build module (`mesh-build-go`). | H2 |
| Met again: the step outputs store keeps 0 bytes, so a failed test's words are lost (the row of 18:40); the pipeline runner. | H2 |
| The proof of the runbook's step 7 is still owed: proof 1 failed on the version race, proof 2 twice, on stale pins and on the composition step of a module no machine holds (settled by H-A-179), both settled; the freeze is not lifted (step 8) (lifted at 19:31 on 2026-11-21, row 173). | H1 |
| Four hand placements more (the distribution tools bundle, the assigner, the builder's program, the node-engine twice) and five hand restarts were needed to break circles, each said to the operator; the runbook. | H1, the runbook |
Added by the lead at 21:30 CET, from the run of 19:50 to 21:30; a row met again names the row it adds to.
| finding | milestone |
|---|---|
| A pin named the newest release of the module holding a package (its release number), while a Go package's version is its tag, so every importer of a nested package failed on "unknown revision" (main.39), and pipelines kept failing on old pins; the indexer (`mesh-delivery-indexer`). Settled by H-A-183, H-A-184 and H-A-185 (the pin is the newest version the registry published for the package path, within the series the module's manifest accepts), built in the indexer and placed by hand, because its own pipeline could not deliver it. | settled in H1 |
| Nine Go packages other modules import were never declared artifacts of their modules (among them the builder's `builds`, the bus module's `busgrants`, disk-load's `diskreadings`), so no release published them and their importers' builds wait past the bound; the owning modules' manifests in the catalog. Settled by H-A-186 (an imported mesh package is a declared artifact of its module); still owed: the catalog's check that refuses a manifest whose Go module imports a mesh package path no module of the catalog declares. | H2 |
| A package artifact's declared series (0.1) differed from its module's version series (0.3 for the assigner), so its publishes would pin nothing; the manifests in the catalog. Settled by H-A-188 (a package artifact's series is its module's version series, or left out); still owed: the catalog's check that refuses a mismatch, and the gate's manifest (`mesh-delivery-gate`) naming the series 0.3 in its `packages` so it accepts the assigner's asks, in the catalog's next change. | H2 |
| A pipeline record of 112 or 129 movers exceeded the bus's 1 MiB message limit (the row of 19:50 on the record's shape); the pipeline runner (`mesh-delivery-pipeline`). Settled by H-A-187 (steps one key per mover), H-A-189 (a mover's unlogged step-log entries under its mover key), H-A-190 (a step-log entry names its mover) and H-A-191 (`list` answers counts, `mover-count` and `step-count`). Still owed: a tool that reconciles a record whose mover-key writes failed; and a bound on every kept value (64 KiB) and on every tool answer, in mesh-sdk, the lead's proposal, whose scope waits on the operator. | H2 |
| The builder's step path pinned a package of the same pipeline at the module's release number, and the Go build module (`mesh-build-go`), given no pin, took another package's version of the same repository (its "askedFor" fallback), so both built against versions never published; the builder and the Go build module. Settled by H-A-192 (the builder takes a pin from the catalog entry or the registry's package-published event alone; a build module given no pin refuses the build, loud); still owed: the Go build module's half, in the catalog. | H2 |
| The builder's lane narrowed a module's single fetch to the paths of its package artifacts, so a program build found no main module; the builder. Fixed in the builder, by ADR 0499 clause 1. | settled in H1 |
| The indexer's tools bundle missed a catalog-revision event in silence, so the pipeline runner waited 12 minutes for the next revision; the tool runner (`node-tools`). The cause, not the SDK's reader: the tool runner on the control-node was built before the one consumer loop (H-A-132, H-A-133), so two pull loops read the bundle's one durable consumer and each event reached one loop only; the events alternated (the bundle read 42 and 44, the runner's own view heard 41 and 43), and the seat mesh-catalog's revision verb answered a stale revision while the same process had heard the newer one. The fix of the cause is the tool runner's own release reaching that node (pipeline main.43); the kind is closed by H-A-196 (the SDK refuses, loud at bind time, a second pull loop on a durable the same process already pulls), in build. A note: a log line per event handed to a bundle. | settled in H1 |
| The seat mesh-grants's verb `grants-for` was cut after 5 s in two pipelines' composition steps (a widening entry on the vault); the grants part. The cause: the verb answers in 3.4 to 5.0 s, because on every call it reads two whole catalog revisions (about 1.4 MB each) page by page through the seat mesh-catalog's revision verb and composes every account twice, with no cache, while the pipeline runner's read bound is 5 s. A revision read whole over the bus is the same habit as the row of 21:30 on the pipeline record over 1 MiB. The fix chosen (thorough): the grants holder keeps each revision it read, a revision never changing; in build now. Not chosen: raising the runner's bound. | H2 |
| The node-engine (`mesh-host`) on one machine said it cannot create a new version's folder ("operation not permitted"), met twice, two days apart; the node-engine. The cause: an immutable attribute a person set by hand on the engine's versions folder during the recovery of the mixed state of 2026-11-13, since removed; the engine keeps repeating the stale words of its last applied record. No fix in code or unit: the words clear at the next applied composition. Owed: a tool of the seat node-files that shows a file's attributes (none exists), and the engine's record says when its words date from. | H2 |
| Two hand placements more (the assigner's compositions fix and the indexer with pins by package path), each on its machine, because their own pipelines could not deliver them; the runbook. | H1, the runbook |
| The "unknown revision" kind, its cause read at 22:12: the Go build module (`mesh-build-go`), given no pin for a requirement at the zero version (a transitive one, or one a sibling names), borrowed the version of the first package of the same repository in the ask, wrong since pins became per-package versions; the registry, the indexer's pins and the publishes were right for the paths they name; the Go build module and the indexer (`mesh-delivery-indexer`). Settled by H-A-192 (a build module given no pin refuses the build; the catalog's change, in build) and H-A-201 (the entry pins every requirement of the module graph, transitively; in build in the indexer). | settled in H1 once delivered |
| The builder writes a git tag `go/v<version>` for every Go package, while the Go toolchain's direct fallback for a nested module looks for `<directory>/v<version>`, so the tags serve nothing; secondary, as the registry seat holds every real version; the builder. Owed: the tag takes the package's directory, or no tag is written at all. | H2 |
| A build that fails this way is asked again every 30 to 40 s, and the builder reserves a new version number each time (`mesh-build-go` 0.1.65 to 0.1.70 in five minutes): the builder never gives up a failing build of an unchanged fingerprint; the builder. Owed: a failed build of a fingerprint is not asked again until its inputs change, and no version is reserved for a build that failed before. | H2 |
| With H-A-196 and H-A-197 built (the SDK's one guard against a second pull loop on a durable; the tool runner claims through it), two durable pull loops in the delivery repository still call the bus client directly: the watchman's dead-letter loop and the grants holder's main loop; each binds one durable once today, so there is no fault, but the kind is open there; the watchman and the grants part. Owed: both route through the SDK's consume function, in a change after this group's SDK is published (a module builds against the latest published SDK); the review that finds a direct durable pull is the check. | H2, or the next change of the delivery repository |
| The seat mesh-grants's verb `grants-for` (row 69): the grants holder keeps the catalog revisions it read, at most `grants-for-revisions-per-branch` per branch and only for the branches it follows, and learns the branch's newest revision from the catalog-revision event; the grants part. Settled by H-A-193 and H-A-195; merged as pull request #294, whose pipeline failed on other faults, so it is delivered with the next passing pipeline. | settled in H1 once delivered |
| The publishes the builder heard lived only in its memory and were lost at a restart, so a build waiting for a package published before it waited the whole bound; the builder. Settled by H-A-194 (before it waits, the builder asks the package registry seat's `versions` verb once), in pull request #291. | settled in H1 once delivered |
| A package artifact's steps lacked its same-repository requirements (H-A-198), and writing the derived "../" paths into the entry (H-A-199) would have changed the form of the seat mesh-catalog's `modules` value, which every module decodes, so every reader would have had to run the new client before the writer: the mesh cannot derive that ordering edge yet; the Go build module (`mesh-build-go`) and the indexer (`mesh-delivery-indexer`). Settled for H1 by H-A-202 (the Go build module derives the same-repository tree transitively; the indexer takes those directories into the fingerprint for every form without writing them into the entry). Owed: a change of a kept value's form is an ordering edge the delivery plan derives (a contract version on the value, or the readers' release before the writer's). | H2 |
| The indexer pins every other-repository requirement across the module graph, never one of its own repository (H-A-201, pull request #296), and the Go build module refuses a build with no pin (H-A-192, the catalog's change); together they end the "unknown revision" kind (row 72); the indexer and the Go build module. | settled in H1 once delivered |
| The seat mesh-catalog's hand-written digest helpers lived under the contract's generated root, so the generator's check failed every unit step; the contracts module. Settled by H-A-200 (they live in the seat's hand-written client), in pull request #295. Owed: the generator's check runs in the contracts module's own unit step on the mesh (it does today), and the hand-written clients' import of the delivery SDK (ADR 0625 §3) is still on trunk. | H2 |
| The pipeline runner's lint, unit and integration asks carried no pins (only the build ask does, and the builder adds them), so once the Go build module refused a requirement with no pin (H-A-192) twelve test steps of the contracts mover could not run; the pipeline runner (`mesh-delivery-pipeline`). Settled by H-A-203 (every step ask carries the entry's pins), in build in the runner. | settled in H1 once delivered |
| The entries of modules not changed since kept their old `packages`: a direct requirement with no pin although the registry held its version, a declared package never published left out, a same-repository chain missed; six build asks were refused; the indexer (`mesh-delivery-indexer`). Settled by H-A-204 (an entry names every requirement, with an empty version where none is published so the builder waits; a publish re-pins every kept entry of any repository; a tool answers one entry's pins), in build in the indexer. Owed: the kept-entry rule "unchanged unless it imports a package the commit moved" is replaced by the publish re-pin everywhere. | H2 |
| A second build node still ran the Go build module (`mesh-build-go`) from before the pin refusal, so one pipeline's build borrowed a pin there and failed "unknown revision" while the first build node refused loud; the fixed build module could not be placed on that node tonight, so its Go steps were paused by its tool; the Go build module and the runbook. Owed: a hand placement reaches every node that runs the module, or the module is delivered by its pipeline (H1's purpose). | H1, the runbook |
| Two pipelines of consecutive revisions ran at once, and the older one's builds failed "revision 45 of main not in the builder's picture within 2m0s" while the seat mesh-catalog's revision verb answered 46; the builder. Settled by H-A-205 (for a revision below the newest it heard, the builder asks the revision verb by number), in build. | settled in H1 once delivered |
| A test step of an entry whose package has no version yet went out without that pin and was refused; the pipeline runner (`mesh-delivery-pipeline`). Settled by H-A-206 (a Go artifact's test steps wait for their pins as the build does, "waits on the publish of <path>"), in build in the runner. | settled in H1 once delivered |
| The Node and the Go build modules' tools that list their running steps do not list delivery asks (the builder's own asks), so the check "no running step" before a hand restart cannot see them; the Go build module's was seen at 01:17 to 01:19, its step list showing none while the seat's `current` verb showed asks running; the Node build module and the Go build module (`mesh-build-go`). Owed: each list names every ask the module runs, whoever asked. | H2 |
| A test step held for a pin not yet published had nothing to end it once its build passed (the builder had read the registry and pinned it), so with one pipeline at a time the queue would stop; the pipeline runner (`mesh-delivery-pipeline`) and the builder. Settled by H-A-207 (the build's end reports the pins it built with, the seat mesh-builds' end carrying `packages`, and the runner asks the held steps with them), in build. | settled in H1 once delivered |
| The reading of the module graph (H-A-201) runs at a take-in, which applies a repository whole, so repositories with no merge since the rule changed kept their modules' direct requirements only, and no tool took a repository in again; the indexer (`mesh-delivery-indexer`). Settled by H-A-208 (the tool `indexer_take_in_again`), H-A-209 and H-A-210: the take-in again keeps no catalog revision and asks no gate; it re-reads the repository's kept requirements at its merge commit and recomputes the modules state as a publish re-pin does; in build. Owed: a change of the indexer's rules recomputes every repository by itself at the indexer's start; the tool is the hand form of that. | H2 |
| The pin kind (rows 62, 66, 72, 79, 81 to 85, 87, 88) was fixed one instance per round for five hours, against the rule "at the second failure of a kind, fix the kind"; the rule was then written whole as a specification with a gap table against the code ([H-pins-spec-and-gaps.md](H-pins-spec-and-gaps.md)): 35 lines, 24 built, 6 built otherwise, 1 contradicted, 2 missing, and 7 changes still missing (its section 8), the largest that a re-pin on a publish never became a revision or a mover (the "entry-missing" holds on wants), settled by H-A-211 (a re-pin is taken in as the next catalog revision of the same source); the indexer (`mesh-delivery-indexer`), the pipeline runner, the builder and the Go build module. The lesson for playbook 07: a kind met twice gets its specification before its third fix, and one owner across every part it touches. | H1 (the way of working); H2 for the owed items of the specification's section 8 |
| A catalog revision's number equalled the gate's source revision by habit, so a re-pin had no number to keep its entries under, and the pipeline runner started a pipeline per published artifact (several per release) from its own hearing; the indexer (`mesh-delivery-indexer`), the seat mesh-catalog's definition and the pipeline runner (`mesh-delivery-pipeline`). Settled by H-A-212 and H-A-213: a revision's number is the indexer's own counter, with the gate's source as a field; a revision carries its call (`call`: take-in, release of a module version, or take-in again of a repository); one pipeline per release revision; the runner keys pipelines and reads revisions by number. The call's kind is a field of its own, `call-kind`, an enumeration the seat's schema validates (take-in, release, take-in-again), with `module` and `version` or `repository` beside `call`, the words for a person, so no reader parses words (H-A-215). The seat mesh-builds' package-published names the revision it was built from (`revision`, set by the builder), so the runner finds the publishing pipeline among several revisions of one source (H-A-218). Every ask of the runner (build, step, wants) names the catalog revision number in its `revision` field, with the gate's source beside it in `source`, so a build module and the builder read one meaning of the word (H-A-219). A build the builder starts from its own picture takes its revision number from the picture's half into its reservation, so its publish names the same revision its source comes from (H-A-220). The runner's pipeline subjects (pipeline-started, pipeline-ended, wait-held, wait-ended) name their last token `<revision>` and carry the pipeline's revision number, the same number as its key, so name and value agree (H-A-221). In build by the one owner of the pin kind (row 89). | settled in H1 once delivered |
| With revision numbers no longer the gate's source (row 90), two readers still looked a revision up by its source: the seat mesh-catalog's revision verb's source input, and the indexer's freeing of a pipeline's pins on the seat mesh-wants' pipeline-wanted, which named only the source; and the take-in again could re-read only the trunk, since only its merge commit is kept; the indexer (`mesh-delivery-indexer`). Settled by H-A-214 (pipeline-wanted names the revision number; the verb's source input answers the take-in's revision; the take-in again covers the trunk, and another watched branch is re-read at its next merge). In build by the pin kind's second owner: the first ran out of context after the indexer's part, and the hand-over cost one review round. Owed: a take-in again of another watched branch, once branches live longer. | settled in H1 once delivered; H2 for the owed item |
| Beyond the publish re-pin, three more whole recomputes of the indexer (on a build module's assignments change, on a toolchain report, and by the recompute tool) moved fingerprints with no kept revision, and the assigner (`mesh-delivery-assigner`) derived a pipeline's source from its key, which now carries the revision number; the indexer (`mesh-delivery-indexer`), the pipeline runner and the assigner. Settled by H-A-217 (any recompute that moves a fingerprint keeps a revision of `call-kind` recompute naming its reason; the runner treats every revision whose kind is not take-in alike, one pipeline for its movers) and H-A-216 (the assigner keeps the source the pipeline's end names and sends it in pipeline-wanted beside the revision). In build by the pin kind's second owner (row 91). | settled in H1 once delivered |
| The joined pipeline runner (`mesh-delivery-pipeline`) crashed at every start on the control-node ("concurrent map writes" in its per-mover step store: the store's shared maps were written under each pipeline's lock only, while the start placed several branches' waiting pipelines at once) and was rolled back within a minute. Before dying it had split two kept pipelines into per-mover keys, and the old runner then placed one running pipeline's steps again from the emptied record, losing that record's history; no hand repair, as the new runner composes from the keys; the pipeline runner. Settled in H1 by a mutex over the store's maps and a run of the race detector over the runner's start path with kept pipelines. Owed: every module's unit and integration suites run under the race detector in the check, and a tool that lists the runner's state keys (a whole list exceeds the bus; no key listing exists). | H1 (the fix); H2 (the check and the tool) |
| The indexer (`mesh-delivery-indexer`) refused its own take-in-again tool's ask ("a takeins value naming no hand act the indexer serves"): the decoder of a take-in ask kept a hand-written list of hand-act fields that the new field was not added to, and no test sent a tool's value through the decoder; the indexer. Settled in H1 by deriving the check from the ask's fields, and by a table test that decodes every tool's value. Owed: the same table test for every module whose tools write asks its daemon decodes. | H1 (the fix); H2 (the kind across modules) |
| The seat mesh-catalog's revision verb answered from the tools bundle's view of the trunk in memory, which ran one or more revisions behind the kept revisions once releases kept several in a row, so the pipeline runner waited minutes for a revision the indexer had kept (four minutes for revision 52) and the builder's picture failed a pipeline's first builds past its bound (rows 68 and 84); the indexer (`mesh-delivery-indexer`) and the builder. Settled by H-A-222 (the verb answers the newest kept revision read from the store at the ask; the builder's picture holds an ask that names a kept revision number, read by number), in build. | settled in H1 once delivered |
| A release re-pinned a mover of a running pipeline of 120 movers (the tool runner, pinned to the SDK's new version) while that pipeline still built it at the old fingerprint; the build failed and, as a pipeline passes or fails whole, took every other mover with it, because the runner moved only movers of waiting pipelines; the pipeline runner (`mesh-delivery-pipeline`). Settled by H-A-223 (a moved mover leaves a running pipeline too: its steps end superseded, its asks are cancelled, the end judgement counts it as left; a pipeline whose every mover left ends superseded), in build in the runner. Also seen in the same pipeline: two builds done "but no version is reserved", because the builder's picture lagged the revision that named their fingerprints (row 95's cause). | settled in H1 once delivered |
| On the build node the SDK's own integration test of the views reader ("the views reader and two handlers share the module's one durable") failed under the new guard against a second pull loop on one durable (H-A-196), while the same test passed locally at review. The cause, not the guard: the test read the durable's pending-ack count the moment the handlers had spoken, while the reader acknowledges afterwards and the bus takes acknowledgements on its own, so one was still pending on the loaded build node; the test now publishes a mark event and waits for the consumer's acknowledged floor to reach it, fixed in mesh-sdk, in review. The kind: a test reading the bus's acknowledgement count right after a handler speaks; mesh-sdk. Also seen: four release-revision pipelines waited with no steps for over ten minutes behind one running pipeline that could no longer pass, because the pipeline runner (`mesh-delivery-pipeline`) runs one pipeline at a time and ends a pipeline only when its last step ends. Owed: a pipeline that cannot pass ends at once (H-A-163 as written), and the queue's setting is raised once the build nodes allow. | H1 (the SDK's fix); H2 (the queue) |
| With the SDK's new guard against a second pull loop (H-A-196), which reads a consumer's cached information at bind, a test fake of a consumer in the indexer (`mesh-delivery-indexer`) that answered no such information panicked, so the indexer's unit step would fail against the new SDK although no indexer code changed; mesh-sdk and the delivery repository's modules. Fixed in H1 by completing the fakes across the delivery repository's modules. Owed: a change of the SDK that adds a call on an interface every module fakes is tried against the modules' suites before its merge (the group's check builds every importer, but runs no importer's suite). | H1 (the fakes); H2 (the check) |
| The builder was restarted by hand while Go asks ran in the Go build module's runtime (`mesh-build-go`), whose step list showed none because it does not list the builder's own delivery asks (row 86); the asks survived the restart because the build module runs them, but the "no running step" check before a hand restart is blind to them; the build modules and the runbook. Owed: one tool across the build seats that lists every running ask, whoever asked it. | H2 |
| The watchman's entry still pinned no client that its same-repository `buildrun` module requires, because the watchman's go.mod names `buildrun` in a replace directive without a require line, and the reading of the module graph (H-A-201) followed require lines only; six test steps were refused "no pin" (rows 79 and 82); the indexer (`mesh-delivery-indexer`). Settled by H-A-224 (a same-repository module named only by a replace counts as required; its requirements are pinned transitively), in build in the indexer. | settled in H1 once delivered |
| The builder keeps one reservation per module and series and bumped its number on any new run of a build (a restart's re-run included), while the run already building carried the old number, so its publish was refused "has no version reserved or released"; and a take-over of the series by another fingerprint dropped the older reservation without stopping the older build, which then published a dropped number; the builder. Settled by H-A-225 (a reservation is kept for the same fingerprint until it is released; a taken-over build is withdrawn; a number never published is freed), in build in the builder. Its last clause is withdrawn by H-A-226: the builder's Built and the reserved answer match by version alone, and the registry refuses a republish with other bytes, so a reused dropped number would let a withdrawn build's late publish land in the new reservation; a dropped number stays a gap, which harms nothing, and the series key keeps only the withdrawn numbers above the catalog's highest released patch. Also seen: after the builder's start it logged "no seat builds an artifact of language go and kind package" dozens of times a second (the journal suppressed over a thousand lines); not a spin but a burst at the start: every catalog entry taken in and every seat definition heard plans every known module again, and a failed plan is not kept, so the same line is logged once per definition and module. Owed: a failed plan is kept and said once until the seat list changes. | settled in H1 once delivered; H2 for the owed items |
| A restart of a node's tool runner (`node-tools`), to load one module's new tools bundle, silences the seat verbs of every module whose tools run inside it: the artifact registry seat answered "no responders" for about two minutes while the control-node's tool runner restarted, and the builder's publishes failed meanwhile; the tool runner and the builder. Owed: a tool runner serves one module's bundle again without restarting (H-A-158's make before break, for a bundle), and a publisher retries a seat that answers no responders, within a bound. Also seen there: the registry seat's list answer exceeds the bus (1.5 MB; pages are owed, the same habit as row 65), and a finding of kind read-side-down raised by one writer cannot be cleared by the tools' writer (owed: one owner per finding kind). | H2 |
| The thirteen issues the lead held were judged against what the milestone delivered: five closed as superseded by H's merge call and the checker's retirement (the forge's status writes, the merge Approve path, a second check overwriting the first, a gate merge without a manifest, a refused merge asked again); three resolved with their fixes named (the controller's check bound, the checker's tests on the desktop, the build node's resolver); one released back to open (the verbs of the seat node-package-manager, which H does not touch); two kept with a note (the bus flood, whose kind now sits on the connection of the control-node's tool runner; the session not told of an answer); and two wait for the proofs (a held module's chain; one release for a change across repositories, proof 2); the issue tracker. A missing tool was met: no forge tool lists merged pull requests by number. | H1 (done); H2 for the two waiting and the tool |
| The artifact registry's receiver read its incoming object store's fill on every chunk it took, and the tool runner (`node-tools`) answered the fill by listing every kept description of the store, the leftovers of about twenty thousand deleted chunks included, so the control-node's tool runner read fourteen megabytes a second and the bus ran at full CPU; every take-in and publish slowed (proof 1's take-in took six minutes), and discovery answered incompletely (rows 65 and 102); the artifact registry, the tool runner and the delivery SDK. The recovery (drop one dead upload, purge the store's leftovers) removes data and was put to the operator. Settled by H-A-227 (a fill is read from the stream's own figures, never by listing; a receiver reads it once per transfer; the owner compacts a store of leftovers), in build in the tool runner and the delivery SDK. Also seen: three findings streams stood full (the pipeline runner's, the builder's and the node-engine's); owed: a findings stream bounded by age, and a reader of its fill. | H1 (the fix); H2 (the compaction and the bounded streams) |
| The validate step's run ask (the manifest validator's program, built and run from the delivery repository's tree) still carried no pins after H-A-203 was built for the test asks, so with the build module refusing a requirement without a pin every validate step ended "could not run" (proof 1's feh at 01:56, the SDK's at 01:30) and no composition followed (rows 81 and 85); the pipeline runner (`mesh-delivery-pipeline`). Settled in H1 by giving the validate ask the pins of the manifest validator's own entry at the pipeline's revision, in build in the runner. The kind: every ask the runner makes carries pins, and a review that reads "every step ask" lists the asks. | settled in H1 once delivered |
| The bus module's keeper reads only a manifest's new-form asks, so the eleven entries the two foundation parts (the artifact registry and the forge) declare in their old sections, all with live data, stand as orphans to it: the registry's incoming store could not be rebuilt empty ("an orphan: drop it, or ask for it in a manifest again"), and the only way to empty it was a drop on the operator's warrant followed by the grants part's assert that makes it again; a careless drop of any of the other ten would lose live data (rows 65 and 104); the bus module. Settled by H-A-229, H-A-230 and H-A-231: every manifest's old-section entries are asked for, never orphans; the keeper keeps, grows and rebuilds only those it made, and creates none (the grants part makes the rest); in build in the bus module. Ten of the eleven clear; the lower-case events stream, which the keeper made under a name the grants part does not derive, stays an orphan, to be dropped on the operator's warrant. | H1 |
| Three fixes were merged between 02:09 and 02:13 and each taken in within a minute (the flood halved after the dead upload was dropped): the validate and composition run asks' pins (the holder of the seat mesh-wants), the tool runner's fill from the stream's figures, and the receiver's one read per transfer. The first lands in the holder that runs on a node of its own and through which every validate step runs, so no pipeline can deliver it to itself: a hand pack for that node, copied by the operator at their terminal (the session's permission check refused the lead's copy) and restarted there before the running pipelines' validate steps can pass. The last of the three re-pins twenty-nine modules into one pipeline; the runbook. | H1 |
| The bus module's drop of an orphan asks the operator's warrant with a window of ten minutes, and then ends with nothing removed ("ask again with a new request") while the operator is away, whereas the session's own asks carry an expiry the asker sets (up to a day); the drop's warrant should carry the asker's expiry too, or at least the operator's answer to the session's ask should count (row 106); the bus module. Owed: the bus module's warranted acts take an expiry from their caller. | H2 |
| The bus module's orphan judgement (row 106) was fixed, reviewed in two rounds (the first found the keeper taking into its care a state's object store the grants part made, and its cap sum dropping kept state buckets) and merged at 02:33; its take-in took close to three minutes while the indexer waited on a package's versions, where the night's others took under a minute; its pipeline waits with five others on the validate fix reaching the node that runs the holder of the seat mesh-wants (row 107); the bus module and the runbook. | H1 |
| Every take-in of the catalog repository since a Go module was removed from it on 2026-11-17 said "its packages are not published": the indexer (`mesh-delivery-indexer`) lists a repository's packages from its kept packages state too, which still holds the removed module, so the forge's listing of the whole set fails, and the indexer's one-directory fallback runs only on its own error, not on the forge's. Nothing of that repository was published since, so the digests of its three same-repository packages froze on their last commit, and a change to one would not move its seven importers, unsaid; met twice tonight before it was read (row 81 on the pins kind; issue 1585, one release for a change across repositories); the indexer and the forge module. Settled by H-A-232 (a repository's packages are those in the merge's tree, and a gone key is dropped and said; the forge answers not-found and the fallback runs on it; any other failure stays loud), in build in the indexer and the forge module. | H1 |
| The operator restated at about 03:33 the bound ADR 0282 decides: a fix to a leaf module runs healthy on every node within five minutes of its merge, a core module within ten. Tonight's measured parts: merge to take-in 25 to 45 s for the delivery repository and 2 min 40 s to 5 minutes for the catalog repository (cause not yet known; the indexer waited on a package's versions); take-in to placement about two minutes under the queue of pipelines at once; a leaf's build step running past six minutes; and no pipeline reaching its composition since 01:56 (the validate asks). No pipeline completed merge to running tonight, so the whole is unmeasured (rows 105 and 107); the pipeline runner (`mesh-delivery-pipeline`) and the condition keeper. Owed: the pipeline's phases timed and said per pipeline (the pipeline-ended event carries each step's start and end), and the delivery time held against ADR 0282 by a condition. | H2 (the measure); H1 records it |
| A release pipeline held the pipeline runner's one slot for nine hours (02:06 to 11:08): its validate ask was lost when the holder of the seat mesh-wants was restarted for a hand pack, and the runner waits on an ask without a bound, so eight pipelines queued behind a step nobody would answer, until the lead cancelled it on the operator's word (rows 107 and 111); the pipeline runner (`mesh-delivery-pipeline`). Settled by H-A-235 (every ask the runner makes is bounded, asked again once, then ends could-not-run with a finding, and the slot frees), in build in the runner. | H1 |
| The runner's rerun of a validate step was always refused ("placed no ask now"): the verb looks for the ask by the mover's id, while the validate ask is one per pipeline and names no mover (H-A-51), so a failed pipeline's validate could not be asked again after the pins fix, and proof 1 had to be run a second time from a new merge (row 105); the pipeline runner. Settled by H-A-236 (the rerun of validate asks the pipeline's one validate ask again; the rerun of composition builds the composition ask for the named mover), in build in the runner with the row above. | H1 |
| The bus module's drop and rebuild warrants ask at the destroy level, which needs a code no channel carries yet, so the router held all four of the night's asks unshown ("no channel can carry it now") while the tool answered "the operator is asked", and each expired after ten minutes; the operator saw nothing on Telegram (rows 106 and 108); the bus module and the operator channel's router. Settled by H-A-237 as a weighed bend the operator asked for: the keeper asks at the approve level until a channel carries destroy, with the caller's expiry; the tool reads the router's record and says offered, held or refused; the router's hold reason names the level. Owed: the destroy proof stays designed (ADR 0259), and a channel that carries a destroy answer. | H1 (the bend); H2 (the destroy channel) |
| Once the slot was freed, the first pipeline through the fixed holder of the seat mesh-wants passed at 11:07 (a release of a contracts package, six movers): validate three minutes after placement, compositions on the build node, the pipeline ended passed, and the next took the slot within a minute; the pipeline runner (`mesh-delivery-pipeline`). Still seen: the seat mesh-grants's verb `grants-for`, cut after 5 s, marks every mover's widens could-not-run (rows 69 and 76, the grants cache); and two movers are over the test budget (an NFS server module at 51 integration tests, a package manager module at 121, against 50). | H1 (the pass); H2 (the cut, the budget) |
| Proof 1 runs a second time: one line in the wallpaper module, merged at 11:07:56, taken in 2 min 51 s later as its own pipeline with the one mover, and placed last in a queue of six; the catalog repository's take-in still says "its packages are not published", because the forge's not-found fix is merged but not running yet (rows 110 and 113): the hand packs of the forge module and the indexer go onto the control-node now, on the operator's word, with the tool runner's; the runbook. | H1 |
| On the operator's word ("if you would run all the changes on our local machine, it wouldn't take that long"), the night's merged fixes to the delivery system itself went onto the control-node as hand packs between 11:10 and 11:19 (the indexer, the forge module's code, the tool runner for seventeen units), each by its notes, with the kept copies beside; all units are active and the forge's listing verb is served; the two proofs alone go by their pipeline (rows 107 and 110); the runbook. Seen in the indexer's journal: its findings writer owns four kinds while its code raises others (a missing pin, generated types out of step, a merge not taken in), so the writer refused them once a minute for hours and no finding of the indexer was written; the kind of H-A-233 would have met the same; the indexer (`mesh-delivery-indexer`). Settled by H-A-240 as H-A-242 corrects it (row 119). | H1 |
| The root of row 112: the holders of the seats mesh-builds and mesh-wants take their asks on a plain subscription, not from a work queue, so an ask put while the holder is down (a hand pack's restart) is lost, and neither seat says a word about an ask before the step's end (rows 107 and 112); the pipeline runner (`mesh-delivery-pipeline`), the builder and the holder of the seat mesh-wants. Settled by H-A-241 and H-A-243: the runner puts every open ask of a seat again when the seat's holder starts, on the node-engine's running event; for a seat that says no first word, one silent bound (`ask-silent-bound`, default forty-five minutes) ends the step could-not-run instead of two short ones, so no build of ordinary length is cut; the second ask's id is derived in the accepted form; in build in the runner with rows 112 and 113. Owed: the seats' asks as a work queue, and an ask-taken from both holders. | H1 (the runner); H2 (the queue) |
| Row 117's cause corrected: the refusals come from the SDK's held writer, which at its start seeds every key of the module's shared findings state, the daemon writer's kinds included, and refuses them once a minute, against the design's rule that no bundle reads the whole state to state another's findings (G §580); mesh-sdk and the indexer (`mesh-delivery-indexer`). Settled by H-A-242, which corrects H-A-240: the held writer seeds only the kinds it owns; each writer's kinds stay in code, with a unit test holding the code to them; an unowned kind is said once; no manifest field; in build in the SDK and the indexer (row 117). | H1 |
| A pipeline placed from the queue nine hours after its take-in still carried a mover whose fingerprint a newer revision had moved at 03:33 (the series taken over by the newer build), so its build step found the old build done but holding no number, and the pipeline failed: the rule that a moved mover leaves a pipeline (H-A-223) was applied to running pipelines only (rows 90 and 112); the pipeline runner (`mesh-delivery-pipeline`) and the builder. Settled by H-A-244 (the rule holds for every pipeline not ended; the builder's answer for such a build says "stale: its series moved", never "no version is reserved"), in build in the runner and the builder. | H1 |
| A package's version tag (`go/v0.1.59`) stood at another commit on the forge, so the version-released event could not write it and was given up after five deliveries while the publish went on (row 101); the builder. Settled by H-A-245 (the builder reads the tag through the seat git before reserving a number, and takes the next free one, with the finding version-tagged-elsewhere; a tag is never moved). Owed: its build in the builder. | H2 |
| The bus module's warrant fix (row 114) was reviewed in two rounds and merged at 11:28, and taken in three minutes later as a pipeline of two movers (the bus module and the router). The same take-in proved the hand-placed indexer and forge module (row 117): the forge's listing answered not-found for the gone directory, and the take-in went through where every one since 2026-11-17 had said "not published" (row 110). The bus module's hand pack is built from that merge and placed on the control-node next; then the registry's incoming store is dropped on the operator's warrant at the approve level and made again empty; the bus module and the runbook. | H1 |
| With the bus module's hand pack placed (11:35), the drop of the registry's incoming store was refused by design (the store is asked for again, row 106), and the rebuild was asked at the approve level: the router offered it on Telegram at once, the operator chose Rebuild, and the keeper took a snapshot and rebuilt the store empty at 11:39:46, so row 104's recovery is done (rows 104, 114 and 122); the bus module. Seen beside it: the keeper does not withdraw the ask of a request it refused at once, so a dead "remove it?" stayed on the operator's channel until it expired. Owed: the keeper withdraws the ask of a request it refuses. | H1 (the recovery); H2 (the withdrawal) |
| The rebuild did not end the flood: the bus still delivers about six thousand messages a second (five to seven megabytes) to the control-node's tool runner, so the listing of that store was one source and not the only one (rows 102 and 104). No tool of the bus module reads consumers by delivery rate or creation time, nor a connection's busiest subscriptions, so the source could not be named from the tools (a missing tool, by the instruction one-question-one-tool). Under reading now: the artifact store's bundle asking the registry's list verb in a loop, while the registry answers by listing a store whole and the answer exceeds the bus's 1 MiB; the bus module, the tool runner (`node-tools`) and the artifact registry. | H1 (the source); H2 (the tools) |
| The flood's second source, read at 11:47: the artifact store's bundle starts a sweep on every finished build and an observation on every want change, each reading the builder's builds state key by key (ten thousand keys, two bus answers each, because the tool runner binds the bucket before every read), the starts queued behind one lock and draining back to back, and it asks the registry's list at every pass though its answer exceeds the bus's 1 MiB: about a third of the six thousand messages a second (rows 102, 104 and 124); the artifact store's bundle, the tool runner (`node-tools`) and the artifact registry. Beside it, the registry refuses that bundle's removals as not the sweep's, so the store never shrinks. Settled by H-A-250 (one pending pass, one paged read, a loud stop with the finding artifact-list-unread) in the artifact store's bundle and H-A-251 (the tool runner binds a state once) in the tool runner, both in build. H-A-257, H-A-258 and H-A-260 amend the followed view: its first view is the watch's handover, a build's end comes from the builder's log, and an unread end holds the pass and raises the finding artifact-builds-unread. Owed: the registry's list paged (with row 102), and the sweep's removals taken by the registry. | H1 (the two fixes); H2 (the list, the sweep's refusal) |
| A pipeline's validate passed at 11:40 and the pipeline runner dropped its end: the one validate ask names no mover, the holder's end names the mover whose body it took, and the runner compared it with the first step carrying the ask ("a step's end the runner does not take"), so every mover's validate stayed running and the pipeline held the slot until the lead cancelled it, proof 1's behind it; seen at 01:11 too; the second of row 113's kind, a shared ask read as one mover's (rows 113 and 118); the pipeline runner (`mesh-delivery-pipeline`). Settled by H-A-252 (a validate end matched by its ask alone ends every mover's validate step; the same for the composition's shared runs), in build in the runner with rows 112, 113, 118 and 120. | H1 |
| Proof 1's second run passed its pipeline: merged at 11:07:56, taken in at 11:10:47, placed at 11:48:00 after thirty-seven minutes in the queue behind five older pipelines (one held nine hours by a lost ask, one by a dropped end), and built, tested, validated and composed by 11:49:06, sixty-six seconds from placement; the queue, not the pipeline, took the time (row 111); the pipeline runner (`mesh-delivery-pipeline`). | H1 |
| The pipeline's wants were written only at 11:54:21: the holder of the seat mesh-wants runs its pass (the assignment graph, the tiers' judgement, the wants) only when a catalog revision arrives, so a passed pipeline waits for an unrelated merge's take-in (five minutes here, twelve for an earlier one) (rows 111 and 127); the holder of the seat mesh-wants (`mesh-delivery-assigner`). Settled by H-A-256 as H-A-259 corrects it (row 131). The node-engines on the desktop and the build node took the new want within a minute and updated the module's tools bundle, the files bundle following the composer. | H1 |
| The SDK's paged read of a state takes a key as its cursor while the bus reads no key range, so a page read replays the bucket once per page, and a large state read in pages costs more than key by key (rows 102 and 125); mesh-sdk, the tool runner (`node-tools`) and the artifact store's bundle. Settled by H-A-255 in H1 (the artifact store's bundle reads the builder's builds from a followed view, no bus read per pass), amending H-A-250 and H-A-254. H-A-257, H-A-258 and H-A-260 amend the followed view: its first view is the watch's handover, a build's end comes from the builder's log, and an unread end holds the pass and raises the finding artifact-builds-unread. Owed: H-A-254 (pages in sequence order with an opaque cursor, a contract change). | H1 (the view); H2 (the cursor) |
| The pipeline runner's change for rows 112, 113, 118, 120 and 126 was built as eight commits and approved in three rounds (the rounds found a validate rerun covering one mover only, bounds that expired while the runner was down never heard, and a restart asking an answered step again), and is merging now; the pipeline runner (`mesh-delivery-pipeline`). The reviewer's notes stay owed: a holder restarted at the same build with its health unchanged says no new running, so its lost asks are not put again until the seats' asks travel through a work queue; and the builder's build log does say a build started, a first word H-A-241 could use (rows 112, 118 and 126). | H1 (the change); H2 (the notes) |
| Row 128's cause corrected: the holder of the seat mesh-wants does wake its pass on the pipeline-ended and running events, but each pass that keeps a fresh assignment graph revision sits six to eight minutes keeping and removing revisions (every unlisted entry object read one at a time, the kind of row 125), so a wake waits for the blocked pass: feh's wants at 11:54 were the end of a pass begun at 11:46 (rows 125 and 128); the holder of the seat mesh-wants (`mesh-delivery-assigner`). Settled by H-A-259, which corrects H-A-256 on the cause (the keeping runs off the pass loop, one at a time; its judgement reads the entries in one read; each pass and keeping logs its duration), in build in the holder. | H1 |
| Between 11:50 and 12:03 four changes merged and were each taken in within a minute or two: the SDK's held findings writer (rows 117 and 119; its release re-pins 126 modules into one pipeline), the indexer's finding kinds (row 119; its merge was held seven minutes until the SDK's Go package was published, so it builds against the new version), the tool runner's bind once (row 125) and the pipeline runner's bounded asks (row 130). Their hand packs go onto the control-node now; the queue of pipelines behind them runs for hours, the one of 126 movers above all (row 111); the runbook. | H1 |
| Proof 1's one line never reached the file: the wallpaper module is a moved module, so its template file is the provisioner's to fill (ADR 0349 §4); the node-engine deletes the file's content and hands a plan line to the provisioner, and the provisioner's client renders the files archive on the machine. The provisioner on the control-node runs a build from before the indexer's view rename, asks every minute for a first view the indexer no longer serves (503, no responders), and has made no plan since 2026-11-20 09:41; its own pipeline was the one cancelled in row 126, so no current build of it exists. The node-engines did take feh's new want and its tools bundle within a minute, and the builder did publish the new files archive (its digest moved twice since 2026-11-20) (rows 126, 127 and 128); the provisioner and the runbook. The provisioner goes onto the control-node as a hand pack from main on the operator's word (row 117), and its plan then names the new archive. Owed: a cancelled pipeline's movers get a pipeline again by themselves. | H1 (the pack); H2 (the cancel's movers) |
| The four hand packs went onto the control-node between 12:14 and 12:23 (the pipeline runner with its bounded asks, the indexer with its finding kinds, the provisioner from main, the tool runner for seventeen units), every unit active: the provisioner composed every machine from 12:17 without the stale first view; the tool runner's "finding kind not declared" line stopped; the mesh MCP server dropped for a minute at 12:16 and came back by itself; and the big pipeline's validate (row 126's kind) was asked again with the fixed verb at 12:23 and runs under its bound (rows 117, 130 and 133); the runbook. | H1 |
| Proof 1 (its second run) is shown: the wallpaper file on the desktop and the build node carries the merged line, read at 12:26. The chain: merged at 11:07:56, taken in at 11:10:47, placed at 11:48:00, passed at 11:49:06, the want written at 11:54:21, the node-engines applied it within a minute, the provisioner's plan named the new files archive at about 12:23 once a current provisioner ran, and the file was written by 12:26. No hand act touched the module's own path; the hand acts were on the delivery system's parts (the assigner on the build node, the cancel of the held pipeline, the provisioner). The time from merge to running was 78 minutes, 37 of them in the queue and 30 waiting on a stale provisioner, so ADR 0282's five minutes is not met (rows 111, 127, 128 and 133); the runbook. | H1 (the proof); H2 (the bound) |
| Proof 2 began: the SDK's one-line change and the tool runner's were merged in one call at 12:26:59 (the seat git's merge verb with two members), the gate moved main's source to one revision for both repositories, and the indexer took both in together at 12:27:18 as one pipeline of 126 movers, the SDK and the tool runner among them (the SDK's release re-pins every importer); the pipeline waits fifth in the queue (rows 127 and 135). The acceptance: the tool runner runs on every machine at the new SDK version with no hand act; the gate, the indexer (`mesh-delivery-indexer`) and the pipeline runner (`mesh-delivery-pipeline`). Owed: a tool that reads one pipeline's movers, with the lighter read per step (row 124's kind). | H1 |
| The change of the holder of the seat mesh-wants for row 131 was built, reviewed in two rounds and merged at 12:41 as its own pipeline; the first round found wants written at the start before any revision is kept, and the full-store verdict moved out of the pass, both settled by H-A-261 (no want before a revision is kept; the full-store verdict is the pass's own); the holder of the seat mesh-wants (`mesh-delivery-assigner`). The reviewer's notes stay owed: the bus wrappers' race on one handle, met twice (a handle per goroutine, or a guard in the SDK), and a failed first keeping holding the wants until the next event. Also seen: with the pipeline runner's change live, the waiting pipelines collapsed as designed at 12:38 (three left the queue, their movers moved by the newest), so proof 2's pipeline stands next after the one running (rows 130, 131 and 136). | H1 (the change); H2 (the notes) |
| The pipeline ahead of proof 2 (774 steps) made no step the pipeline runner said from 12:42: four contracts modules added to their repository after the registrations' seed of 2026-11-14 were never registered (the seed writes only when no registration is held, and nothing registers a module that enters the module graph later), so their steps waited on a registration nobody had asked, with no bound and no finding (rows 112 and 136); the indexer (`mesh-delivery-indexer`) and the pipeline runner (`mesh-delivery-pipeline`). The build seats were in fact working the other movers while the usage view said none, because it judges a build module by the node-engine's held phase rather than its running asks. The recovery: the four were registered by the register verb, each an Approve on the operator's channel. Settled by H-A-262 (the indexer registers a module the moment it enters a watched trunk's module graph, with no ask, saying registration-changed; the runner raises the finding registration-missing while a mover waits on one), in build in the indexer and the runner. Owed: the usage view judges a build module by its running asks. | H1 (the fix); H2 (the view) |
| The pipeline ahead of proof 2 ended at 13:13:18, its contracts movers still unregistered, and proof 2's pipeline took the slot the same second, placing 182 steps within fifteen seconds; its three contracts movers wait on the same registrations (four Approves open on the operator's channel since 12:59, asked by the indexer at the lead's register calls); a newer merge took 28 movers of the delivery repository out of it at 13:22, while the SDK and the tool runner stay in it (rows 136 and 138); the pipeline runner (`mesh-delivery-pipeline`). | H1 |
| Row 138's fix was built in the indexer and the pipeline runner, reviewed in three rounds and merged at 13:22 as its own pipeline; the rounds found a finding that never cleared, three design points (a pending proposal is skipped; a module the seed left out is not registered by the graph; the branch is the one the siblings hold alike, else the repository's default) and an untested rule, settled by H-A-263, H-A-264, H-A-265 and H-A-266 (row 138); the indexer (`mesh-delivery-indexer`) and the pipeline runner. Its hand packs go onto the control-node next, so the indexer's start pass registers the four modules itself. Owed: a read of the registrations store in one call. | H1 |
| The hand packs of row 140 went onto the control-node at 13:27 and 13:28: the indexer's start pass registered a fifth unregistered module at once (a networking contracts module nobody had noticed) and skipped the four whose proposals were pending, as H-A-265 asks; the lead had those four proposals dropped with the indexer's own tool (the operator's four asks cancelled with them), and the next start registered the four at 13:28:29, each at version 1 with the warrant "module graph". The pipeline runner (`mesh-delivery-pipeline`) at its start said 115 movers of proof 2's pipeline "have no registration yet" before its view of the registrations had loaded, then placed 1048 of their steps at 13:30:55: a fault of the start order of the runner's new check, loud and passing (rows 138, 139 and 140); the indexer (`mesh-delivery-indexer`) and the pipeline runner. Owed: the check waits for the view's first read. | H1 (the registrations); H2 (the start order) |
| Proof 2's pipeline ran from 13:13 with over a thousand steps: the SDK's new version 0.1.29 was published, and the build node built modules against it from 13:58; the tool runner's six steps passed in it. Then the revision of the register-at-take-in merge (13:22) and the indexer's recomputes moved the tool runner and about a hundred other movers to the newer pipelines, as the rule says, so the proof's acceptance follows the tool runner's want on each machine rather than one pipeline's end; the superseded pipeline keeps running its remaining movers (rows 136, 139 and 141); the pipeline runner (`mesh-delivery-pipeline`). Owed: a read of a pipeline's record for one mover's steps (62 KB) still exceeds a reader without a shell, the lighter read of row 124's kind. | H1 |
| The pipeline that carried the tool runner after the move of row 142 ended failed at 15:03:55 on the required steps of three modules of the catalog repository, none of them the tool runner's (its build, tests, validate and composition all passed, its release 0.1.37 reserved): the forge module's TypeScript build cannot find the contracts package it imports and uses fields its contracts type lacks, and its integration test of the whole seat fails; the bus module's integration test of the whole module fails on the subtest "the fill pass runs while the first view is asked", the one every developer tonight reported as failing at trunk and skipped (by the rule of the second failure, the kind is fixed now, not skipped again); and the registry's integration test of the whole module fails; so no pipeline wrote a passed end for the tool runner, and its want stays. Seen beside it: the earlier pipeline passed at 14:26, but the holder of the seat mesh-wants wrote no want for its eleven remaining movers (its record of the pipeline's end names none of them; the SDK's want still names the morning's pipeline); and the builder has asked the registry to publish the tool runner's release again every few minutes since 14:50, with no "published" answered. Under reading (rows 104, 137 and 142); the forge module, the bus module, the artifact registry, the holder of the seat mesh-wants and the builder. | H1 |
| Row 143's causes, read by 15:30: (a) the Node build module places only the SDK into a trunk build and leaves out every other mesh package a package file names, so the forge module's TypeScript build has failed at every build since 2026-11-19 (H-A-267: every named mesh package at its latest published release, as the Go build module does through the pins); (b) the bus module's subtest waits for a first view's "answered", which the keeper never marks for an empty view, so it could never pass (H-A-268: the test waits for the first fill pass); (c) the builder reads every reservation per published event, fifteen seconds apiece, its consumer thousands behind, while its loop asks the same release to be published again every few minutes (H-A-269: one read by digest; no publish asked again while a published is unheard); (d) the holder of the seat mesh-wants skips in silence a passed pipeline's mover whose version the pipeline runner has not yet written, and the version waits on (c) (H-A-270: the skip is said; the runner says pipeline-ended again when a version is written after the end). All four fixes are in build, one owner each; the Node build module, the bus module, the builder, the holder of the seat mesh-wants (`mesh-delivery-assigner`) and the pipeline runner. The failure words of the registry's whole-module test and the forge's whole-seat test could not be read, because the runner's step outputs store holds no bytes for them (the rows of 18:40 and 19:50 on step outputs). The assigner's keeping fix (row 137) went onto the build node by hand at 15:25, and its passes now take 3 to 25 seconds (rows 124, 137 and 143). Owed: step outputs kept and readable. | H1 (the four); H2 (the outputs) |
| The builder's loop asking the publish of the tool runner's release 0.1.37 again (row 143) had a second cause under the first: the artifact registry holds that version at another digest than the build's, so even a heard "published" would not have marked it, and the asks would have gone on until the version ended unreleased; the kind of row 121, met on a registry instead of a tag (rows 121, 143 and 144); the builder. Settled by H-A-275 (a number a registry holds is never reserved; a done build so caught moves to the next free number, with the finding version-held-elsewhere) and H-A-274 (a registry record holding the built digest ends the publish as published), in build in the builder. The builder's fixes of the reading of events and the publish asked again (row 144 (c)) were approved at 15:45. | H1 |
| Row 144's four fixes were built and reviewed by 16:00: the Node build module's and the bus module's test (merged at 15:49 as a pipeline of 36 movers; the Node build module's pack goes onto the build node by hand, so the forge module's build can pass in it); the builder's (approved in two rounds; the second found that every artifact carries its version at build time, so a build whose number a registry holds at another digest is built again at the next free number rather than moved: H-A-279); and the pipeline runner's and the assigner's (approved in two rounds; the first found that a passed mover with no version yet must hold its tier, else a later tier is wanted before it: H-A-277). The merge of the runner's and the assigner's waits on the operator's word, because the session's permission check refused the lead's dispatch of it (row 144); the Node build module, the bus module, the builder, the pipeline runner (`mesh-delivery-pipeline`) and the assigner (`mesh-delivery-assigner`). | H1 |
| The tool runner (`node-tools`) sits in no live pipeline: its last one failed on other movers (row 143) and its fingerprint has not moved since, so nothing builds it again until a merge re-pins it; a module stranded by a failed pipeline gets no pipeline by itself, the kind of row 133's cancelled movers (rows 133, 142 and 143); the pipeline runner. Proof 2 therefore runs a second time, with a new one-line merge of the SDK and the tool runner once the fixes are live. Owed, as one rule: the movers of an ended pipeline that have no passed end are put in a pipeline again at the next kept revision. | H1 (the second run); H2 (the rule) |
| The builder's fix (rows 144 (c) and 145) merged at 15:59 and went onto the build node as a hand pack at 16:09 (its program only, the tools bundle left, so the mesh MCP server stays up; a publish in flight was cut by the restart and is asked again). Within three minutes the builder dropped the tool runner's held release 0.1.37 for a new fingerprint of the tool runner that a fresh pipeline carries, and reserved 0.1.38 for it; its loop that asks a publish again now waits, saying so every thirty seconds, while its events consumer's backlog of about 3,800 messages drains under the bound of a hundred at about one and a half a second (some forty minutes). The Node build module's pack went onto the build node at 15:59 too, and the forge module's build moved into the newest pipeline behind the Node build module's files (rows 144, 145 and 146); the builder, the Node build module and the runbook. | H1 |
| The builder's events backlog (row 148) drained at only fifty a minute under the new builder, holding up every publish and so every pipeline waiting on one: a published at a version many reservations share still cost three seconds (the fallback by version read every reservation at the version, and the journal line read them all again), and the SDK's event hub pulls five hundred messages per pull and handles them one by one, so buffered messages outlive the thirty-second ack wait and are given again (almost every outstanding message redelivered) and handled twice. Every recovery loses something (a purge of the consumer would drop take-ins, source moves and conditions among the publisheds), so the backlog drains while the fixes build (rows 144 and 148); the builder and mesh-sdk. Settled by H-A-280 (each reservation read once, the fallback only over the unbuilt ones, in-progress sent before long work) in the builder and H-A-281 (the hub pulls at most twenty per pull and keeps a slow handler alive with in-progress) in the SDK for every module, both in build. | H1 |
| Row 149's two fixes: the builder's (each reservation read once, the fallback over the unbuilt only, in-progress before the slow pass) was approved and merged at 16:47 as a pipeline of eight movers, its pack for the build node following; the SDK's (the event hub pulls at most twenty messages per pull and sends in-progress every third of the ack wait for a handler still running) is built and in review, and reaches every module at its next build against the new SDK release (row 149); the builder and mesh-sdk. | H1 |
| The SDK's event hub fix (row 150) merged at 16:51, and its release re-pins 126 modules into one pipeline, the tool runner among them. Every merge of the afternoon moved the tool runner to a newer pipeline before the older one could pass (rows 142 and 147), so the lead holds further merges from 16:52 until the queue runs through to the tool runner's pass; the one approved change still unmerged (row 146) waits on the operator's word. The builder's read-once pack goes onto the build node meanwhile, so the events backlog drains faster (rows 142, 146 and 150); the pipeline runner (`mesh-delivery-pipeline`), the builder and the runbook. | H1 |
| The builder was built again against the SDK's hub fix (row 151) and placed on the build node at 16:58 (its read-once pack at 16:52 before it, with no change in the drain rate): the redelivery stopped (two redelivered, against 175 before; nineteen unacknowledged, against the batch of twenty), and the drain rose to about 1.2 messages a second, so the backlog of 2,167 at 17:05 falls under the bound in about half an hour. What remains is about one second of work per event. Each restart of the builder cut one publish in flight, which the loop asking a publish again asked again; the tool runner's release 0.1.40 waits in main.117 on thirteen publishes (rows 149, 150 and 151); the builder. Owed: the cost per event of the builder's published handling, measured and cut. | H1 (the fixes live); H2 (the cost per event) |
| Once the builder's backlog had drained (17:19), the tool runner's release could not publish for another reason: the tool runner imports about twenty packages its own pipeline releases, each package's publish re-pins it (H-A-204), each re-pin keeps a revision of the same source, each such revision's pipeline takes it out of the running one (H-A-223), and each newer build withdraws the older before it publishes; its release ran from 0.1.41 to 0.1.48 in nine minutes with none published: a livelock for any module that imports many packages of one pipeline (rows 142, 147 and 152); the pipeline runner (`mesh-delivery-pipeline`) and the indexer (`mesh-delivery-indexer`). Settled by H-A-283 (a re-pin revision of the same source keeps a mover in its pipeline and asks its build again there; only a new source moves movers), in build in the runner. Owed: pins taken from the reservation and confirmed at publish, so a release re-pins once. | H1 (the runner); H2 (the pins) |
| The pipeline runner's fix for the re-pin livelock (row 153) took two review rounds: the first found the placed-again steps' ask ids equal to the ids the runner had just dropped (the build node refuses a dropped id; the work queue dedupes the composition's; a restart found none of them), and a kept mover placed later reading the branch's held view instead of its kept revision. H-A-286 settled both (every ask id of a kept mover carries its kept revision; its entry and pins are read at that revision wherever it is placed or pin-checked), and H-A-287 aligned the rule of one validate: a pipeline has one validate run, which a kept mover's own validate ask joins. Approved at the second round and merged at 18:01 into a pipeline of its own, with its hand pack for the control-node built beside it; merges are held again from then (rows 112 and 153); the pipeline runner (`mesh-delivery-pipeline`). Owed: the runner's unplaced line for a kept mover whose revision is not yet readable. | H1 (the fix); H2 (the line) |
| While the re-pin fix (row 154) was built, the pipeline carrying the tool runner (row 151) ended at 17:45 could-not-run: its build ask on the build seat had no word from its holder within the silent bound of forty-five minutes (row 118), because the tool runner's build at that pipeline's fingerprint had been withdrawn by the re-pins' newer builds before it could answer; the tool runner then rode the newest re-pin revision's pipeline, nine of them waiting in the queue; the fixed runner, placed on the control-node by hand at about 18:05, keeps it there from now on. The builder meanwhile says the tool runner's release 0.1.55 is queued at the distribution already, while the registry holds nothing of it; the distribution's word is being read (rows 111, 151 and 153); the pipeline runner (`mesh-delivery-pipeline`), the builder and the artifact registry. | H1 |
| The re-pin fix (row 154) was placed on the control-node by hand at 18:05, and the pipeline runner started clean; but the pipeline of row 155 still held the slot: every one of its movers had left to newer pipelines and its last open step had ended could-not-run at 17:45, yet it counted as running, with nine pipelines waiting behind it. The lead cancelled it at 18:08, the second pipeline of this kind to hold the slot with nothing left to do (row 112 was the first) (rows 112, 154 and 155); the pipeline runner (`mesh-delivery-pipeline`). Settled by H-A-288 (a pipeline ends, and the next is placed, the moment nothing of it is open: at the last mover's leave, at the last open step's end in any outcome, and at the runner's start pass), in build in the runner. | H1 |
| The cause of row 156's held slot, read from the pipeline runner's code and the control-node's journal: the pipeline did judge its end at 17:45, but never wrote it; the runner computed every mover's widens inside the end's compare-and-set loop (126 movers, each asking the seat mesh-grants and cut after five seconds, about eleven minutes per try) while the pipeline's key kept changing under it, so every write was refused and the reads were made again (212 cuts between 17:45 and 18:05) until the restart, and the start pass judged no ends (rows 112 and 156); the pipeline runner (`mesh-delivery-pipeline`). Settled by H-A-289 (the reads an end needs are made once before the compare-and-set and shared by every mover and every retry; a retry reads only the key again), beside H-A-288's end pass at the start; in build in the runner. Owed: the five-second cut of the seat mesh-grants's answer itself (rows 69 and 115). | H1 |
| The tool runner's release 0.1.55 (queued at 17:47) waited more than forty minutes to publish, not lost but at the back of the builder's publish queue: a state bucket with one key per holder and version, worked one version at a time, oldest first, the whole bucket listed and read again before every send (about 1,900 subjects; the read tool timed out on it), and every start of the builder asks a publish again for every done build without a release, so old versions of many modules ride ahead of the ones a pipeline waits on; the second slow drain in the builder today (row 149 was the first) (rows 149, 152 and 155); the builder. Settled in H1 by H-A-290 (a publish a pipeline's step waits on goes before any asked again at a start; a withdrawn or taken-over build never publishes; one listing per pass and four sends at a time; a send that does not send says why; the read tool answers at any size), in build in the builder. Owed: the publish queue as a work-queue stream per holder, with tools to drop one item or put it first. | H1 (the five parts); H2 (the stream) |
| The fix of rows 156 and 157 (a pipeline with nothing open ends at once; an end's reads are made once; a journal line at every end) was approved at its first review round without findings and merged at 18:22 into a pipeline of its own; its hand pack goes onto the control-node at about 18:30, the pipeline runner's second hand pack of the evening, after the re-pin fix at 18:05. After the cancel of 18:08 the queue runs again: the next pipeline took the slot at 18:08 with 853 steps; the tool runner rides the eighth pipeline behind it, and its release of 17:47 still waits in the builder's publish queue (rows 156, 157 and 158); the pipeline runner (`mesh-delivery-pipeline`) and the runbook. | H1 |
| The fix that ends an empty pipeline (row 159) runs on the control-node since 18:26; its start pass found nothing to end, the cancelled pipeline having ended at 18:08; the evening's second pipeline runs since 18:08, with the tool runner's seven pipelines behind it. The builder's publish-queue change (row 158) was built with two gaps its developer named: at a start every old unreleased version still rode ahead of the live ones, and a live build waited for a whole start list. H-A-291 settles both (a start asks a publish again only for each module's newest reservation and retires the ones a newer reservation or release supersedes; a live enqueue makes the pass list again after its sends in flight), added before the review, together with a lock on two test fakes that failed the race detector on main (rows 158 and 159); the pipeline runner (`mesh-delivery-pipeline`) and the builder. | H1 |
| With the two fixes of the pipeline runner live, the queue ran through: three re-pin pipelines passed between 18:39 and 18:45 (each with few movers), and the tool runner's pipeline was fourth in line at 18:47. Its release's publish had reached the front of the builder's publish queue at 18:27, in the very minute the control-node's tool runner restarted for a hand pack's bundle, and failed with no responders; the builder did not retry it in eighteen minutes, so the lead asked the publish again through the builder's own tool at 18:46, and it was published at 18:46:46 (the publish-queue fix of rows 158 and 160, in review, makes the retry the builder's own). The passed pipelines reached the control-node as the evening's first asks for a person's approval: the store and the identity provider, each recorded as a module a person moves, asked on the operator's channel at 18:45 and 18:46 before their containers are made again (rows 158, 159 and 160); the pipeline runner (`mesh-delivery-pipeline`), the builder and the node-engine. | H1 |
| The large pipeline of the SDK's release (853 steps, row 159) ended failed at 18:37: the private network module's unit and integration tests failed, and every other mover passed; its movers get no pipeline by themselves (row 147's rule) and will ride the next merge that touches them. The review of the publish-queue change (rows 158 and 160) found one thing: its read tool reads the builder's own states in pages, which H-A-255 forbade for H1 because each page replays the bucket; H-A-292 allows it for a module's own tool when one page of about 768 KB holds the whole state (one replay instead of a request per key), and the review judges the same head again (rows 158, 159 and 160); the pipeline runner (`mesh-delivery-pipeline`) and the builder. Owed: a failed pipeline's movers put in a pipeline again. | H1 (the review); H2 (the re-pipelining) |
| The builder's publish-queue change (rows 158, 160 and 162) was approved at its third and last review round: the second round had found the read tool paging on past one page, and the retire rule crossing version series (a standing 0.2 would have retired a done 0.1.x build); H-A-293 settled both (a one-page read past its page answers the first page and says it is capped, with the state's size; the newest reservation and release are found per module and series), and the fix was judged in one commit. Merged at 19:00 (19:00:35, rebased first onto the fix that ends an empty pipeline, the builder's code unchanged) into a pipeline of its own, with its hand pack for the build node (the program and the tools bundle) built beside it, the first of the evening's packs to restart the build node's tool runner (rows 158, 160 and 162); the builder and the runbook. | H1 |
| A second re-pin pipeline ended failed at 18:58 on one module's tests, the teller's program and tools integration tests, every other mover passing, after row 162's private network module at 18:37. The movers of these pipelines carry only the re-pin to the SDK release with the event hub fix (row 150: pulls of twenty instead of five hundred, in-progress acks), so the kind is read before another pipeline fails on it: whether the tests depend on the old pull size or timing (a regression every module meets), or fail for their own reasons. The tool runner's pipeline is second in line from 18:58 (rows 150 and 162); mesh-sdk, the teller and the private network module. | H1 |
| A third re-pin pipeline ended failed at 19:01 on the zfs module's tools unit test; the read of all three failures (rows 162 and 164) found none of them the SDK's: the teller's test (an ask refused for want of room is asked again) is sensitive to timing and failed five of seven pipeline runs today, four of them before the SDK's change, so its fix starts now under this milestone (the teller is a module of the delivery system); the private network module's three tests read files outside their own module and failed in every pipeline today (a fix for its repository, after the proof); and the zfs module's test has a data race on the peer's id (a fix for the catalog repository, after the proof). The read also met a missing tool: no tool shows a failed step's test output, only its counts and the names of the failing tests, which belongs with the owed keeping of step outputs (row 144). The tool runner's pipeline was placed at 19:03 with 105 steps; its build, lint, unit and integration steps passed, and validate runs (rows 150, 162 and 164); the teller, the private network module, the zfs module and the pipeline runner (`mesh-delivery-pipeline`). | H1 (the teller's test); later (the two others) |
| The publish-queue change (row 163) runs on the build node since 19:03, the program and the tools bundle, the bundle's restart of the build node's tool runner silencing the tools of the mesh MCP server for about a minute (19:05 to 19:06); within three minutes the builder sent two live publishes and said both published, and its read tool answered the queue (empty) with its three standing publish items. Seen at its start: the start pass wrote one line per module no seat can build (about 6,500 lines the journal suppressed), which can hide other lines for a minute, the kind of row 101's burst (rows 158 and 163); the builder. Owed: one summary line for them. | H1 (live); H2 (the summary line) |
| The tool runner's pipeline (row 165) ended failed at 19:09 on the forge module's six integration steps, while the tool runner's own build, tests, validate and composition had passed; a pipeline's wants are written only when it passes, so the tool runner got none, and a failed pipeline's movers get no pipeline by themselves (row 147). It is the fourth re-pin pipeline of the evening sunk by one module's tests (rows 162, 164 and 165), so the lead stops iterating pipelines and fixes the kind under this milestone: the teller's test that is sensitive to timing, the private network module's tests that read files outside their inputs, and the zfs module's test race, each in its repository, while the forge module's six failures are read. The tool runner gets a pipeline of its own at once, by a one-line probe commit in its repository merged as one call (the operator's word of 2026-11-16 on probe merges), built against the latest published SDK release; the one-call merge of the SDK and the tool runner itself was shown at 12:26 (row 136), and this pipeline shows the delivery part of proof 2 (rows 136, 147 and 165); the pipeline runner (`mesh-delivery-pipeline`), the teller, the private network module, the zfs module and the forge module. | H1 |
| The forge module's six failures (row 167) are one test: its whole-seat test over a real bus, added on 2026-11-20, needs the module's npm packages installed, which the Go integration step never has (it fetches the tree without network), so it has never passed in a pipeline and sank every pipeline carrying the forge since, the one of 15:03 (row 143) included; the forge module and the Go build module (`mesh-build-go`). Settled by H-A-294 (a test that needs tooling its step lacks checks its needs first and ends NOT RUN with the reason and where it was proven, the build module's own precedent), in build in the catalog repository. The probe merge of row 167 landed at 19:13 and became a pipeline of one mover, the tool runner, being watched. The first of the four test fixes is built: the private network module's three tests read their facts from copies in the package's own test data, held equal to the originals wherever the repository is whole; the cause was the artifact's declared paths holding only the module's Go directory (rows 143, 165 and 167). Owed: the Go integration level receives a module's npm tree behind a declared need, and a read tool for a run's test output, which answers nothing through the mesh MCP server today. | H1 (the fixes); H2 (the need and the tool) |
| The tool runner's own pipeline (row 167) waited its turn behind the running ones and was placed at 19:20 with eight steps; the fixed builder (row 166) had built and published the tool runner's release 0.1.56 at 19:15, before the pipeline's turn came, the publish sent by the publish-again path within a minute of the build's end. The first test fix (row 168) went to a second review round: it cited an issue instead of its design line (A-474, a module's tests read nothing outside their module), and its drift guard compared the copies against the sibling module's tree, which that line forbids; the guard now holds only the module's own manifest, and the contracts module's facts are proven against copies without a guard (rows 166, 167 and 168); the pipeline runner (`mesh-delivery-pipeline`), the builder and the private network module. Owed: the facts' home is a test in the contracts module. | H1 |
| The tool runner's own pipeline (row 169) ended failed at 19:21 in its composition step: the compose ask met no responders on the node-engines of three nodes at once, while every node-engine answered discovery three minutes later; the lead ran the step again at 19:25 with the pipeline runner's rerun tool, and H-A-296 settles the kind (a seat ask that meets no responders is asked again with a back-off until its bound, never a verdict at once). The remaining three test fixes are built: the teller's test bed now answers the seat-holder ask the live mesh answers (the fault was the bed's, five of seven pipeline failures today), and on the way a live fault of the teller was fixed (two takers of one event since the SDK's views reader took its bare subject; H-A-295 keeps the ask-again for want of room until A-424 is built); the zfs module's test race is fixed, with a real fault of its client beside it (a peer not root whose write was cut was never told "only root"); and the forge's whole-seat test ends NOT RUN when its npm tooling is missing (H-A-294) (rows 165, 168 and 169); the holder of the seat mesh-wants (`mesh-delivery-assigner`), the pipeline runner (`mesh-delivery-pipeline`), the teller, the zfs module, the forge module and the Go build module. Owed: the no-responders wait in the assigner's composition run and in the runner's asks, and the step's own NOT RUN summary in the Go build module. | H1 (the fixes); H2 (the no-responders wait, the step summary) |
| The tool runner's own pipeline (rows 169 and 170) passed after the composition's rerun, and at 19:28:13 the holder of the seat mesh-wants wrote the tool runner's want on every node (the operator's desktop, the laptop, the home server and the control-node) at the new fingerprint and release 0.1.56, step passed-pipeline (read by the lead at 19:30 through the assigner's reasons tool); the mesh MCP server dropped for a minute at 19:29, as the tool runner on the operator's desktop restarted with the new release; the node-engines' start of the new release on each node is being read, and is row 172's. From the probe merge at 19:13 to the wants: fifteen minutes, the rerun's three minutes inside them. This is the delivery part of proof 2 (row 167); the one-call merge of the SDK and the tool runner was row 136's (rows 136, 167 and 170); the holder of the seat mesh-wants (`mesh-delivery-assigner`) and the tool runner (`node-tools`). | H1 |
| The node-engines applied the tool runner's new composition on every node within thirty-five seconds of the wants: the laptop at 19:28:36, the control-node at 19:28:42, the operator's desktop at 19:28:46 and the home server at 19:28:47, each restarting the tool runner because its bundle and its fingerprint changed, and reporting the new build healthy within twenty seconds (the build digest the node-engines report, 0a11dca2…, is the one the builder published as release 0.1.56 at 19:15); the control-node's node-engine had waited a minute for the composition ("the composer has made none yet", 19:27:43), the no-responders episode of row 170. Proof 2 is shown: the SDK and the tool runner merged in one call (row 136, 12:26), the tool runner running everywhere at the new SDK release by its pipeline (rows 167 to 172), no hand act on its path, and the day's hand packs all on the delivery system's own parts (rows 136, 167 and 171); the node-engine and the tool runner (`node-tools`). | H1 |
| The lead's statement (lead-47, on the operator's desktop, 19:31): the freeze on hand placing of the delivery system's parts is lifted (step 8). Both proofs of the runbook's step 7 are shown; every part of the delivery system now runs a build its own pipeline delivered or, where a hand pack of today still runs (the pipeline runner, the builder, the indexer, the assigner, the tool runner, the private network module and the store module, named in rows 134, 148, 160 and 166), a build whose source is merged on main and whose pipeline has passed or runs. From now a change to any part is delivered by its pipeline only, and a fault met is fixed in its repository and delivered the same way; the operator's rule of 2026-11-16 on probe merges ends with this statement. The merge of the change of the assigner and the runner (row 146) waits on the operator's word only because the permission check of the lead's session refused the dispatch, not as a decision. What H1 leaves to H2 is the owed list across rows 150 to 170; the runbook. | H1 (done) |
| Step 8's tail: the two issues the milestone ran under (one held module holds every reader's version back; a change across the SDK, the controller and the catalog repository needs three releases) were resolved at 19:33 with the proofs as the live case, and the second one's last open note (the indexer's dry run of a branch writes that branch's packages into the live packages state the trunk reads) was carried into H-A-297 as owed work. The recovery-mode rules of 2026-11-15 and 2026-11-16 on the lead's side ended with the freeze. The lead's dispatch of two reviewed merges, the change of the assigner and the runner (row 146) and the teller's test fix (row 170), was refused by the lead session's permission check, so both wait on the operator's word and are not routed through another agent; the catalog repository's two test fixes (rows 165 and 170) merge as one call; this branch's pull request is being opened for hq's check (rows 146, 170 and 173); the indexer (`mesh-delivery-indexer`) and the runbook. Owed: H-A-297 (a dry run reads and writes only its own scratch state, and leaves the trunk's packages state untouched). | H1 (done); H2 (the dry run) |
| The catalog repository's two test fixes (rows 165 and 170) merged as one call at 19:29 and became one pipeline of 36 movers: a commit touching two test files moved every module of the repository, because a module's fingerprint takes the repository's commit rather than its artifacts' declared paths; the take-in took eleven minutes, seven of them without a journal line, while the indexer waited on the forge's listing under a busy control-node (the forge at over five cores). This branch's pull request (#797) was opened at 19:35 and had no delivery record or check seven minutes later; the chain from the forge's event to the gate and the checker is being read (rows 168, 170 and 174); the indexer (`mesh-delivery-indexer`), the forge module and the gate. Owed, by H-A-298: a module's fingerprint over its artifacts' declared paths and its manifest, so a commit outside them moves nothing; and a take-in that says what it waits on after a minute, naming the part. | H1 (recorded); H2 (the fingerprint, the take-in's word) |
| The read of this branch's pull request (row 175) found the chain from the forge's event to the gate whole, and the cause elsewhere: hq is not a source repository of the gate, so an hq pull request gets no delivery and no check from the mesh, as none of the day's earlier hq pull requests did (the row of 14:22 on hq's registration); it merges on hq's own checks, run before every commit (ADR 0527); whether hq becomes a watched source with a mesh check is the operator's question (H-A-299). The same read met four live faults after the pipeline of 36 movers: the forge refuses the mesh's admin account since 19:41, which stops the forge watcher and the gate's acts on the forge (796 owed; being read: its cause, and the tool that provisions the account again); the gate's ledger records for two revisions exceed the bus's message size; the forge bridge's store of performed acts is full ("maximum bytes exceeded"); and the deliveries read tool cannot answer per repository (rows 150, 166 and 175); the forge module, the gate (`mesh-delivery-gate`) and the forge bridge. Owed, by H-A-299: one ledger key per module and revision; every store with a cap it prunes toward, a read of its fill and a limits tool; and a read tool that filters before it sizes. | H1 (recorded); H2 (the three); open (the forge account) |
| The forge's refusal of the mesh's admin account (row 176) was the store's absence: the store's container was replaced between 19:41:04 and 19:41:32 (a move the operator approved on their channel), the forge answered 401 for that minute and said the account was refused, and it recovered by itself at 19:42:11 with a fresh token; the gate's views owed on the catalog repository's two merged pull requests failed in that minute and ended could-not-be-performed, with nothing performing them again; the forge module and the gate (`mesh-delivery-gate`). The record's own pull request (rows 175 and 176) was refused by the mesh's merge verb ("its base main is no watched branch"); the day's earlier hq merges went through the forge's own interface, and the lead's session refused to dispatch that, as it refused the two code merges of row 174, so the three wait on the operator. The private network module's pipeline (the fix of rows 168 and 169) passed at 19:46, the first pipeline of the day with that module's tests green (rows 169, 174 and 176). Owed, by H-A-300: an act failing while a part is away stays owed and is tried again with a back-off; the forge module names the cause it can read; one token mint at a time; a tool that performs every owed act of one record again. Owed too: hq registered as a watched source, so the mesh merges and checks it (H-A-299's question). | H1 (recorded); H2 (the owed acts, hq as a source) |
| One more pipeline fell to the store's half-minute absence (row 177): the re-pin pipeline that followed the tool runner's ended failed at 19:43, with many build steps failed and lint steps could-not-run, because the builder's fetch of each source met the forge's 401 in that minute and the builder read the refusal as the build's verdict; the builder. Meanwhile the pipeline of 856 steps holds the slot since 19:46, and the catalog repository's pipeline of 36 movers waits behind it (rows 170, 175 and 177). Owed, by H-A-301, the same kind as H-A-296 and H-A-300: a step whose fetch meets the forge away is asked again with a back-off until its bound, and a fetch failure is said apart from a build failure. | H2 (owed) |
| 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) |
| The held puts (row 181) went onto the operator's desktop at 20:28 and the control-node at 20:30 too, but they only slow the loop: the node-engines still compose the tool runner themselves and restart it every four to five minutes instead of every half minute; the holds stay until the node-engine's fix (H-A-303 and H-A-306, in build) is delivered, and the mesh MCP server drops for a minute at each restart of the tool runner on the operator's desktop. Two more faults were met meanwhile: the pipeline runner's show verb refuses the record it reads ("unknown field kept-revisions"), because the tool runner's new release carries the runner's tools at a release older than the runner's record form (H-A-309); and the catalog repository's pipeline of 36 movers had eleven steps placed at 20:15, then "written meanwhile, so nothing is placed in it now", with no line since 20:17, being read. The packet filter's work stands: ADR 0683 reserved and in its third proposed version; the design amendments to 08 §4, 33 and the glossary (the word "allowance") committed and pushed on their own branch, in review by two architectural domains; the lead answers H-A-308 (an allowance's identity per interface, its expiry by the holder, the verbs' answers) and H-A-310 (the verbs required from the start in one group; ADR 0246 ended for the seats of contracts modules) (rows 180, 181 and 182); the node-engine, the tool runner (`node-tools`), the pipeline runner (`mesh-delivery-pipeline`) and the packet filter module. Owed: a tool decodes another part's record tolerantly (H-A-309). | open (the loop); other (the packet filter); H2 (the tolerant decoding) |
| The catalog repository's pipeline of 36 movers (row 183) was stuck: its placing, cut at 20:15:59 by a concurrent write of the pipeline's record, was never done again; the last test's late progress was dropped without placing what its end unlocked; and the pipeline runner's health said healthy through seventeen minutes with nothing open; a restart of the runner at 20:35 placed 392 steps in twenty seconds from its start pass. It is the second recovery by restart of this kind (row 156 the first), so H-A-311 settles the kind in the runner, in build: a cut placing is done again at once from the record as read again; a late step end still places what it unlocks; a running pipeline with nothing open and nothing placed for five minutes is unhealthy, and said. The packet filter's build moved: the seat's definition, made whole (six verbs, the event, the state, generated Go and TypeScript packages), is committed in the networking repository, and the holder's build follows (rows 156, 182 and 183); the pipeline runner (`mesh-delivery-pipeline`) and the packet filter module. | H1's tail (the runner); other (the packet filter) |
| The node-engine's fix of the restart loop (rows 180 and 181) is built and in review: a held module's slice of the tool runner's process is copied verbatim from what runs, so a holding pass has a digest equal to what runs and writes no revision; the withheld part is said once, naming the holder asked; the developer read the restart cause in the home server's journal ("its unit's Environment MESH_TOOL_MODULES changed") and found a failure of the race detector that predates the change. The packet filter's design amendments were read by two architectural domains (seams and tools: eight points; security and upgrade: seven) and settled in H-A-314 and H-A-315; among them: the allowances state takes the template's option of one bucket per machine (a shared bucket would have opened a port on every node); the verbs' classes and the node-engine's grants; a caller not proven is refused; an allowance with an expiry is rendered as a set element with a timeout, so the kernel closes it while the holder is away; a port that a derived rule admits only from the private network is refused unless a source is given; the loaded mark is compared on the allowance's time; and a running holder is not withdrawn when its seat's definition grows. H-A-316 adds a read verb `converged` to the node-engine's seat, so the holder knows its node is adopted; H-A-313 settles the stalled pipeline's journal line (row 184) as the tools program's. The packet filter's seat definition and holder are committed; the node-engine's part and the reviews' additions are in build by two developers (rows 180, 183 and 184); the node-engine, the packet filter module and the pipeline runner (`mesh-delivery-pipeline`). | open (the loop's fix in review); other (the packet filter); H1's tail (the runner) |
| The packet filter's design amendments (row 185) now carry every point of the two reviews by architectural domain, and were pushed on their branch at 20:43 (hq's branch design/firewall-control-verbs, head 8fc4f09d): design 08 §4 with its part "control verbs" (eight lines: the node-engine as the one renderer, asking the holder's allowed verb within its compose-ask bound; a refusal keeping the loaded filter; converged nodes only; each expiring allowance its own one-element set with a timeout; the event heard; the acceptance test proving the drop before the allowance); design 33's part (fourteen lines: the six verbs with their classes and refusals, the event and its family, the state one bucket per machine, the verb `converged` on the node-engine's seat, the settings, the holder's start removing expired allowances); and the glossary word "allowance" (a port of the packet filter opened by the operator through the seat). The adoption text of design 08 moved whole into its own delivered part, to keep the main file under its size bound. The decision record ADR 0683 is in its fifth proposed version, with the same points (rows 180, 183 and 185); the packet filter module and the node-engine. | other (the packet filter) |
| The node-engine's fix of the restart loop (row 185) was approved at its first review round at 20:45 (the reviewer took each part out in a copy and saw the tests fail; live, the home server's composition still alternated between two digests, which no tool can read word by word, H-A-306 (4) owed); the lead session's permission check refused dispatching its merge, as it refused the three of rows 174 and 177, so four reviewed merges now wait on the operator's word: the change of the assigner and the runner, the teller's test fix, this branch's pull request, and the node-engine's fix; until the last is delivered, the held puts of row 183 stay. The pipeline runner's fix of the cut placing (row 184) is built and in review: a placing refused because the record changed is done again from the record as read again; a late step end places what it unlocks; the health names a running pipeline five minutes without an open step, written once to the tools program's journal. The packet filter's build met two forms the lead's lines had wrong, settled in H-A-317: the state template's option per machine is one bucket whose keys carry the node, so the state's keys begin with the node while the allowance's own key stays as designed; and a holder does not list its seat's event in its manifest's emits, the claim says it (rows 174, 177 and 185); the node-engine, the pipeline runner (`mesh-delivery-pipeline`) and the packet filter module. | open (the loop); H1's tail (the runner); other (the packet filter) |
| The packet filter's decision record (ADR 0683, "The packet filter's control verbs beside the ports derived from declarations") was approved by the knowledge base's own review at its eighth version at 20:46: fourteen clauses carrying H-A-304 to H-A-316 (the derived ports stay automatic; the six verbs; allow and its refusals; one allowance per protocol, port and interface; disallow; allowed and rules; the state per machine; one renderer, with the event; removed at its until; an unanswered read keeps the loaded filter; converged nodes only, with the read verb `converged`; the verbs required from the start; two settings; how it is checked), changing ADR 0170 and ending ADR 0246's optional-first for the seats of contracts modules. It is marked needs-operator and waits on the operator's Approve on their channel (the ask expires on 2026-11-22 at 19:36 UTC); nothing of it is in force until then. Two more forms met in the build after the record's last version are H-A-317 (the state's keys carry the node; the claim says the event) and H-A-318 (allowed asks converged again when it holds no answer); they are facts of the templates, and enter the record as a progressive insight if its review asks (rows 180, 186 and 187); the packet filter module and the knowledge base. | other (the packet filter) |
| The catalog repository's pipeline of 36 movers (row 184) was not stalled after the pipeline runner's restart; it ran unseen: the builder answered its 36 build asks within seconds (every key already built), and the check asks ran on the Go build module of the operator's desktop at about six a minute, with no journal line from the runner for a step's end nor from the builder for an answered ask, so the lead read a stall where the bus showed the work; by 20:48 its builds, lints, units and validates had passed and three integration steps had failed (the Node build module's, its setup over its thirty-second bound, and the recovery module's whole test), so the pipeline will end failed on those, the kind of rows 162 to 165 again. The read also found the asks of the seat mesh-builds on a work-queue stream no consumer takes (1,524 kept), the home server's Go build module taking no check asks, and the unanswered bound not ending asks left untaken for thirteen minutes. H-A-319 settled the packet filter's refusal of a source-bound port as the chain shows it (a port accepted only with a source match) (rows 165, 184 and 188); the pipeline runner (`mesh-delivery-pipeline`), the builder, the Go build module (`mesh-build-go`) and the packet filter module. Owed, by H-A-320: a journal line per step end and per answered ask; the mesh-builds asks consumed, or the stream bounded; every build seat takes check asks; the unanswered bound ends an ask left untaken. Owed too, by H-A-319: the node-engine's render marks each derived rule with its scope. | H1's tail (recorded); H2 (the owed); other (the packet filter) |
| The pipeline runner's fix of the cut placing (rows 184 and 187) was approved at its second review round at 20:54: the first round had found the stalled rule reading the pipelines through the seat's strict decode, which refuses the runner's own property `kept-revisions` (the live cause of the show verb's refusal, row 183), and counting a required waiting step (an approval, a pin-held step) as nothing open; both are fixed, the property dropped before the seat's decode, so show, stands and the health read every record again; the five-minute bound stays a value named in the code with the rule it comes from (H-A-322). It joins the merges waiting on the operator's word, now five (rows 174, 177 and 187). Meanwhile the lead resumed the home server's Go build module, found paused with a capacity of one while the operator's desktop took every check ask (row 189), and the laptop's, whose Go build module a passed pipeline had delivered at 18:20 (main.131, release 0.1.125, read by a watcher); check asks now run on three nodes. The packet filter's design parts are whole at 41005dfc, with every build form through H-A-321 (rows 183, 187 and 189); the pipeline runner (`mesh-delivery-pipeline`), the Go build module (`mesh-build-go`) and the packet filter module. Owed, by H-A-322: a settings form a tools program can read. | H1's tail (the runner); other (the packet filter) |
| The packet filter's build (rows 185 to 190) reached its third repository at 20:56: the node-engine seat's whole definition in the contracts repository gained the read verb `converged` (the node's convergence state: adopted or converged, since when, and the found firewall when adopted) and the composition answer's field `withheld-parts` (which part a compose kept because its read did not answer, and why), with the fixtures and the generated Go and TypeScript packages, the seat generator's check clean; the holder's build takes the verb from that package, and the node-engine's serving of it follows in the fourth repository. The group's heads so far: the networking repository's seat definition (being amended for the reviews' forms), the catalog repository's holder (the same), and the contracts repository's seat of the node-engine (rows 185, 186 and 190); the packet filter module and the node-engine. | other (the packet filter) |
| The packet filter's fourth part is built at 21:08: the node-engine renders one rule per allowance after the derived ports, with the comment carrying the allowance's key and time, a timed allowance as a one-element set with a timeout, and, with no allowance, the filter file byte for byte as today; its compose asks the holder's allowed verb within a new setting, keeps the filter file as it runs when the verb does not answer, without holding the holder's module, says the withheld part once, hears the event on its own node's subject, and serves the verb `converged` from its record. The developer read four facts the lead's lines had wrong or left open, three settled by H-A-324: an allowance with no interface would have opened a node's outward link (a hub's internet-facing one), so "no interface" now excludes outward links too, and an outward link is opened only when named; a timed allowance's render again reloads the filter and arms the remaining time again, accepted; the converged answer's since is optional for older records; and the allowances go to the renderer rather than to the reader of the derived rules, since the adoption's openings read the latter. The group's heads: the networking repository 32f0ade8, the catalog repository 09d57583, the contracts repository efcef83c, the node-engine 9c357b6f; H-A-324's change of the render and the validator's verdicts on the node-engine's manifest are the last subtask before the group's one review (rows 186, 190 and 191); the node-engine and the packet filter module. | other (the packet filter) |
| The catalog repository's pipeline of 36 movers (rows 184 and 189) stood still a second time: every test had ended by 20:53 (the zfs and forge fixes among them, passed), yet two movers waited "for mesh-grants' packages before their build", though those packages had been published at 20:00, before the wait was written, so no publish event ever came for them; the pipeline runner's health said healthy; the lead restarted the runner at 21:15, and its start pass placed them, the third restart of this kind tonight. H-A-326 settles it on the runner's open branch (a wait on a package is a read first and an event second; a pipeline whose movers only wait on packages counts as nothing open for the stalled rule; the journal says which way a wait resolved), so the fifth merge waiting on the operator (row 190) moves to a new head after its review. The packet filter's design gained H-A-325: the holder reads no shape of the loaded table to tell an outward link; the converged answer carries the node's links (the tunnel's name, the list of outward links) as the node-engine classifies them for its render, and a kept allowance names the outward link it opens; the design parts are at 3a969c6b (rows 184, 189 and 192); the pipeline runner (`mesh-delivery-pipeline`), the node-engine and the packet filter module. | H1's tail (the runner); other (the packet filter) |
| The restart of row 193 ended the catalog repository's pipeline at 21:15:30 through the pipeline runner's start pass (row 159's rule that ends an empty pipeline, at work): it ended failed on the Node build module's integration tests, whose setup took forty seconds against a thirty-second bound while three nodes' checks ran, and on the recovery module's whole test; the zfs and forge test fixes passed in it, so their kinds are closed, while the laptop's Go build module stays at its earlier release, since a failed pipeline writes no wants; the next pipeline was placed at 21:15:42 (rows 159, 165 and 193); the pipeline runner (`mesh-delivery-pipeline`), the Node build module and the recovery module. Owed, by H-A-327, of H-A-294's kind: a setup bound read from the step's own bound; a whole-module test that needs the bus's time under load says NOT RUN rather than failing; both fixed in their modules before the next release that carries them. | H1's tail (recorded); H2 (the two tests) |
| H-A-326's read (row 193) met the fact that the pipeline runner's record knows only the publishes it heard, and a package published before a pipeline existed is in no record of it (the two movers' packages had been published by an earlier pipeline at 20:00); the builder owns publishes, so H-A-328 gives the seat mesh-builds a read verb `published` (module, artifact and fingerprint; answering published, version, digest and when), served by the builder from its reservations and the registries' record, which the runner asks once when it writes a mover's wait on a package, the publish event staying the second path. The seat mesh-builds is defined in the delivery repository's own contracts module (not in the contracts repository, as the lead's map had it; H-A-328 is corrected so), so the runner's open branch stays one branch in one repository, holding the seat's definition, the builder's serving and the runner's asking, and the fifth merge waiting on the operator (row 190) keeps one head, new after its review (rows 190, 193 and 194); the pipeline runner (`mesh-delivery-pipeline`) and the builder. | H1's tail (the runner and the builder) |
| The packet filter's group was complete at 21:23, an hour after the operator's decision (rows 180 to 195): the networking repository's seat definition, made whole (the six verbs, the event, the state per machine, a kept allowance naming its outward link, rules listing what is loaded but not kept); the catalog repository's holder (27 tests, type-checked against the generated packages, the catalog's 33 checks green, the manifest validator accepting its manifest); the contracts repository's seat of the node-engine (the read verb `converged` with the node's state and links, the composition answer's withheld parts); and the node-engine (the compose asking allowed within its bound, the filter kept as it runs when unanswered, the render with timed sets and the default excluding outward links, the event heard, `converged` served from the render's own sources); the one review of the four heads began at 21:24. One fact for the pipeline's check: the manifest validator, run against the trunk's seat files, refuses the node-engine's manifest in both cases for a cause that predates the change (two registry seats' versions verbs absent from those files), which the live seat list is believed to carry; the pipeline's own validate decides (rows 186, 192 and 195); the packet filter module and the node-engine. | other (the packet filter) |
| The pipeline runner's open branch (rows 190, 193 and 195) gained H-A-326 and H-A-328 at 21:25 in three commits: a step held waiting on a package's publish counts as nothing open for the stalled rule; the seat mesh-builds gains the read verb `published` (module, artifact and fingerprint; answering published, version and digest), served by the builder from a reservation of that fingerprint whose artifact is marked published, or from a kept release of it; and the runner, when it writes a mover's wait on a package, asks it once per package and fingerprint and places the mover at once when the answer is published, the journal saying "placed from the published record" apart from an event; a package published before the pipeline existed thus no longer holds a pipeline until a restart. Two manifests and the seat's definition changed, so the manifest validator runs before the branch's third review; the approved head of row 190 is superseded by this one (rows 190, 193 and 195); the pipeline runner (`mesh-delivery-pipeline`) and the builder. Owed: the answer's time, never filled because the builder keeps no publish time, with that record. | H1's tail (the runner and the builder) |
| The manifest validator's run on the pipeline runner's branch (row 197) at 21:28 found the change adding no problem: with the branch's seat definition, the change case's verdicts equal the trunk case's for every one of 157 manifests. But the builder's and the runner's manifests are refused in both cases, on fifteen and three lines naming verbs of the registry and build seats that the validator program does not see in the repositories' trunk seat files (they declare acts and accepts), lines the live validate of the same modules passed today; every developer and reviewer runs the validator this way, because the live answer of the seat list is too large to read into a session. The branch's third and last review began at 21:30 (rows 190, 196 and 197); the pipeline runner (`mesh-delivery-pipeline`), the builder and the indexer's manifest validator. Owed, by H-A-329: the seat mesh-catalog answers the seat list as one object a validator run takes; and the validate step counts only the problems new against its before case for a touched module (the reader found it counts every problem). | H1's tail (the runner); H2 (the validator's reads) |
| The two reviews came back at 21:34 and 21:35, neither approving. The packet filter's group (row 196): five findings, one a real fault (the holder accepted an expiry without seconds that the node-engine's time reader refuses, so every later compose would have withheld the filter), the others form (the verbs served before the holder's start had said started; the holder copying the seat's names instead of importing the generated package, the copies already drifted; the seat definition's description of the default set stale; the stored copy of the node's grant lacking the event's subscription), all in one developer's hands; the holder's ten-second bound on its converged ask stays a value (H-A-330). The pipeline runner's branch (row 197), third round: one finding, the published answer never carrying its time, and never the digest for a release, which the builder did not keep; H-A-331 settles it (the publish time kept on the mark from now on, a release keeping its digest, both absent for older records and said so; a withdrawn number never answered published). The lead takes a fourth look at that one commit rather than a fourth round: the rule of three rounds bent for a detail of form, and said here (rows 196, 197 and 198); the packet filter module, the node-engine, the pipeline runner (`mesh-delivery-pipeline`) and the builder. | other (the packet filter); H1's tail (the runner) |
| At 21:40 the operator said not to wait for them, and at 21:41 approved ADR 0683, so the lead stopped holding on the merges and prepared them instead: the four reviewed code branches were pushed and their pull requests opened for the operator's merge (the delivery repository's #317, the change of the assigner and the runner; #318, the teller's test; #319, the pipeline runner's placing fix, approved at its fourth look; and the node-engine's #244, the fix of the restart loop), beside hq's #797 (this record) and #798 (the packet filter's design amendments, now resting on an accepted decision); the runner's branch had its manifest validator run (row 198), and the base of #317 sits seventeen commits behind main but merges clean. The packet filter's group had its five findings fixed in one commit per repository and entered its second review round at 21:44. And the next milestone's design began: a writer turns every item the H1 record names as owed into H2's design lines, with the two proofs that show a change delivered in under ten minutes with no hand act and no restart (ADR 0282), for the reviews by architectural domain and the prepare that follow (rows 173, 187 and 199); the runbook. | H1 (closed); other (the packet filter); H2 (begun) |
| At 21:47 the operator said the lead can and should merge the pull requests, and at 21:48 that they cannot be bothered with them, so merges are the lead's from here, as the mesh's rule on merges says, and the lead will not put a merge to the operator again. By the lead's reading, the earlier refusals were the lead session's own permission check reading the handovers' words ("the operator decides", "a check refused the earlier dispatch") as routing around a review, not a rule of the mesh; a plain handover quoting the operator passed. An agent merges the six at 21:48, in this order: the node-engine's #244 first (it ends the restart loop; its pipeline delivers the node-engines, and then the held puts are released); the delivery repository's #317, #318 and #319 as one call; then hq's #797 and #798, through the forge's interface (rows 174, 187 and 200); the runbook. | H1 (closed); other |
| The merges landed: the node-engine's fix (#244) merged at 21:48:30, and its pipeline passed at 21:50:53, two and a half minutes from merge to pass, the node-engine's want moving on the home server and the control-node at 21:51 (the other two and the node-engines' restarts are being read; the held puts of row 183 are released once the restart loop has stopped); the three delivery fixes (#317, #318 and #319) merged as one call at 21:49, and their pipeline of 23 movers runs. hq's two pull requests (#797, this record, and #798, the packet filter's designs) have no merge path in the mesh: the forge tool never merges (ADR 0266), and the merge verb takes only a watched branch, which hq, registering no module, is not; the lead session's permission check refused dispatching hq's registration as a source, so the operator merges them at the forge for now. The fix of the journal lines (H-A-320 (1)) is built and in review (rows 176, 200 and 201); the node-engine, the pipeline runner (`mesh-delivery-pipeline`), the indexer (`mesh-delivery-indexer`), the gate and the checker. Owed, by H-A-332: a repository with no module registers as a source only; its own check runs as the mesh's; its pull requests merge like any other. | H1 (closed); H2 (hq as a source, the journal lines) |
| The node-engine's fix is delivered: the new node-engine ran on the home server and the operator's desktop from 21:52, each restarting the tool runner once more for a real change (a secret filled) and then no more; the held puts of row 183 were released at 21:54 (the home server) and 21:58 (the operator's desktop and the control-node), and the loop of rows 179 to 181 is over. One smaller flap of the same kind remains: the reads runtime restarts for the node-files holder's words derived from held modules' stubs, and H-A-335 extends the held-module rule to every runtime process the node-engine composes (in build). The fix of the journal lines (H-A-320 (1)) went to a second round under H-A-333 (every said end writes its line in the one place the event is said; the builder's answered line at its one finish; the asked line kept). The next milestone's design part, H2 "the delivery system's owed work", was written (forty-three lines, §775 to §817, with the two proofs: a change delivered in under ten minutes, read from the gate's new delivery time, with no hand act and no restart by hand) and pushed, with hq as a watched source as a line (H-A-334) and the bend of the destroy channel kept; its four reviews by architectural domain run, and a progressive insight on ADR 0668 adds the fault class "away" (rows 181, 200 and 202); the node-engine, the pipeline runner (`mesh-delivery-pipeline`) and the builder. | H1 (closed); H2 (begun) |
| The pipeline of the three merged delivery fixes (rows 146, 170, 184, 187 and 190: the cut placing, the stranded want of room, the versioned end) ended failed at 22:00: the control-node's node-engine restarted its tool runner for a changed fingerprint in one module's words at 21:59, while the forge's bundle took a package's first chunk, so the publish died and the contracts module's build failed, and every mover downstream was not asked; the change itself was sound (every test run passed, and the same build passed on its next try at 22:05). The next merge's pipeline (the journal-lines fix, row 202, merged at 22:01) carried the same movers and re-pinned them to the published packages at 22:06, so nothing was run again by hand. A design's part is reviewed before its prepare: the four reviews by architectural domain of H2's part reported thirty-seven musts and notes in twelve minutes, answered in one batch (H-A-338 to H-A-341) and applied by the writer; and a TypeScript bundle's mesh packages get no catalog edge before its first build (H-A-336, owed in H2b) (rows 146, 170, 179, 184, 187, 190, 202 and 203); the node-engine, the tool runner (`node-tools`) and the Node build module. Owed, by H-A-342: a publish refused by a holder that is away ends the run again like a fetch; and the tool runner drains its calls in flight at a stop, within a bound, before the node-engine starts the new one. | H1 (closed); H2 (begun) |
| The reads runtime's restarts (row 203) are over: the node-engine's fix (a held module's share of the holders' merged words comes from what runs; H-A-335 and H-A-337) was reviewed in two rounds, merged at 22:20 and delivered by its pipeline in three minutes (passed at 22:24), and the new node-engine ran on all four nodes by 22:26; no restart of the reads runtime since 21:57 on any node. Each new node-engine's first pass restarted the tool runner once with a false why (a secret said changed that did not change), as main.151's node-engine had at 21:52, and the mesh MCP server dropped for a minute each time; H-A-348 owes the fix to H2b (the judgement reads what the running unit holds, never only the node-engine's memory). The pipeline of the journal-lines fix (row 202) failed twice on the Node build module's integration tests, three tests, on two build nodes; their kind (H-A-347): since the toolchain lock pins no SDK (G §571), they had read the SDK from a stale toolchain through the "installed last" fallback for ten days, until the desktop installed the current lock at 19:26; the fix (the shared setup supplies the SDK the skipped fetch would place) is in review, and the fallback gains a journal line. The two insights are accepted: ADR 0668 at version 17 (the fault class "away") and ADR 0664 at version 16 (a holder that is away, and the forge's 401 or 5xx on a source fetch, end a run again). H2's part passed the second look of the four reviews (every must answered but six, which are answered as H-A-344 and applied), and is hq's pull request #799, for the operator (rows 202, 203 and 204); the node-engine, the Node build module and the knowledge base. | H1 (closed); H2 (begun) |
File diff suppressed because it is too large Load Diff
@@ -0,0 +1,347 @@
---
layer: to-be
status: in-progress
design: 47
milestone: H
updated: 2026-11-20
decisions:
- "ADR 0499"
- "ADR 0573"
- "ADR 0682"
---
# 47, milestone H — the pin rule: its specification and its gaps
The rule by which a catalog entry pins the mesh packages a module's build resolves, written whole from the lead's
answers H-A-147, 151, 154, 155, 156, 157, 161, 162, 165, 167, 168, 170, 172, 173, 183, 184, 185, 186, 188, 192, 194,
198, 201, 202, 203, 204, 205 and 206 ([H-lead-answers.md](H-lead-answers.md)), G §370
([G-7-answers.md](G-7-answers.md)), ADR 0499 §1 to §4 and ADR 0573 §2 and §4 (the knowledge base), then held against
the code as it stands after the evening's three fix branches.
A word first. The glossary's **pin** is a person's choice of provider for a consumer (Provisioning). This file, as the
lead's answers do, uses "pin" for the version a catalog entry names for a mesh package its module's build resolves.
That is a second sense the glossary does not hold; the proposed word is **package pin** (a catalog entry's version of
one mesh package its module's build resolves, its key the package's Go module path), to be added in its own pull
request. Until then "pin" below means the package pin, and "revision pin" means a record keeping a catalog revision
(the indexer's state `pins`).
## The code read
| Part | Repository | Read at |
|---|---|---|
| The indexer (seat `mesh-catalog`) | mesh-delivery, module mesh-delivery-indexer | main `b9cc9747` plus branch `fix/47-H1-indexer-repin` at `94202fb6` (commits `0418a2b9`, `94202fb6`); the tool commit said to be in progress was not in the branch's worktree (clean at `94202fb6`) |
| The pipeline runner (seat `mesh-pipeline-runner`) | mesh-delivery, module mesh-delivery-pipeline | branch `fix/47-H1-runner-step-pins` at `e3fed775` (commits `a926a40e`, `e3fed775`) over main `b9cc9747` |
| The builder (seat `mesh-builds`) | mesh-delivery, module mesh-delivery-builder | branch `fix/47-H1-builder-revision-picture` at `0fcc614e` (one commit over main; its worktree clean) |
| The Go build module (seat `node-build-go`) | mesh-catalog, module mesh-build-go | main `34a884ff` |
| The delivery SDK's build step and step runner | mesh-delivery, module mesh-delivery-sdk, packages `buildstep`, `steprun` | main `b9cc9747` |
Every fact below names its file and function, read with `git show` at those heads; no line numbers (they move).
## 1. The specification
### What an entry pins
- **S1** An entry's `packages` names every mesh package its module's Go build requires, read from the `require` lines of
the go.mod files at the take-in, at any version, the zero version and `// indirect` included, with no build needed
(H-A-157, H-A-201).
- **S2** The set is transitive across the module graph the go.mod files give, not only the module's direct requirements
(H-A-201).
- **S3** A requirement of the module's own repository is never pinned: it is built from the tree (H-A-198, H-A-201,
H-A-202), whether or not that package is also published.
- **S4** A pin's key is the package's Go module path as go.mod requires it, a nested module's whole path included
(`<repository>/modules/<m>/go/clients/<c>`), never a root path or a module's name (H-A-183: "the package path").
- **S5** A pin's version is the newest version the registry seat published for that package path, as the registry's
published events name it (path and version); never a module's release number, never a commit (H-A-161, H-A-183;
G §370: a Go package's version is its tag).
- **S6** The pin stays within the series the module accepts: the one its manifest names in `packages`, the default
where it names none, whether or not a series value holds contents; a publish in another series pins nothing and moves
nothing (H-A-184, H-A-185). A package artifact's series is its module's version series (H-A-188).
- **S7** The pin is always the newest release in that series; an older version never stands over a newer release
(H-A-167).
- **S8** A requirement of another repository with no published version in its series is named with an empty version,
never left out (H-A-161, H-A-204).
- **S9** A pin is written `vMAJOR.MINOR.PATCH` everywhere it is carried (G §370's tag form; the step contract's
semantic-version form), and only an empty version stands for "none yet".
- **S10** A Go package path another module imports is a declared package artifact of its module; the catalog's check
refuses a manifest whose Go module imports a mesh package path no module declares (H-A-186).
### When an entry is computed and pinned again
- **S11** The entry and its pins are computed at the take-in of every watched branch, for every module the take-in
holds (H-A-157; H §743).
- **S12** A package's publish pins again every kept entry, of any repository and whether or not its module changed,
that names the path with no version or an older one in its accepted series (H-A-165, H-A-204).
- **S13** The pins move on the event, never waiting for a merge or a hand act (H-A-165).
- **S14** A pin that moves moves the importer's fingerprint; the importer becomes a mover, and the builder builds a new
key against the release (H-A-167; ADR 0573 §3).
- **S15** A failed re-pin is not acknowledged, so the publish is delivered again (H-A-167).
- **S16** The indexer answers one entry's `packages` and paths at a revision through a tool, without the whole revision
(H-A-204; tools-are-how-a-module-is-spoken-to).
### What the fingerprint takes in
- **S17** Every form's fingerprint (the version line's and the import form's) takes the module's pins, sorted; a
fingerprint with no pin stays as it was (H-A-167, H-A-172; ADR 0573 §2).
- **S18** The objects of every same-repository module directory the build derives from the go.mod files enter the tree
input, a line per directory, for every form, without being written into the entry; the entry's `paths` keep the
manifest's form (H-A-199 as H-A-202 amends it).
- **S19** A module whose every artifact names its paths takes its tree input from the manifest and those paths (ADR
0499 §2).
- **S20** A build's reported imports refine the go.mod's set and never replace it with an empty one while go.mod names
a mesh package (H-A-157).
### Who carries the pins into which ask
- **S21** The builder takes a build's pins from the catalog entry alone and never computes one (H-A-192).
- **S22** The builder's own build ask of a lane (the trunk build it puts on the build seat's stream) carries the same
pins (ADR 0573 §2: the build writes those versions into its workspace; H-A-192).
- **S23** The runner puts the entry's pins into every step ask's fetch (lint, unit, integration), the same pins the
builder gives the build (H-A-203).
- **S24** A run on request's build step ask names no source revision (H-A-162).
### What waits
- **S25** A build step ask names its branch and source revision; when the builder's picture does not hold that revision
yet, the ask waits for the picture to take it in, woken by the state's change events and by each revision the view
takes in, up to `revision-wait-minutes` (1 to 60, default 2), then fails loud naming the revision and the branch; a
build with no version is never made (H-A-155, H-A-156, H-A-162).
- **S26** The builder's picture holds every kept revision: a revision below the newest it heard is read by number
through the catalog seat's `revision`; only one above the newest is waited for (H-A-205).
- **S27** A build whose entry names a package with an empty pin first asks the package registry seat's `versions` once
for that path and takes the newest in the accepted series; else it waits for the registry's published of that path
and series, up to `package-wait-minutes` (1 to 120, default 10), and pins the version that event carries; past the
bound it fails "package <path> has no released version" (H-A-165, H-A-192, H-A-194).
- **S28** The runner asks a Go artifact's lint, unit and integration steps only when every pin of its entry has a
version; until then the steps stand as "waits on the publish of <path>", and end as the build ends when the bound
passes; the publish pins the entry again and moves the mover to its new fingerprint, whose pipeline runs them
(H-A-206).
### What refuses
- **S29** The Go build module refuses, loud, a requirement of another repository the ask gives no pin for (H-A-192).
- **S30** It never takes another path's version, a sibling's version or the latest for it (H-A-192, H-A-201).
- **S31** It builds a same-repository requirement from the fetched tree, transitively through those modules' own
go.mod files, and keeps those directories in the narrowed tree (H-A-198, H-A-202; ADR 0499 §4: a build sees only its
named paths).
- **S32** A version a repository's go.mod names is read as the oldest it accepts, and nothing more; nobody fixes a
version by hand (ADR 0573 §2).
### What keeps the revision an entry lives in
- **S33** The take-in pins the branch's newest kept revision for the same pipeline record as its own, and writes that
revision's number as the field `base` on the revision it writes, absent on a branch's first take-in; both are freed
with the pipeline (H-A-147, H-A-151, H-A-154).
- **S34** A passed pipeline pins, under `release.<branch>.<module>`, the revision of each mover that released a version;
a newer pipeline's `pipeline-wanted` with outcome running frees it from the revisions below only where the newer
revision holds that module's release record (H-A-168, H-A-170, H-A-173).
### From the records, not judged here
- **S35** A delivery group's check builds its members against the group's own heads (ADR 0573 §4). Milestone H's runs
on request replace the earlier model's group check; whether §4 still asks anything of the pin rule is a question for
the lead, not this table.
## 2. The gap table
Sizes: S one function (under an hour), M one module's part (a day), L the part's shape (more than a day).
| Line | Status | Where | What the code does instead | Size |
|---|---|---|---|---|
| S1 | built | mesh-delivery-indexer: `cmd/.../named.go` (the go.mod read, `fingerprint.MeshRequiresOf`); `internal/index/package_trees.go` `otherRequired`; `internal/index/versions.go` `releasedPins` (branch indexer-repin, its `required` argument) | | |
| S2 | built otherwise | `internal/index/package_trees.go` `sameRepositoryRequired`, `otherRequired` | The reading follows only same-repository modules' go.mod files; a pinned package's own requirements (another repository's go.mod) are never read, so a transitive requirement is pinned only where the module's own go.mod lists it as `// indirect` (a tidied go.mod). | M |
| S3 | built | `releasedPins` (skips `trunk.SameRepository`); `fingerprint.OtherPackages` | The indexer never pins a same-repository package, published or not. The Go build module's side is S31. | |
| S4 | built | indexer `HearVersion` (`GoModule` from the registry's published `Module`), `releasedPins` (`s.GoModule == p`); builder `PackagePublished` (keyed by the published `Name`); mesh-build-go `takeZeroRequirements` (`asked[p.module]`) | The key is the full Go module path on every side. Live: the registry holds `.../modules/mesh-grants/busgrants` at 0.1.48 under its nested path (the indexer's `indexer_package_users`). | |
| S5 | built | `releasedPins` (branch); `fingerprint.WithPins` | The entry's pins are registry versions. The fingerprint's version line still takes commits (leftover L1). | |
| S6 | built | `releasedPins` (`m.AcceptedSeries(s.Name)`); builder `awaitPublished` (`man.AcceptedSeries(p)`) | The rule that a package artifact's series is its module's version series (H-A-188) lives in the catalog's check, outside these modules: not judged. | |
| S7 | built | `releasedPins` (the highest in the series) | | |
| S8 | built | `releasedPins` with `required` (branch indexer-repin `0418a2b9`) | The empty version is refused by a run on request's candidate: `internal/index/candidate_values.go` `checkCandidateModule` runs `sdkstep.PackageVersions.Check`, which accepts only a commit or a semantic version, on `runcandidates.go`'s values copied from the module's `Packages`. A run of a module with a package not yet published fails. | S |
| S9 | built | indexer `releasedPins` (`"v"+`), series kept without it (`HearVersion`); builder `publishedPin` (`"v"+`), `PackagePublished` (trims it); runner `stepAsk` (copies); sdk `buildstep` `PackageVersions.Check` (needs `v`); mesh-build-go `takeVersion` (`path@v…`) | One form throughout. The empty version is the one exception S8 names. | |
| S10 | not judged | the catalog's check (mesh-catalog's manifest check), not one of the modules held here | | |
| S11 | built otherwise | indexer `takeInSource` (`takein_source.go`), `recomputeLocked` (`toolchains.go`) | On the first watched branch every module is computed. On another branch the take-in recomputes only the moved repositories' modules and those whose pins name a package of a moved repository; every other entry is carried from that branch's newest revision with the pins it had. | M |
| S12 | built otherwise | `cmd/.../series.go` `heardVersion` (a registry's published runs `Recompute` of every module); `versions.go` `releaseVersion` calls `repin`; `toolchains.go` `Repin` (branch: by pins and by kept requirements) | Two paths move the pins, both in the first watched branch's view only (`ix.Modules`). A kept catalog revision is never rewritten, and another branch's entries are not pinned again. | M |
| S13 | built otherwise | as S12; `catalog_revisions.go` `keepBranchEntries` is called only from `takeInSource` | The view moves on the event, but an entry anyone reads (the builder, the runner, the node-engine through the revision) changes only when the next take-in of that branch writes a revision, which only a merge on that branch makes. | L |
| S14 | missing | `internal/index/movers.go` `moversOf` | A mover is a module of a moved repository whose fingerprint changed, or a module whose pins name a package a mover publishes. A module whose fingerprint moved by a re-pin is neither, so no pipeline builds or tests it. The builder's picture builds the new fingerprint on its own once a later revision carries it (leftover L5), outside any pipeline, with no test step and no want. | L |
| S15 | contradicts (one of two paths) | `cmd/.../series.go` `heardVersion` | The version-released path returns the re-pin's error, so the package-published is not acknowledged (built). The registry-published path logs a failed `Recompute` and acknowledges the event, so that re-pin is lost until the next publish. | S |
| S16 | missing | indexer tools (branch indexer-repin holds none) | The seat verb `mesh-catalog.entry` answers one whole entry by fingerprint, not at a revision. The tool H-A-204 asks is the commit still in progress. | S |
| S17 | built | `versions.go` `pinnedOf`; `fingerprint.WithPins`; `form.go` `formOf` (import form `stands` kept only while its built pins equal the new ones) | | |
| S18 | built | `package_trees.go` `derivedDirs`, `derivedTree` (main `b9cc9747`, merged #296) | | |
| S19 | built | `fingerprint.NamedTree` | | |
| S20 | built | `form.go` `refined` | | |
| S21 | built | builder `internal/build/step.go` `buildEntry` (entry by fingerprint through `mesh-catalog.entry`, then `awaitPublished`) | | |
| S22 | built | builder `internal/build/run.go` `runLane` (`awaitPublished`, `ask.Packages`) | Its `delete(ask.Packages, fb.Package)` loop runs over `req.Builds`, which nothing sets (leftover L6). | |
| S23 | built | runner `internal/pipeline/place.go` `stepAsk` (branch runner-step-pins `a926a40e`) | Empty pins are left out, so a step waits for them (S28). | |
| S24 | built | runner `place.go` `place` (source 0 for a run) | | |
| S25 | built | builder `internal/build/revisionwait.go` `awaitRevision`, `PictureHeld`; `module.json` `revision-wait-minutes` | | |
| S26 | built | builder `revisionwait.go` `keptRevisionHolds`; `cmd/.../keptrevision.go` `keptRevisionVia` (branch builder-revision-picture) | The kept revision is judged by its source and its fingerprints; the pins used are then the entry read by fingerprint (S21). | |
| S27 | built | builder `revisionwait.go` `awaitPublished`, `PackagePublished`; `cmd/.../versions.go` `publishedVersionsVia`; `cmd/.../seats.go` (the published heard); `module.json` `package-wait-minutes` | | |
| S28 | built otherwise | runner `place.go` (`unpinnedPackage`, `PinWait`, `endPinHeld`); `steps.go` `OnStepEndedShared`, `endPipeline` (branch runner-step-pins `e3fed775`) | A failed build ends the waiting steps with its outcome (built). When the build passes, `endPinHeld` ends none and nothing asks them: a waiting required step holds `endPipeline`, so the pipeline never ends and holds its place in the queue. The line counts on S14 (a new pipeline at the re-pinned fingerprint), which is missing. | M |
| S29 | built | mesh-build-go `cmd/mesh-build-go/pins.go` `takeZeroRequirements` ("no pin for … the builder pins or waits") | | |
| S30 | built | as S29; `versions.go` `takeRequirementsOf` leaves forge modules to their own rule | | |
| S31 | built otherwise | mesh-build-go `pins.go` `takeZeroRequirements`, `useOwnModules`; `narrow.go` `ownZeroPackageDirs` | Only a same-repository requirement at the zero version comes from the tree. One at a real version is fetched at that version through the Go seat, while the indexer's fingerprint takes the tree's objects (S18): the build and its key disagree. The repository test is the literal owner prefix `"novox/"+p.repo`, a value written into the code. | S |
| S32 | built | mesh-build-go `versions.go` `takeVersion` (a newer go.mod version is built, and said) | | |
| S33 | built | indexer `catalog_revisions.go` `keepBranchEntries` (`rev.Base`, the newest pinned in the same write); `pins.go` `HeardPins`, `unpinElsewhere` | | |
| S34 | built | indexer `pins.go` `HeardPins` (a release record only for a mover with a version), `HeardPipelineWanted` (running only; the newer revision's own release record) | | |
| S35 | not judged | | The question of whether ADR 0573 §4 still binds after the runs on request is the lead's. | |
Counts: 35 lines; built 24, built otherwise 6, contradicts 1, missing 2, not judged 2.
### The six points the lead asked about
1. **The pin key's form.** On the branches every side keys by the full Go module path: the indexer from go.mod and the
registry's published `Module`, the builder from the published `Name`, the Go build module by `p.module`. A nested
path is pinned when the registry published that path (H-A-186's artifacts). The builder writes one git tag per
release, `go/v<version>` (`internal/versions/tag.go` `GoTagOf`), never `<package dir>/v<version>`. The fetch asks the
Go seat first, so the tag is not on the path, but if the seat misses and the fetch falls through to the forge's git,
a nested path's `@v0.1.x` is an unknown revision (leftover L9). I think the refusals of nested paths seen earlier
came from the pins of H-A-161 (the module's release number) and the undeclared artifacts H-A-186 names. Both are
fixed on main and on the branches; the running indexer predates them (section 3).
2. **Reported imports against the go.mod graph.** `formOf` takes the import form when a build reported imports, and
`fingerprint.Resolve` gives versions only for the holders of what was imported. Since `0418a2b9`, `releasedPins`
adds every requirement the go.mod graph names (`required`), so the entry's pin set no longer shrinks to the imports.
The `stands` case keeps `prev.Packages` only while those equal the new pins (`pinnedOf`), so a moved pin moves the
fingerprint (S17).
3. **The recompute of unchanged modules of other repositories** (`recomputeLocked`, the held-stands guard). At a
take-in naming repository R, a module of another repository is recomputed only when its new pins name a package of
R (`importsOf`). Since `0418a2b9` that set includes requirements with an empty pin, so an importer of R's package is
recomputed. Any other module keeps its held value. A publish recomputes every module of the first watched branch's
view (`Recompute` on the registry's published) or the modules naming the released module's packages (`Repin`).
Other watched branches are not reached (S11, S12).
4. **The lane path's trunk asks.** `runLane` waits in `awaitPublished` and copies the filled pins into `ask.Packages`
for a Go fetch with any pin (S22). The lane runs both for a step ask and for the builder's own picture-driven builds
(L5).
5. **A same-repository requirement that is also published.** The indexer never pins it. The Go build module builds it
from the tree only when go.mod names it at the zero version; at a real version it is fetched from the Go seat at
that version (S31).
6. **The "v" prefix.** It is one form across the indexer, builder, runner, step contract and Go build module (S9). The
empty version is the one value the step contract refuses, which breaks runs on request (S8).
## 3. The leftovers
| What | Where | What it does | Line it contradicts |
|---|---|---|---|
| L1 The version line's commit form | indexer `form.go` `lineVersions` (`fingerprint.HeldVersionsOf`, the gate's heads for an unpublished package, G A-365); `fingerprint.VersionLine` | The fingerprint takes, for each other-repository package, the held module's commit or the branch head's commit. A merge of a package's repository moves every importer's fingerprint before anything is published. | S5 in spirit (H-A-161: never a commit). The pins themselves are versions. |
| L2 The accepted series' contents read at the published commit | indexer `series.go` `HearVersion` (`packagesAt`), `acceptedSeries` (DLV-I6) | Reads the published version's package digests through the forge for the import form, keeps a commit form where it cannot. | none (ADR 0593 §2's import form), but a second source of package versions beside the pins |
| L3 A whole recompute on every registry publish | indexer `cmd/.../series.go` `heardVersion` | `Recompute` of every module on each published version, beside the targeted `Repin` on version-released. | none; it duplicates S12's path, and acknowledges on failure (S15) |
| L4 The requirements state from go.sum | indexer `requirements.go` (`indexer_requirements`, `keepRequirements`, `RequiredOf`) | Keeps per package the highest version each consumer's go.sum names, for the builder's floor. Under the zero version go.sum names none (H-A-157). | none directly; H-A-157 says go.sum is never read for package edges, and H-A-159 removed the builder's own numbering it served |
| L5 The builder's picture-driven builds | builder `internal/build/run.go` (the picture's take calls `consider`), `Reconsider`, `Sweep`; `numbers.go` `PackageNamed` | Builds every fingerprint a watched branch's picture takes in, outside any step ask. It is the only path by which a re-pinned fingerprint is ever built today. | none of this part's lines (the earlier model's "the builder builds every fingerprint of the catalog half"); a builder that builds what no pipeline asked is a question for the lead |
| L6 Dead pin deletion | builder `run.go` `runLane` (`for _, fb := range req.Builds`) | Deletes from the pins the packages `builds` names, over a list nothing fills. | none |
| L7 Commit pins and pull-request heads | mesh-build-go `versions.go` `takeVersion` (a commit resolved to a pseudo-version, else `placePin` from `refs/pull/*/head`), README "A pin on a pull request's head" | Accepts a 40-hex commit as a pin and places a pull request's head beside the workspace. | S5 (H-A-161: never a commit) for a delivery build; it served ADR 0573 §4's group heads |
| L8 The literal owner prefix | mesh-build-go `pins.go` `takeZeroRequirements`, `narrow.go` `ownZeroPackageDirs` (`"novox/"+repo`) | Decides "same repository" by a written owner name. | principle 11 |
| L9 One Go tag per release | builder `internal/versions/tag.go` `GoTagOf`, `reserve.go` | Tags `go/v<version>` once per module, whatever paths its Go packages have. | none of this part's lines; H-A-183 names `<package dir>/v<version>` as what the forge's Go seat looks for |
| L10 The candidate check on pins | indexer `candidate_values.go` `checkCandidateModule`; sdk `buildstep` `PackageVersions.Check` | Refuses an empty version. | S8 |
## 4. Live against main
Read through the mesh at 23:00 to 23:10 CET with read tools only (`mesh-delivery-view.node_haves`,
`mesh-catalog.entry`, `mesh-delivery-indexer.indexer_package_users`). Machines are named by role; the mapping is a
guess (section 7).
**The indexer**
| Machine | Build that runs | Main's or by hand | What main and the branches have that it lacks |
|---|---|---|---|
| the control-node | fingerprint `src2:9ac151c2…`, its entry at commit `f00d3467` (main, 2026-11-20 17:35 UTC) | the entry is main's commit; whether a pipeline or a hand placed it the tools do not say | 8 commits of main on the module: H-A-183, 184, 185 (the pin by path and series), H-A-186, H-A-200, H-A-201, H-A-202; and both commits of branch indexer-repin. Live, the entries of the indexer and the runner still carry 40-hex commits as pins, and the busgrants user `nats` shows no pin though 0.1.48 is published. |
**The pipeline runner**
| Machine | Build that runs | Main's or by hand | What main and the branch have that it lacks |
|---|---|---|---|
| the control-node | `src2:adf598f2…`, entry commit `9598b92c` (main, 17:37 UTC) | the entry is main's commit | H-A-187, H-A-189, H-A-190, H-A-191 (steps per mover); branch runner-step-pins (H-A-203, H-A-206) |
**The builder**
| Machine | Build that runs | Main's or by hand | What main and the branch have that it lacks |
|---|---|---|---|
| the workstation | `src2:48cabb7e…`, held: "entry-missing … src2:f34620ec…" since 17:49 CET | no kept entry names `48cabb7e`, so I take it for a build placed by hand or from before the clean state | not readable: no entry gives its commit |
| the control-node | removed ("the applied declaration no longer holds the module") | | |
**The Go build module**
| Machine | Build that runs | Main's or by hand | What main has that it lacks |
|---|---|---|---|
| the control-node, a build node | `src2:ae502407…`, phase failed: "the want … names no digest for mesh-build-go:files, mesh-build-go:tools" | no kept entry names it: placed by hand or from before the clean state | not readable |
| the workstation, the laptop | `src2:c69b0f1c…`, the same failure | the same | not readable |
The delivery SDK is a package, not a running module; nothing of it runs on its own.
## 5. The tests
Counted as `func Test` per file; a file whose header carries `//go:build integration` counts as integration. Table
rows inside one function count once.
| Module (head) | Unit | Integration | Starts the module whole against a bus and a store | What the tests would not catch of the gaps |
|---|---|---|---|---|
| indexer (indexer-repin) | 163 | 6 | yes, `TestIndexerWhole` (`takein_integration_test.go`) | It covers revision pins (S33, S34), not pins of packages: no whole test publishes a package and reads the entry pinned again, the re-pinned module made a mover (S14), another branch's entries (S11, S12) or an acknowledgement after a failed re-pin (S15). Unit tests `TestAnEntryNamesEveryRequirementPinnedOrWaiting` and `TestAReleaseRepinsAnEntryNamingItsPackageWithNoPin` (branch) prove S8 and S12 in the view only. |
| builder (builder-revision-picture) | 154 | 18 | yes, `integration_test.go` runs `run` | Nothing ties the lane's pins to an entry with an empty pin across a restart; the branch's unit test proves S26. |
| runner (runner-step-pins) | 91 | 4 | yes, `run_integration_test.go` runs `run` | No test builds a mover whose pin-held steps outlive a passed build (S28); the branch's `testruns_integration_test.go` checks the pins in the fetch (S23). |
| Go build module (main) | 217 | 18 | I found none that runs the module's `run` (guess; section 7) | Nothing fetches a same-repository requirement at a real version (S31) or a transitive other-repository requirement not in the go.mod (S2). |
| delivery SDK `steprun` + `buildstep` (main) | 113 (of the module's 150) | 13 (all in `steprun`) | not applicable (a package) | Nothing runs `PackageVersions.Check` on an empty version from a candidate (S8). |
All five are inside the budget of 500 unit and 50 integration tests per module.
## 6. Fix in place or write again
**The indexer.** Fix in place. 14 of its 21 lines here are built. The pin's computation (S1 to S9, S17 to S20) and the
revision pins (S33, S34) follow the design. Its shape breaks in one place: a re-pin reaches only the in-memory view of
the first watched branch, and nothing turns a moved fingerprint into a catalog revision and a mover (S12 to S14, L).
That is a design question before it is code. A revision is numbered by its source (H-A-32), and a publish has no
source, so the design must say what takes in a re-pin (a take-in the publish itself starts, or a revision of its own
form). The rest are S: the acknowledgement (S15), the empty pin in a run's candidate (S8), the tool (S16).
**The builder.** Fix in place. Its four lines (S21, S22, S25 to S27) are built on the branch, in the design's shape
(events and a bound, the versions verb read before the wait). Its open question is L5: it builds every fingerprint its
picture takes in, outside any pipeline. Today that is the only path that builds a re-pinned key, so it must not be
removed before S14 is built.
**The pipeline runner.** Fix in place. S23 and S24 are built, and S28 is built but for one case: a pin-held step whose
build passed is never asked and never ended (M). It needs a design line for that case, for example asking the steps
with the pins the build resolved, which its step end would have to carry, or ending them "not asked" in favour of the
re-pinned mover's pipeline once S14 exists.
**The Go build module.** Fix in place. S29, S30 and S32 are built; S31 holds only at the zero version and on a
literal owner name (S each). L7, the commit and pull-request-head pins, is the earlier model's and can go once no ask
names a commit.
**The delivery SDK.** Fix in place: one change, the candidate check's treatment of an empty pin (S8), shared with the
indexer.
## 7. What I could not read, and what I guessed
- I could not send the lead an interim status mid-run: this agent has no messaging tool but its final report.
- **The tool commit of branch indexer-repin** was not in its worktree (clean at `94202fb6`), so S16 is judged missing.
Check: `git log fix/47-H1-indexer-repin` once it lands.
- **The builder's and the Go build module's running builds** have no kept entry (`mesh-catalog.entry` answers "no
entry of fingerprint … is kept"), so their commits are unknown. That they were placed by hand is a guess. Check: the
node-engine's composition of those modules on each machine (`<node>/node-engine.composition`).
- **Whether a pipeline or a hand placed the indexer and the runner** is not said by the tools I used; their entries'
commits are main's.
- **The role of each machine** is a guess from the mesh's instructions (the control-node, the workstation, the laptop,
a build node). Check: `mesh-controller.nodes`.
- **The Go build module's whole test:** I searched its tests for a call of `run` and found none. A test that starts it
another way may exist. Check: read its `*_integration_test.go` files.
- **S2 in practice:** whether every mesh go.mod lists its transitive mesh requirements as `// indirect` I did not read.
Check: `go mod tidy` is a lint step, or read a module's go.mod at main.
- **The cause of the earlier nested-path refusals** (point 1) is a guess from the lead's answers, not from a record of
those builds. Check: `records_search` with the refused build's words.
- Line numbers are not given, by this agent's way of working (they move with every commit); each fact names its file
and function.
## 8. The shortest list of changes still missing after the three branches
1. **A re-pin becomes a revision and a mover** (S12, S13, S14). Owner: the indexer (its take-in), after a design
line from the lead or the design writer on what takes a re-pin in, since a revision is numbered by its source
(H-A-32). It also covers every watched branch, not only the first (S11). Size L.
2. **A pin-held step whose build passed** is asked with the pins the build resolved, or ended for the re-pinned
mover's pipeline (S28). Owner: the runner, with a design line. Size M.
3. **A failed re-pin on the registry's published is not acknowledged** (S15). Owner: the indexer, `heardVersion`.
Size S.
4. **An empty pin passes a run on request's candidate** (S8, L10). Owner: the indexer's `checkCandidateModule`, or the
SDK's `PackageVersions.Check` with an "empty allowed" form for entries. Size S.
5. **The tool answering one entry's pins and paths at a revision** (S16). Owner: the indexer. Size S (in progress).
6. **A same-repository requirement at a real version comes from the tree**, and "same repository" is read from a
setting or the fetch, not the literal owner (S31, L8). Owner: the Go build module. Size S.
7. **Transitive other-repository requirements** are pinned from the pinned packages' own go.mod files, or a check
refuses an untidied go.mod (S2). Owner: the indexer, or the catalog's check. Size M; needed only if a go.mod is
found that does not list them.
L1 (the commit form in the fingerprint's version line) is left in place until item 1 lands, since today a
package's merge moving its importers' fingerprints is what makes them code dependents in that pipeline at all.
File diff suppressed because it is too large Load Diff