300 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	1dab64134a	Playbooks 07 and 08: the one check is one status, mesh/check; drop the leftover try wording (review fixes)	2026-10-26 20:52:36 +01:00
jschoubben	a0e4c1fe17	Playbooks 07 and 08: one release, one check, no try, push once after the review (ADR 0548) ... Build capacity is the mesh's scarcest resource: a try before and after the review plus a check per fix round on an open pull request spent it several times per release.	2026-10-26 20:50:37 +01:00
jschoubben	b7dabd8ceb	Design 47 gives its running milestones rows; the glossary and playbook 07 name progress (issue 1947) ... The three milestones of the controller leaving build and delivery were prose only, so no reader of the table saw the running work; 1209 and 971 were listed in two milestones against ADR 0493 §2.	2026-10-26 16:40:12 +01:00
jschoubben	11b0a450c3	Designs 47, 24 and 39 follow ADR 0548 to 0551: one check per set of heads with carried verdicts and merge turns, placement in the catalogue, every secret in the vault ... Design 47 names ADR 0548 (a check runs to its end, a trunk move carries a verdict by its package digests, the hold and the merge turn), ADR 0551 (the hold and turns only while the check gates merges), ADR 0549 (placement files read by the indexer) and ADR 0550 (the vault signs and adopts the loaded hashes), and ADR 0547's answers on placement and signing. Design 24 gains every secret in the vault; design 39 moves grants and tokens into it. The glossary gains carried verdict, merge turn and placement file.	2026-10-26 13:29:30 +01:00
jschoubben	be1bbe0a65	Playbooks 07 and 08: read the forge head before trusting a reported push, so a try never runs on a push that did not happen	2026-10-26 11:02:44 +01:00
jschoubben	0354947ba6	Playbooks 07 and 08: the dependent-pull-request rule leaves delivery group members out; the instance-search rule is a numbered item	2026-10-25 13:29:17 +01:00
jschoubben	4d596bd211	Playbooks 07 and 08: open a dependent pull request only after delivery, fold a follow-up into the unapproved one, search every instance of a fault kind	2026-10-25 13:27:54 +01:00
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	d08cac4e86	Answer the review of hq's finish: role names in the as-is delivery, ADR 0524-0529 named, stale check names fixed (issue 1296)	2026-10-24 04:40:02 +02:00
jschoubben	ca460b681b	hq's checks read the whole repository: mark the package reads-outside so its tests always run (issue 1935)	2026-10-24 03:46:56 +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	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	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
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