100 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
jschoubben	656f3af86f	Merge pull request 'R4g+R5 (hq): its checks as Go tests; design 47, the glossary and playbooks say what R4g builds (design 47)' (#470) from feat/r4g into main ... Reviewed-on: #470	2026-10-23 17:54:31 +00:00
jschoubben	e8bd9171cd	Design 47: the gate reads mesh/check, the forge requires no status (ADR 0534 §1 changes ADR 0447 §5)	2026-10-23 16:31:15 +02:00
jschoubben	8f7c23da7d	Make a timer that writes state, or a rule in code that overrides a person, a change the review asks (issue 1903)	2026-10-23 16:10:44 +02:00
jschoubben	d49dccb8d5	Use the glossary's word composition check where the merge gate was struck (issue 1303)	2026-10-23 16:10:08 +02:00
jschoubben	6ead37ee7b	Design 47: no status is required on any repository, so hq's Python checks go after the delivery (ADR 0534), and ADR 0529 is named	2026-10-23 16:10:01 +02:00
jschoubben	c8ccbfe35f	Playbooks 07, 08 and the overview name what runs: the checker's try and status, hq's Go tests, the stream backlog, and the way to deliver without the builder (issue 1888)	2026-10-23 15:17:30 +02:00
jschoubben	99fa8f0f09	Glossary: the build seat, the build queue and the build capacity as asks on a language's streams, and the build module (issue 1788)	2026-10-23 15:16:08 +02:00
jschoubben	75056fa931	Design 47 says what R4g and R5 build as one milestone: asks on streams, the assigner's wants, hq's Go tests, the hand path (issue 1130)	2026-10-23 15:15:18 +02:00
jschoubben	47e78d8ff4	Strike the word merge gate: the composition check replaces it in the glossary, the designs and the playbook, and old issues keep it dated (issue 1303)	2026-10-23 15:12:57 +02:00
jschoubben	1385452dc9	Say in the checks' README that the same four checks are Go tests (issue 1296)	2026-10-23 15:11:20 +02:00
jschoubben	5b63a86464	Run words.py as Go tests, with the clock injected and the catalogue comparison skipped when unset (issue 1296)	2026-10-23 15:10:53 +02:00
jschoubben	344c92498d	Run cycle.py as Go tests: a design's layer, status, decisions and code, and the issues folder's numbers and frontmatter (issue 1296)	2026-10-23 15:07:48 +02:00
jschoubben	9339e953b8	Run index.py as Go tests: the reading order's topics are written and no list of records is stored (issue 1296)	2026-10-23 15:07:48 +02:00
jschoubben	0ad95768b6	Run records.py's five checks as Go tests, each proven against a broken tree first (issue 1296)	2026-10-23 15:07:35 +02:00
jschoubben	dd45f31307	Give hq a Go module and the checks' shared reading, so the four checks can become Go tests (issue 1296)	2026-10-23 15:06:25 +02:00
jschoubben	333e73830c	Amend design 42 for the package view, one-at-a-time upgrades and the fallback kernel (ADR 0507, ADR 0508, ADR 0510; issues 1840, 1841)	2026-10-22 17:41:15 +02:00
jschoubben	9a74de0bd6	Name the session that pushed a head in its pull request, so a head that needs a new one names its author (ADR 0505 §5)	2026-10-22 14:25:50 +02:00
jschoubben	2b857df4b5	Never cut a milestone by an order between its parts: the delivery plan keeps that order from the module graph ... The operator, 2026-10-22: a milestone is a milestone; which module reaches the machines first is what the delivery plan is for. The prepare step still lists every part a change reaches, as issues of the same milestone; an order the plan cannot keep is an issue of the build and delivery system.	2026-10-22 01:30:20 +02:00
jschoubben	c07483081d	Cite ADR 0494 in design 47: the checker's milestone is one group, not two deliveries	2026-10-21 22:54:18 +02:00
jschoubben	1955d7f624	Correct design 47 after review of #463: R4e timing of the SDK group, the wait list's Waited-by condition, and what builds images from R4g	2026-10-21 22:52:18 +02:00
jschoubben	38020bee9a	Name the accepted decisions 0480 to 0493 in design 47 and state in its prose what they changed, so the design matches what holds	2026-10-21 22:44:29 +02:00
jschoubben	0162e04f92	Describe a milestone as one delivery group released by one plan, and make a fix found during it ride in the group	2026-10-21 18:08:58 +02:00
jschoubben	37a01b93a5	Use the glossary's word for the milestone's branch	2026-10-21 18:05:07 +02:00
jschoubben	c6fc663019	Make a small fix in mesh-sdk or mesh-controller ride with the milestone's release, so each is delivered once per milestone	2026-10-21 18:04:49 +02:00
jschoubben	5f281dd2a3	Playbook 07: a new verb of a seat the mesh defines waits for the SDK and a controller delivered with it, so the prepare step searches the SDK for each seat a change adds verbs to	2026-10-21 15:22:27 +02:00
jschoubben	373b7e7dd1	Correct design 47's R4c row (installed toolchain, ADR 0477/0478) and move 1305 from R4e to R4f	2026-10-21 13:35:58 +02:00
jschoubben	7c8e1f521d	Add milestone F2b to design 60, and write into playbook 07's prepare step that every strict reader of manifests ships a new word first	2026-10-21 12:53:37 +02:00
jschoubben	be30b63976	Mark design 61 designed now that ADR 0479 is accepted, and follow its last version: PDF and JPEG only, the printer asks its own link	2026-10-21 12:36:24 +02:00
jschoubben	467a2e6c97	Credit restart and the settings read to ADR 0467, and only configure to ADR 0474	2026-10-21 11:18:56 +02:00
jschoubben	115df9fd69	Follow ADR 0479 version 6: the glass only until the feeder is decided, and how the upload bound holds	2026-10-21 11:18:13 +02:00
jschoubben	c7bebf53d4	Answer the review: the page follows ADR 0474, and records who managed the printer	2026-10-21 11:16:48 +02:00
jschoubben	e0118ca67e	Write design 61, the print and scan page, as the home of ADR 0479	2026-10-21 11:15:36 +02:00
jschoubben	64e64ac69d	Answer the review: credit the one-call print to ADR 0468, name F3's dependency and the parts verbs' exception	2026-10-21 11:12:24 +02:00
jschoubben	e111fb875c	Name the accepted ADR 0468 in design 60 and break its building into three milestones, cut by release order	2026-10-21 11:10:31 +02:00
jschoubben	0b21bd0b26	Name ADR 0475 in design 60, now its number is reserved	2026-10-21 01:55:22 +02:00
jschoubben	e212e3841d	Follow the scanning record's settled shape in design 60: a file under the home folder, the certificate as health	2026-10-21 01:54:01 +02:00
jschoubben	8d3a9011ac	Mark design 60 proposed and tie each brother feature to the record that decides it ... The review found features stated as in force that rest on records still proposed (ADR 0468, ADR 0474 and the scanning record to be reserved), and rules without the test that checks them.	2026-10-21 01:47:59 +02:00
jschoubben	b6e01318cf	Design the brother module whole, so printer settings can be changed through the mesh without opening the device ... The operator asked on 2026-10-21 to configure the printer and scanner easily, or through the mesh's tools; the design names the configure verb, its deny list and the proposed decision it rests on (ADR 0474, number to be reserved).	2026-10-21 01:43:14 +02:00
jschoubben	cc605e3b13	Answer design 47's review for release 4's check: the judge's account ends at release 4, the assigner's reads and version skew and field refusal stated, where acceptance tests 22 and 23 are measured, and what release 4 retires	2026-10-19 22:44:18 +02:00
jschoubben	9ffa60924e	Graduate research 058 into design 47's release 4: a check runs only what changed, its tests by the language's build module, its composition by the assigner, in one status ... The check took 3 to 4.5 minutes on every change and paid the whole suite again on every re-ask; the operator's target leaves it about a minute. ADRs 0444 to 0447 decide how; the glossary gains composition check and kept verdict, and merge gate is struck once release 4 is delivered (issue 1303).	2026-10-19 22:03:44 +02:00
jschoubben	3174d5aa6e	Name R3c's issues and the forge module it takes in, and the orders its prepare step found (design 47)	2026-10-19 14:46:33 +02:00
jschoubben	5816ca669f	Say the page's freshness is not yet checked (issue 1222), and fix 08's leftover 'reviewed after its push' (review round 1)	2026-10-19 13:29:22 +02:00
jschoubben	afe83b9124	Keep the drawn overview of the playbooks in hq, for a later docs site	2026-10-19 13:27:55 +02:00
jschoubben	6c607504de	Say a moved trunk is met by the merge check, not promised to step 3 (review round 2)	2026-10-19 13:05:09 +02:00
jschoubben	20c857443c	Bring the branches up to the trunk before the try, and say the try at step 1's end runs the integration tests (review round 1)	2026-10-19 13:04:30 +02:00
jschoubben	7735cfd107	Try before the review, fail first on behaviour, survey every reader of a changed value (playbooks 07 and 08)	2026-10-19 13:03:28 +02:00
jschoubben	19a8e92801	Design 47: R3b's issues, and the two facts its prepare step found for R3c's insight on ADR 0437 (issues 1210-1218)	2026-10-19 11:51:15 +02:00
jschoubben	95bf5cbf20	Design 47: R3a's issues, the two controller fixes it needed first, and R3c's open question on Go-compiling images (issues 1200-1204, 1208, 1209)	2026-10-19 11:09:15 +02:00
jschoubben	643ec2b1bf	Design 47: release 3 is the milestones R3a to R3d by ADR 0437, and answering asks in the view moves to R5	2026-10-19 10:19:55 +02:00
jschoubben	292fae8863	Design 47: R2c is split by its order, the controller's last heard from presence before the node-engine stops sending alive (issue 1183)	2026-10-19 02:12:16 +02:00
jschoubben	d10965a341	Design 47: release 1-2 is the six milestones R1a to R2c, each one release; playbook 04 splits a milestone that holds a release order (the operator, 2026-10-19)	2026-10-19 00:11:02 +02:00
jschoubben	86e66dd51f	Playbook 07: the prepare step looks for the orders a release hides, and fixtures come from the writer's shape (design 47 release 1-2, 2026-10-18)	2026-10-18 21:26:06 +02:00
jschoubben	4a090df25a	Design 47: release 1-2 cut by the orders its prepare step found, with its new decisions and issues (issue 1130)	2026-10-18 20:31:36 +02:00
jschoubben	d81c23b65a	Design 47: the operator confirmed the releases as milestones (2026-10-18); release 1-2's issues and their order	2026-10-18 17:55:21 +02:00
jschoubben	cd9336d05a	Design 47 and glossary: review round 1 (the sections stay the design until their release, rule 4's step above zero, the Approve on the phone until issue 953, release of a milestone under The record)	2026-10-18 17:48:15 +02:00
jschoubben	5c81f1170c	Design 47: the six releases of ADR 0429 as milestones, milestone 6 folded into release 4; glossary: the delivery domain, its parts and their words (ADR 0428, ADR 0429) ... Research 063 graduated into ADR 0429 and this design (playbook 02 step 3). The design names the parts and the releases; its other sections hold until each release is delivered and are rewritten as each is prepared (issue 1130). The words the plans use are marked as going at release 6, not struck: they stay true until that release is delivered.	2026-10-18 17:45:59 +02:00
jschoubben	d0a2950bb0	Playbook 02: wrap the check line and name the step it means (review round 1)	2026-10-18 17:05:46 +02:00
jschoubben	8e76098412	Playbook 02: after three review rounds the lead fixes further findings itself and proposes again; only a finding that changes what was decided goes to the operator (the operator, 2026-10-18)	2026-10-18 17:04:38 +02:00
jschoubben	cec72d1dc9	Playbooks 07 and 08: integration tests run once through mesh-controller.try on the pushed branch before the pull request, never on the machine (the operator, 2026-10-18)	2026-10-18 15:02:56 +02:00
jschoubben	ec373556d0	Playbooks 07 and 08: an acceptance criterion is numbered and cited by its test as <issue>/AC<n>, so its check is a grep (review round 1)	2026-10-18 12:50:30 +02:00
jschoubben	f242b8763b	Design 47 builds with ADR 0426 (no timer where an event can end the wait)	2026-10-18 12:49:18 +02:00
jschoubben	bb6af05f5c	Playbooks 07 and 08: tests are written from acceptance criteria the larger model writes onto the issue (issue 1118); design 47 gets milestone 5b, the planning out of the controller (issue 1117)	2026-10-18 12:42:06 +02:00
jschoubben	19bd7fd960	Retire the word epic, and define milestone as a group of a design's issues delivered together (issue 1105) ... The operator decided on 2026-10-18 that a domain word is used only when clearly defined. epic had three uses and no code; design 47 now names two ways, hotfix and feature.	2026-10-18 04:08:15 +02:00
jschoubben	17c27ddf83	Playbook 07: a new integration test enters through the path the live trigger takes (issue 1086) ... Milestone 4's test saved its plan by hand, skipped the cut from a batch, and passed while the backup step never ran.	2026-10-18 02:19:20 +02:00
jschoubben	b6cf49d8ce	Design 47: milestone 3 fix names issue 1079, of which 1084 was closed as a duplicate, and the forge module it touched	2026-10-18 01:49:37 +02:00
jschoubben	c10efa4d8c	Playbook 07: the new test failed on its first two runs, not three	2026-10-18 00:30:41 +02:00
jschoubben	24fd567c31	Design 47: milestone 4 delivered and split; a fix of milestone 3 comes next. Playbook 07: new integration tests are read against the code before the first push (issues 980, 1082)	2026-10-18 00:29:35 +02:00
jschoubben	64e357da7d	Playbook 07: a change the new merge script must judge ships the script first (issue 895)	2026-10-17 21:32:35 +02:00
jschoubben	9a9a78f882	Playbook 07: report every ten minutes (the operator, 2026-10-17)	2026-10-17 21:28:46 +02:00
jschoubben	e816b61cb7	Playbook 07: the prepare step splits an issue sized over an hour (the operator, 2026-10-17)	2026-10-17 21:25:39 +02:00
jschoubben	610be93803	Playbook 07: a fixing agent never runs an integration test locally (the operator, 2026-10-17)	2026-10-17 21:23:05 +02:00
jschoubben	d5ddd1e715	Playbooks 07 and 08: no ready mark; the review record rides in the pull request and the Approve is asked once the checks pass (issue 1022, ADR 0421)	2026-10-17 20:55:47 +02:00
jschoubben	2001d6e063	Playbook 07: a milestone has steps, runs the whole unit suite, writes its findings into its issues and watches on the smaller model; design 47 names milestone 2b and takes 895 into milestone 3 (issue 1053)	2026-10-17 20:19:16 +02:00
jschoubben	e1987b3654	Playbook 07: the reviewer is kept for the whole release, and a watcher waits for its checks (issue 1042) ... The operator asked why review takes so long: a fresh reviewer per round or per mark reads everything again, and a reviewer waiting on the forge's checks spends its run waiting.	2026-10-17 18:26:06 +02:00
jschoubben	b5d3f23947	Design 57: its milestones name their issues, not their delivery state (issue 1039, folded into 1038)	2026-10-17 18:20:58 +02:00
jschoubben	c753ff068a	Playbook 07: a design names its milestones' issues, never their delivery state (issue 1038) ... The tracker and the delivery records hold whether a milestone is delivered, when and by what; a copy in the design's table is a central status kept by hand (AGENTS.md). Design 47 loses its copied cells.	2026-10-17 18:18:45 +02:00
jschoubben	0b9fda46cc	Design 47: phase II release 1 delivered, 2026-10-17 (playbook 07, write-back)	2026-10-17 18:04:17 +02:00
jschoubben	6b58a6af82	Playbook 07: the glossary's word, the builder (review of #405)	2026-10-17 18:03:52 +02:00
jschoubben	9a39785116	Playbook 07: every wait on the wait list has a watcher agent on the bus (the operator, 2026-10-17)	2026-10-17 18:00:35 +02:00
jschoubben	06440c1522	Playbook 07: the build seat's holder, not a retired word (review of #405's check)	2026-10-17 17:56:21 +02:00
jschoubben	0e7eb9c2da	Playbook 07: read a failed check's whole log; a change to merge-check.sh is judged by main's version	2026-10-17 17:29:43 +02:00
jschoubben	b0cfd08f7c	Design 47: ADR 0420 accepted, ADR 0249 superseded, milestone 3's issues named (review of #404)	2026-10-17 17:20:16 +02:00
jschoubben	0a6613f0d4	Design 47: one plan per group, no order lines, the Approve as the only gate (ADR 0418, 0419, 0421)	2026-10-17 17:18:03 +02:00
jschoubben	85a729c607	Design 47: milestones 1 and 2 delivered, 2026-10-17 (playbook 07, write-back)	2026-10-17 15:06:38 +02:00
jschoubben	fb284fa6ee	Playbook 07: the full report shows the whole design's milestones, the running one's issues under it (the operator, 2026-10-17)	2026-10-17 14:13:28 +02:00
jschoubben	addbd74c39	Playbook 04 and design 47: the milestone is one release, not a feature step (review of #401)	2026-10-17 13:47:37 +02:00
jschoubben	6bf18062c4	Playbooks 07 and 04: a milestone is one release, never cut for size or time; milestones are cut by release order (the operator, 2026-10-17)	2026-10-17 13:47:21 +02:00
jschoubben	edff1f25a1	Playbook 07: one milestone is one branch per repository, its steps reuse the name (the operator, 2026-10-17)	2026-10-17 12:04:37 +02:00
jschoubben	24701df23e	Merge branch 'main' into feat/agents-write-git-ssh	2026-10-16 22:27:02 +00:00
jschoubben	748641dd22	Review of #393: rollouts run one at a time today (issue 525); Approve on Telegram (issue 953 for the terminal); 976's place in the order; milestone 1 takes the rest of 525 and acceptance test 9	2026-10-17 00:06:59 +02:00
jschoubben	75d3ac0f82	Playbooks 04 and 07 after research 055: a milestone's shape from what-if; the Approve on every merge into main; when the two-step exception ends (issue 922)	2026-10-17 00:04:48 +02:00
jschoubben	b6a191d0a6	Design 47's milestones and issues (playbook 04), and the as-is delivery rewritten from research 055's findings ... The operator confirmed six milestones on 2026-10-17; issues 973-981 and 971 carry their repository parts, linked depends-on in order. The as-is described the predecessor's pipeline; it now says what runs today, which design 47 replaces.	2026-10-17 00:04:00 +02:00
jschoubben	aa4bfe289e	Design 47 and the glossary: the reviewer's findings (three work queues, a feature in one repository, what-if, ADR 0406 clause numbers, backups by protection, no suite-time claim, the Go module's judge account)	2026-10-16 23:44:59 +02:00
jschoubben	6f0db74ee4	Design 47: the SDK commits the catalogue accepts (ADR 0402 §4)	2026-10-16 23:42:56 +02:00
jschoubben	e7854a31a6	Design 47: a member naming the SDK member's head is proven by its own merge check (ADR 0402's review)	2026-10-16 23:41:37 +02:00
jschoubben	8bfb11da2c	Design 47 and the glossary: the batch's record in the chain is the rollout (ADR 0408's review)	2026-10-16 23:40:11 +02:00
jschoubben	96f2ae72c1	Rewrite design 47 from research 055's decisions: hotfix, feature and epic from the trunk, delivery on the bus ... ADR 0401-0408 graduate research 055: no release branch, two more ordering rules, the composed check as each member's gate, a backup before the send, installed toolchains, events and work queues on the bus, the merge window as keys, and one chain kept on the bus alone. Design 47 is rewritten from them (one design per thing); the glossary takes hotfix, feature, toolchain, milestone and epic and retires release branch; design 18 loses the toolchain image; playbooks 07 and 08 drop the release-branch wait.	2026-10-16 23:39:12 +02:00
jschoubben	3c49b389d1	Playbook 09: a deletion is approved as an ask on the operator's warrant once design 58 milestone 7 is built; until then the operator runs the approved list	2026-10-16 20:51:00 +02:00
jschoubben	222fbe95f4	Playbook 09 and the hq-cleanup skill: a cleanup reads first, deletes only what the operator approves, and reports what it kept (the operator, 2026-10-16)	2026-10-16 20:01:13 +02:00
jschoubben	101d7f30f7	Playbook 02: one design per thing; a graduation rewrites the design that covers it instead of writing a second (the operator, 2026-10-16)	2026-10-16 19:40:48 +02:00