Design 47's B0 says what was built: the checking program on every check, its input by the checker's verb (issue 1921) #524

Merged

mesh-tools merged 5 commits from docs/47-b0-row into main 2026-11-06 23:01:03 +00:00

Conversation 1 Commits 5 Files Changed 7

+133 -51

5 Commits

Author	SHA1	Message	Date
jschoubben	d676466578	Design 47's B0 says the checker is delivered first and a failed seat list ends the check there (issue 1921, B0 review round 2) ... Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i	2026-11-06 23:56:30 +01:00
jschoubben	da828c147a	Design 47's B0 takes in round 1's rulings: the input asked of the checker's verb, the cycle rule the program's ... A build module reading the checker's state broke ADR 0596 §2, and no record names the cycle rule as an exception to ADR 0656 §5; the code now follows both, and so does the design, with the answer's bound that the build module now enforces. Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i	2026-11-06 23:51:08 +01:00
jschoubben	35b92fde78	Design 47's B0 says what was built, so the review reads the design the code follows ... The first code review round found the B0 section described the input and answer in the build seat's objects, no running rule after B0, and a carry's program built at merged heads. It now says the input is kept in the checker's own state and the answer rides the step key, names the cycle rule and a failed program's wording as the two exceptions until milestone G with why, and says where a carry's program is built and when a trunk move asks a new build. Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i	2026-11-06 23:23:53 +01:00
jschoubben	60369fddee	Design 47's B0 takes the lead's rulings on its open points ... The begin bound of a run ask, the referenced objects' size, the kept programs' tools and their 30-day sweep, and the versioned input were left open by the first amendment; each is now one of B0's choices with its reason, as ruled, so the developers and the review read one text. Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i	2026-11-06 22:10:14 +01:00
jschoubben	12489d580c	Design 47's B0 names the trunk's homes and runs the checking program on every check ... Row B0 named mesh-delivery-contracts for the ask `run`, but the registry group creates that module and joins milestone G, after B0; on every trunk before G the seat's types are mesh-sdk's go/delivery and go/composer, which G's merge moves (ADR 0634 §4, ADR 0635 §4). The bootstrap section now says every check runs the checking program (a lone pull request a group of one, a carried verdict included), that the program makes the heads' seat list, and carries the seams review's three findings on B0's prepare as the design's own choices with their reasons: a dropped `run` ask fails by name within a bound, kept programs have tools and a sweep, and the input goes by reference with a size bound. The glossary gains "seat list", used as a term by ADR 0635, ADR 0636 and design 47 without an entry, retiring "seat set" in hq; four designs take the word, and issue 299's narrative keeps its day's word by an allowance row. Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i	2026-11-06 22:08:31 +01:00