Build features from the design alone and ask the operator what it leaves open #537

2026-11-10T16:22:12Z

mesh-tools commented

2026-11-10 16:22:12 +00:00

The operator, 2026-11-10: "we do so much research and design, and then during implementation, you always completely ignore it"; "yes, fix our HQ, maybe also look at other parts of our implementation that could be causing errors". Milestone 47/G's prepare and develop made about 40 rulings between the leads, several against the decisions and designs, and found 46 questions the design does not answer only during develop.

Playbook 07: the milestone part of the design is the only input to prepare, develop and code review. The prepare puts out a build map per repository and the design questions, nothing else (no findings, no rulings). New step Design complete: the operator answers each question, the answer goes into the design, then develop starts. Commits carry Builds: design NN M §n; the code review judges each change against its design line. One lead per milestone; a contract's users start from its commit; one writer per file; one sibling placement; a subtask starts only with room for the whole of it.
Playbook 02: the shape of a design (a main file of at most 80 KB, one milestone part of at most 60 KB per milestone, numbered lines that leave the builder no choice); answering a design question (only the operator; written into the design, or a record first where it changes one).
Playbooks 04, 08, the overview and playbooks.html to match; AGENTS.md; the glossary (milestone part, design line, build map, design question).
Agent definitions: mesh-preparer rewritten; mesh-developer, mesh-code-reviewer, the four domain reviewers and hq-design-writer changed; skills hq-handoff and hq-amend-design.

Needs a tool: one placement of sibling repositories as the checker lays them (none exists). Needs the operator: three instruction sections now contradict the playbooks (discover-knowledge-eagerly, act-on-the-intent, how-work-is-done), to be changed through the instruction proposals.

Not reviewed by an agent yet; hq's checks pass (go test ./...), playbooks.html rendered and checked.

Issue 1966.

https://claude.ai/code/session_01JG73KK8HD1gufnqyFxMFdW

The operator, 2026-11-10: "we do so much research and design, and then during implementation, you always completely ignore it"; "yes, fix our HQ, maybe also look at other parts of our implementation that could be causing errors". Milestone 47/G's prepare and develop made about 40 rulings between the leads, several against the decisions and designs, and found 46 questions the design does not answer only during develop. - **Playbook 07:** the milestone part of the design is the only input to prepare, develop and code review. The prepare puts out a build map per repository and the design questions, nothing else (no findings, no rulings). New step *Design complete*: the operator answers each question, the answer goes into the design, then develop starts. Commits carry `Builds: design NN M §n`; the code review judges each change against its design line. One lead per milestone; a contract's users start from its commit; one writer per file; one sibling placement; a subtask starts only with room for the whole of it. - **Playbook 02:** the shape of a design (a main file of at most 80 KB, one milestone part of at most 60 KB per milestone, numbered lines that leave the builder no choice); answering a design question (only the operator; written into the design, or a record first where it changes one). - **Playbooks 04, 08, the overview and playbooks.html** to match; **AGENTS.md**; the glossary (milestone part, design line, build map, design question). - **Agent definitions:** mesh-preparer rewritten; mesh-developer, mesh-code-reviewer, the four domain reviewers and hq-design-writer changed; skills hq-handoff and hq-amend-design. Needs a tool: one placement of sibling repositories as the checker lays them (none exists). Needs the operator: three instruction sections now contradict the playbooks (discover-knowledge-eagerly, act-on-the-intent, how-work-is-done), to be changed through the instruction proposals. Not reviewed by an agent yet; hq's checks pass (`go test ./...`), playbooks.html rendered and checked. Issue 1966. https://claude.ai/code/session_01JG73KK8HD1gufnqyFxMFdW

mesh-tools added 1 commit 2026-11-10 16:22:12 +00:00

Build features from the design alone and ask the operator what it leaves open

mesh/delivery closed: a newer head of the same pull request

Details

mesh/check checking 8f9a6d4f7bc9 on b229f5c4df1e

8f9a6d4f7b

Milestone 47/G was prepared and developed from a 430 KB design by agents told to
start from the knowledge base and judge what was not mesh-shaped. The prepare wrote
its own findings and about 40 rulings by two leads, seven of which went against the
records or the design, and 29 questions the design never answered surfaced only in
develop.

The playbooks now make the milestone's part of its design the only input to the
prepare, develop and the code review: the prepare outputs a build map per
repository and the design questions; the operator answers each and the answer is
written into the design before develop starts; every commit cites the design lines
it builds and the review judges it against them. A design is a main file and one
part per milestone, within a size an agent reads whole. Also: one lead per
milestone, a contract's users start from its commit, one writer per file, one
sibling placement, and agents stop between subtasks, never inside one.

Claude-Session: https://claude.ai/code/session_01JG73KK8HD1gufnqyFxMFdW

mesh-tools commented

2026-11-10 16:22:16 +00:00

Delivery novox/hq@cdfed7593e73 — merged since 2026-11-10T16:51:27Z

Source — source.main moved to novox/hq@e65d0f8f2b. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.

Transitions

2026-11-10 16:24 (new) → proposed (announced): novox/hq#537's head announced
2026-11-10 16:24 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
2026-11-10 16:51 ready → merged (merged): on the trunk its modules follow: merged there

The commit's note under refs/notes/mesh-plan keeps every transition of this change up to its merge: git log --notes=mesh-plan.

**Delivery** `novox/hq@cdfed7593e73` — **merged** since 2026-11-10T16:51:27Z **Source** — source.main moved to novox/hq@e65d0f8f2bbd. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Transitions** - 2026-11-10 16:24 (new) → proposed (announced): novox/hq#537's head announced - 2026-11-10 16:24 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false) - 2026-11-10 16:51 ready → merged (merged): on the trunk its modules follow: merged there The commit's note under `refs/notes/mesh-plan` keeps every transition of this change up to its merge: `git log --notes=mesh-plan`.

jschoubben added 2 commits 2026-11-10 16:24:31 +00:00

Compare seat contracts with the design in the prepare, and call a verdictless merge unchecked 6e90fa443e

On 2026-11-10 a seat contract and an event's subject that differed from design 47
surfaced only in develop, and the checker twice dropped a check still running when
its pull request merged. The prepare now compares every seat contract the milestone
touches with its design lines, each difference a design question before develop;
and a merged change with no verdict is reported as unchecked, never as passed.

Claude-Session: https://claude.ai/code/session_01JG73KK8HD1gufnqyFxMFdW

Keep the check step's no-second-review sentence whole

mesh/delivery merged: source.main moved to novox/hq@e65d0f8f2bbd

Details

mesh/check being carried to cdfed7593e73 on e65d0f8f2bbd | from b229f5c4df1e

cdfed7593e

Claude-Session: https://claude.ai/code/session_01JG73KK8HD1gufnqyFxMFdW

mesh-tools commented

2026-11-10 16:24:36 +00:00

mesh-delivery: the operator's Approve of this pull request's merge into main is ended: its head 8f9a6d4f7b is no longer the pull request's head, or the pull request closed. Nothing is merged on it. The operator is asked again once the checks pass at the new head.

mesh-delivery: the operator's Approve of this pull request's merge into main is ended: its head 8f9a6d4f7bc9 is no longer the pull request's head, or the pull request closed. Nothing is merged on it. The operator is asked again once the checks pass at the new head.

mesh-tools merged commit e65d0f8f2b into main

2026-11-10 16:51:25 +00:00

mesh-tools deleted branch process/implement-the-design

2026-11-10 16:51:26 +00:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#537