Playbooks 07 and 08: tests are written from acceptance criteria on the issue (issue 1118); design 47 gets milestone 5b and cites ADR 0426 (issue 1117) #420

2026-10-18T10:51:07Z

mesh-tools commented

2026-10-18 10:51:07 +00:00

The operator, 2026-10-18: acceptance criteria, written by the larger-model agents and linked to the issue, guide the unit, integration and end-to-end tests; the planning moves out of the controller as milestone 5b of design 47, an issue rather than a research effort; zero delay is decided (ADR 0426).

Playbook 07: step 0 item 5 has the lead write each issue's acceptance criteria (given/when/then, the test level that proves it, numbered and cited as <issue>/AC<n>), as an issue-tracker.note until the tracker holds them as a field (issue 1118); step 1 writes the tests from them, each citing its label; step 2 reads every criterion against its test; How it is checked greps the labels.
Playbook 08: the same for a small fix (steps 1, 3, 4, How it is checked).
Design 47: milestone 5b (issue 1117), between 5 and 6; ADR 0426 in its decisions.

Issues: 1117, 1118. Decision: ADR 0426.

Reviewed-by: reviewer-hq@shanks at ec373556d0

The operator, 2026-10-18: acceptance criteria, written by the larger-model agents and linked to the issue, guide the unit, integration and end-to-end tests; the planning moves out of the controller as milestone 5b of design 47, an issue rather than a research effort; zero delay is decided (ADR 0426). - Playbook 07: step 0 item 5 has the lead write each issue's acceptance criteria (given/when/then, the test level that proves it, numbered and cited as `<issue>/AC<n>`), as an `issue-tracker.note` until the tracker holds them as a field (issue 1118); step 1 writes the tests from them, each citing its label; step 2 reads every criterion against its test; How it is checked greps the labels. - Playbook 08: the same for a small fix (steps 1, 3, 4, How it is checked). - Design 47: milestone 5b (issue 1117), between 5 and 6; ADR 0426 in its decisions. Issues: 1117, 1118. Decision: ADR 0426. Reviewed-by: reviewer-hq@shanks at ec373556d0bb8197f3ec025a9d5ce67bac5271b4

mesh-tools added 3 commits 2026-10-18 10:51:07 +00:00

Playbooks 07 and 08: tests are written from acceptance criteria the larger model writes onto the issue (issue 1118); design 47 gets milestone 5b, the planning out of the controller (issue 1117) bb6af05f5c

Design 47 builds with ADR 0426 (no timer where an event can end the wait) f242b8763b

Playbooks 07 and 08: an acceptance criterion is numbered and cited by its test as <issue>/AC<n>, so its check is a grep (review round 1)

mesh/merge-gate head ec373556d0bb merged into trunk 672011ab92ad — pass: the change touches no module of the mesh's graph

Details

mesh/repo-check head ec373556d0bb merged into trunk 672011ab92ad — pass: its merge-check.sh passed

Details

mesh/delivery delivered

Details

ec373556d0

mesh-tools commented

2026-10-18 10:51:08 +00:00

Delivery novox/hq@ec373556d0bb — delivered since 2026-10-18T10:52:54Z

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

Transitions

2026-10-18 10:51 (new) → proposed (announced): novox/hq#420's head announced
2026-10-18 10:51 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-18 10:51 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-18 10:52 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-18 10:52 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@ec373556d0bb` — **delivered** since 2026-10-18T10:52:54Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-18 10:51 (new) → proposed (announced): novox/hq#420's head announced - 2026-10-18 10:51 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-18 10:51 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-18 10:52 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-18 10:52 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 b98b93efc8 into main

2026-10-18 10:52:53 +00:00

mesh-tools deleted branch docs/acceptance-criteria-milestone-5b

2026-10-18 10:52:53 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#420