Commit Graph
8 Commits
Author SHA1 Message Date
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
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
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)
mesh/repo-check head 9a74de0bd64f merged into trunk 77d4a8a39e1f beside mesh-catalog#444@09e749bc +1 more — pass: its merge-check.sh passed
mesh/merge-gate head 9a74de0bd64f merged into trunk 77d4a8a39e1f — pass: group feat/quiet-deliveries composed: every machine composes with the change as it…
mesh/delivery delivered
mesh/delivery-group group feat/quiet-deliveries delivered: every member is delivered
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
mesh/merge-gate head 2b857df4b51e merged into trunk 73a06324dc0d — pass: the change touches no module of the mesh's graph
mesh/repo-check head 2b857df4b51e merged into trunk 73a06324dc0d — pass: its merge-check.sh passed
mesh/delivery delivered
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 0162e04f92 Describe a milestone as one delivery group released by one plan, and make a fix found during it ride in the group
mesh/merge-gate head 0162e04f9275 merged into trunk d5d821220494 — pass: the change touches no module of the mesh's graph
mesh/repo-check head 0162e04f9275 merged into trunk d5d821220494 — pass: its merge-check.sh passed
mesh/delivery delivered
2026-10-21 18:08:58 +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 5816ca669f Say the page's freshness is not yet checked (issue 1222), and fix 08's leftover 'reviewed after its push' (review round 1)
mesh/merge-gate head 5816ca669f20 merged into trunk f269e83f5d1a — pass: the change touches no module of the mesh's graph
mesh/repo-check head 5816ca669f20 merged into trunk f269e83f5d1a — pass: its merge-check.sh passed
mesh/delivery delivered
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