149 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	ba09497092	Name the hand-path command mesh-hand-compose, as mesh-sdk feat/r6 now calls it: main's mesh-compose is the composer (ADR 0482, issue 1943)	2026-10-24 23:06:00 +02:00
jschoubben	2d3a205740	Merge remote-tracking branch 'origin/main' into feat/r6	2026-10-24 23:00:09 +02:00
jschoubben	49dd8fc7e3	Merge pull request 'R4g finish: hq's checks as Go tests, the old word struck, the marker (issues 1296, 1935)' (#473) from feat/r4g-finish into main ... Reviewed-on: #473	2026-10-24 20:56:42 +00:00
jschoubben	4b514e4d69	Design 47, the glossary and playbooks 04, 07 and 08 for release 6: wants and signed compositions, no plans (ADR 0539, issue 1130) ... Release 6 deletes delivery plans, batches, the merge window and tiers, so design 47's sections that described them as current are rewritten to the assigner's seven rules, the controller's signed compositions per node, the node agent, credentials on a done build, the switch as release 5's last plan, the hand path by mesh-compose and a want, and the view's delivered, moving, settled and stuck events. The glossary gains composition and restates want, declaration, send and apply; the playbooks follow a delivery by the view and the have keys and call no plans, plan, push or what-if.	2026-10-24 21:01:24 +02:00
jschoubben	8433e42c03	Playbook 07: the glossary's words, the source revision and the gate (review)	2026-10-24 13:54:31 +02:00
jschoubben	129af9906d	Playbook 07: read a verdict's trunk against main at once, because a lagging trunk makes the Approve merge nothing (issue 1726)	2026-10-24 13:50:37 +02:00
jschoubben	2249d30151	Merge main into feat/r4g-finish (#472)	2026-10-24 13:26:24 +02:00
jschoubben	8498006d23	Playbooks 07 and 08: answer the review (no lab, plain words, checks on the forge, issue 1941)	2026-10-24 12:50:35 +02:00
jschoubben	d20ed892cf	Playbooks 07 and 08: three questions in the milestone file, and a try before a merge by hand (research 071, issue 1921)	2026-10-24 12:45:57 +02:00
jschoubben	6dc008b5e7	Delete merge-check.sh and the four Python checks; the Go tests replace them (issue 1296, H6)	2026-10-24 03:39:11 +02:00
jschoubben	8055006ba1	Playbook 07: the two 'never run integration tests on the machine' lines say 'while developing', so the guideline after a failed try no longer contradicts them (review-471)	2026-10-23 23:24:15 +02:00
jschoubben	2b53b6a5d2	Playbooks 07 and 08: say the local run after a failed try as a guideline, not a rule (the operator)	2026-10-23 23:22:21 +02:00
jschoubben	87c338da8e	Playbooks 07 and 08: a failed try or check is run locally at once, so every failure shows in one run, not one per try (the operator, 2026-10-23)	2026-10-23 23:20:27 +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	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	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
mesh-tools	93963aeb51	Merge pull request 'Playbooks: how a module's old directory is closed, and a refused try (issues 1843, 1854)' (#468) from pb/moving-a-module-directory into main	2026-10-22 18:19:19 +00:00
jochen	eddd7ba684	Answer the review: mockup data invented throughout, later milestones' scope marked proposed, design 59 says where it is replaced, playbook 10 aligned with 04 and 07	2026-10-22 19:19:52 +02:00
jochen	5d745d04db	Write design 63 and playbook 10, so the mail page's next steps are built from a picked design ... Design 63 turns the mail page into the operator's list with Owly beside it (ADR 0515 to 0519), in six milestones with their issues; its reference mockup is kept beside it, its data invented. Playbook 10 says how a page is designed before it is built: mockups with fixed data, the operator picks, the pick is the reference. The as-is of the mail modules now describes mail reading as delivered, the glossary gains design 63's words, design 59's milestone 4 is marked replaced, and AGENTS.md allows a design's mockup. Issues 1855 and 1856.	2026-10-22 18:42:42 +02:00
jochen	7fcca88c01	Playbooks: how a module's old directory is closed, and a refused try (issues 1843, 1854) ... Lessons from closing only-office's old directories: a directory keeps its id until emptied on the operator's word, then leaves the manifest in a second fix; and a fifth try is refused, not queued.	2026-10-22 18:25:05 +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
mesh-tools	a214776696	Merge pull request 'Playbook 07: a new verb of a seat the mesh defines waits for the SDK and a controller delivered with it' (#460) from playbook/seat-contract-order into main	2026-10-21 16:14:23 +00: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
jochen	aa56e9b9e7	Playbook 07: the fixed scope and fixing what you open agree, a blocking issue still goes in	2026-10-21 14:42:27 +02:00
jochen	4f8c469329	Playbooks 07 and 08: the session that opens an issue along the way fixes it ... The operator, 2026-10-21: issues opened along the way were only listed and left. Small ones are fixed in between as small fixes, the rest right after the delivery, outside the running milestone's branch, so its fixed scope holds.	2026-10-21 14:40:56 +02:00
jochen	ad0a95dc0c	Playbook 07: the plural 'issues <n>' is read too; 1654 was another milestone's issue	2026-10-21 14:06:36 +02:00
jochen	c770bc1c50	Playbook 07: name a pull request's own issues as 'issue <n>', and no other ... mesh-delivery reads a pull request's issues from the words 'issue <n>' in its description; okioki #9 listed its own bare and named two follow-ups that way, and the Approve's ask named the follow-ups.	2026-10-21 14:05:28 +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
jochen	9f0b0215ae	Playbook 08: check a module compiles with go vet, never go build in its folder (issue 1577) ... go build in a module's folder writes the program beside go.mod, and two such programs were committed on 2026-10-21, caught only by the review.	2026-10-21 09:58:44 +02:00
mesh-tools	ba9f063c77	Read a hand push's plan first, and assign a new module to one machine first, from the night's build-module faults	2026-10-20 23:34:42 +00:00
mesh-tools	2713e131b4	Name ADR 0465, 0466 and 0469 in design 47, and write the day's lessons on watchers, pushes and what a merge moves into playbook 07	2026-10-20 19:44:57 +00:00
mesh-tools	5705da30c0	Judge a catalogue removal by the controller's unit tests against the catalogue's branch, not by a try ... A controller try reads the catalogue's main, so it would have passed for mesh-catalog #381 (review round 1).	2026-10-20 17:59:47 +00:00
mesh-tools	1d7cfed47a	Name ADR 0457 and ADR 0463 in design 47, and write the day's delivery lessons into playbook 07 ... Design 47's catch-up of merges nobody heard is decided by ADR 0457 and bounded by ADR 0463, so other sessions read them from its frontmatter. Playbook 07 gains four lessons from 2026-10-20: a Retry is never asked beside an Approve (issue 1408), an ask is named only after it is read on the router, a check's wait is read from its delivery and not the build queue, and a catalogue change removing a module is tried against the controller (issue 1406).	2026-10-20 17:57:57 +00:00
jochen	7ed83f4965	Keep three lessons of feature mail-sender in playbook 07: a rule keyed on a shared property, a manifest word's first push, one watcher per wait	2026-10-19 15:28: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	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	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	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