Design 47, milestone H: the plan to deliver the build-and-delivery system properly #737

Merged
mesh-tools merged 5 commits from plan/47-deliver-properly into main 2026-11-20 00:21:01 +00:00
Member

The plan the operator asked for on 2026-11-19 ("write out a plan to deliver our mesh build-and-delivery system, thoroughly"), as design 47's milestone H file, written by the lead from six specifications (one per part of the design, no code read) and six gap tables (main's code held against each specification) plus one live-state reading, all by agents on the opus model during the night of 2026-11-19 to 20.

What it decides: one model and no leftovers (a change is a commit on a watched branch; the forge bridge says it, the indexer takes it in per branch, the runner starts exactly the movers, the gate follows); fix in place for every module, with the indexer's take-in and the assigner's want rule written again; the design brought in line before code (milestone H0, with four questions for the operator); one clean state placed by hand once (milestone H1's delivery); milestones H2 to H5 in dependency order, each delivered by its own pipeline; and the guards so it does not rot again.

Also: two agent definitions, spec-reader and gap-surveyor, that carried the readings (agents-have-a-home), named in AGENTS.md.

Not a change of any design line: the plan names the lines and records that milestone H0 writes. The six held pull requests of 2026-11-19 stay unmerged until H1's step 2.

https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy

The plan the operator asked for on 2026-11-19 ("write out a plan to deliver our mesh build-and-delivery system, thoroughly"), as design 47's milestone H file, written by the lead from six specifications (one per part of the design, no code read) and six gap tables (main's code held against each specification) plus one live-state reading, all by agents on the opus model during the night of 2026-11-19 to 20. What it decides: one model and no leftovers (a change is a commit on a watched branch; the forge bridge says it, the indexer takes it in per branch, the runner starts exactly the movers, the gate follows); fix in place for every module, with the indexer's take-in and the assigner's want rule written again; the design brought in line before code (milestone H0, with four questions for the operator); one clean state placed by hand once (milestone H1's delivery); milestones H2 to H5 in dependency order, each delivered by its own pipeline; and the guards so it does not rot again. Also: two agent definitions, `spec-reader` and `gap-surveyor`, that carried the readings (agents-have-a-home), named in AGENTS.md. Not a change of any design line: the plan names the lines and records that milestone H0 writes. The six held pull requests of 2026-11-19 stay unmerged until H1's step 2. https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
mesh-tools added 2 commits 2026-11-19 23:36:30 +00:00
The system cannot deliver itself: wants held, records never ended, two
models side by side. The plan decides one model, fix in place with the
indexer's take-in written again, one clean state by hand, milestones
H0 to H5 and the guards. Two agent definitions (spec-reader,
gap-surveyor) carried the readings it is written from.

Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
jschoubben added 1 commit 2026-11-19 23:57:08 +00:00
jschoubben added 1 commit 2026-11-20 00:12:24 +00:00
jschoubben added 1 commit 2026-11-20 00:20:15 +00:00
mesh-tools merged commit e6a73d8f59 into main 2026-11-20 00:21:01 +00:00
mesh-tools deleted branch plan/47-deliver-properly 2026-11-20 00:21:01 +00:00
Sign in to join this conversation.
No Reviewers
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/hq#737