Design 59: milestones 2 to 4 confirmed with their issues, and the mail modules' as-is design #443

2026-10-20T17:12:28Z

mesh-tools commented

2026-10-20 17:12:28 +00:00

Playbook 04 for design 59, after research 066's graduation (hq #442).

Design 59 §11: milestones 2 to 4 confirmed by the operator on 2026-10-20, with their issues in order (step 6): milestone 2 is 1227, 1426, 1427, 1428, 1429, 1430, 1431, 1418; milestone 3 is 806; milestone 4 is 1433, 1419, 1432. Also the graduation review's small points: §6 names ADR 0378 §5 and the page's writes with correct and undo; §8 names issue 1419.
New as-is 03-DESIGN/00-as-is/18-the-mail-modules.md (step 3): what milestone 2 replaces, as built on mesh-catalog main a67f0196 and read live: the one grants list that gives reading and asking to send at once, the send path, mesh-mail-web, and mesh-mail-notifier's pop-up for every new mail. It states where the build differs from the decisions (the two modules are separate from mesh-mail's source; mesh-mail still runs on the control-node, issue 803; the notifier's health, issue 841).

hq checks words.py, records.py, index.py, cycle.py pass.

Reviewed-by: reviewer-066@g14 at d2dccddc27

Playbook 04 for design 59, after research 066's graduation (hq #442). - **Design 59 §11**: milestones 2 to 4 confirmed by the operator on 2026-10-20, with their issues in order (step 6): milestone 2 is 1227, 1426, 1427, 1428, 1429, 1430, 1431, 1418; milestone 3 is 806; milestone 4 is 1433, 1419, 1432. Also the graduation review's small points: §6 names ADR 0378 §5 and the page's writes with correct and undo; §8 names issue 1419. - **New as-is 03-DESIGN/00-as-is/18-the-mail-modules.md** (step 3): what milestone 2 replaces, as built on mesh-catalog main a67f0196 and read live: the one `grants` list that gives reading and asking to send at once, the send path, mesh-mail-web, and mesh-mail-notifier's pop-up for every new mail. It states where the build differs from the decisions (the two modules are separate from mesh-mail's source; mesh-mail still runs on the control-node, issue 803; the notifier's health, issue 841). hq checks words.py, records.py, index.py, cycle.py pass. Reviewed-by: reviewer-066@g14 at d2dccddc27268452bd7a5312b32388df23c3f37c

mesh-tools added 4 commits 2026-10-20 17:12:29 +00:00

Write milestones 2 to 4's issues into design 59, as the operator confirmed them 66bb013b85

Playbook 04 step 6. Also names ADR 0378 §5 beside ADR 0440 §4 for the page's use of mail-reading, its writes with correct and undo, and issue 1419 in §8's last sentence, as the graduation's review noted.

Write the mail modules' as-is design, so what design 59's milestone 2 replaces is recorded before it is built e925a843ce

Playbook 04 step 3: the one grants list that gives reading and sending at once, and mesh-mail-notifier's pop-up for every new mail, read from mesh-catalog main a67f0196 and the live mesh.

Answer the review: the mail modules are separate modules, the notifier has no process, nothing future in the as-is; 1433 depends on none dcc6f185d4

Say the notifier's bundle is its own process under its own account, as main.go says

mesh/merge-gate head d2dccddc2726 merged into trunk 0738fa1405dd — pass: the change touches no module of the mesh's graph

Details

mesh/repo-check head d2dccddc2726 merged into trunk 0738fa1405dd — pass: its merge-check.sh passed

Details

mesh/delivery delivered

Details

d2dccddc27

mesh-tools commented

2026-10-20 17:12:38 +00:00

Delivery novox/hq@d2dccddc2726 — delivered since 2026-10-20T17:45:10Z

Delivery plan — builds nothing: the change touches no module of the mesh's graph

Transitions

2026-10-20 17:12 (new) → proposed (announced): novox/hq#443's head announced
2026-10-20 17:13 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-20 17:13 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-20 17:45 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-20 17:45 published → delivered (done): nothing for a walk to move

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

**Delivery** `novox/hq@d2dccddc2726` — **delivered** since 2026-10-20T17:45:10Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-20 17:12 (new) → proposed (announced): novox/hq#443's head announced - 2026-10-20 17:13 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-20 17:13 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-20 17:45 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-20 17:45 published → delivered (done): nothing for a walk to move The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

mesh-tools merged commit a5c6c98ecc into main

2026-10-20 17:45:08 +00:00

mesh-tools deleted branch design-59-milestone-issues

2026-10-20 17:45:09 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#443