What: playbook 07 (feature branches) gains how a feature's issues are given to agents.
The lead decides, a fixing agent builds. Before an agent gets an issue, the lead settles every open question; the issue then names the repository and files, the quoted decisions, the first test, a one-sentence done-when and what not to touch. An agent that finds the code differs stops and reports.
Spend the operator's allowance on judgement. Fixing agents run on the smaller model (Sonnet); the lead, the independent reviews and the decision records on the larger one.
At most two issues at once (was five).
Lessons from feature 57: never land on a red check; a new manifest word lands with the controller that reads it; review the tree that is pushed, and confirm a gitea_commit commit's tree before posting a verdict.
Reports: every ten minutes, and at once when something lands or needs the operator.
Why: on the night of 14-15 October, feature 57 ran five agents at once; eight issues stopped on undecided design questions and restarted, spending 4% of the weekly allowance per 30 minutes. The operator paused the work and asked for clearer, more focused issues and the smaller model for builders.
Reviewed locally by an independent agent: APPROVE at 1d3fd56 (two findings fixed: the report rhythm matches the approved instructions; gitea_commit is glossed). This forge commit 912fd428 has the same tree as 1d3fd56 (2e8f1e71), on main a75faad. The verdict follows as a comment.
What: playbook 07 (feature branches) gains how a feature's issues are given to agents.
- **The lead decides, a fixing agent builds.** Before an agent gets an issue, the lead settles every open question; the issue then names the repository and files, the quoted decisions, the first test, a one-sentence done-when and what not to touch. An agent that finds the code differs stops and reports.
- **Spend the operator's allowance on judgement.** Fixing agents run on the smaller model (Sonnet); the lead, the independent reviews and the decision records on the larger one.
- **At most two issues at once** (was five).
- Lessons from feature 57: never land on a red check; a new manifest word lands with the controller that reads it; review the tree that is pushed, and confirm a `gitea_commit` commit's tree before posting a verdict.
- Reports: every ten minutes, and at once when something lands or needs the operator.
Why: on the night of 14-15 October, feature 57 ran five agents at once; eight issues stopped on undecided design questions and restarted, spending 4% of the weekly allowance per 30 minutes. The operator paused the work and asked for clearer, more focused issues and the smaller model for builders.
Reviewed locally by an independent agent: APPROVE at 1d3fd56 (two findings fixed: the report rhythm matches the approved instructions; `gitea_commit` is glossed). This forge commit 912fd428 has the same tree as 1d3fd56 (2e8f1e71), on main a75faad. The verdict follows as a comment.
Five agents at once, each stopping on an undecided design question and restarting, spent a
week's allowance in a night. Also write down the lessons of feature 57: never land on a red
check, a new manifest word lands with the controller that reads it, and review the tree that
is pushed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Deliverynovox/hq@912fd428fb89 — delivered since 2026-10-14T23:26:04Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-14 23:24 (new) → proposed (announced): novox/hq#358's head announced
2026-10-14 23:25 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-14 23:25 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-14 23:26 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-14 23:26 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-delivery:view -->
**Delivery** `novox/hq@912fd428fb89` — **delivered** since 2026-10-14T23:26:04Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-14 23:24 (new) → proposed (announced): novox/hq#358's head announced
- 2026-10-14 23:25 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-14 23:25 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-14 23:26 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-14 23:26 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`.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What: playbook 07 (feature branches) gains how a feature's issues are given to agents.
gitea_commitcommit's tree before posting a verdict.Why: on the night of 14-15 October, feature 57 ran five agents at once; eight issues stopped on undecided design questions and restarted, spending 4% of the weekly allowance per 30 minutes. The operator paused the work and asked for clearer, more focused issues and the smaller model for builders.
Reviewed locally by an independent agent: APPROVE at 1d3fd56 (two findings fixed: the report rhythm matches the approved instructions;
gitea_commitis glossed). This forge commit912fd428has the same tree as 1d3fd56 (2e8f1e71), on maina75faad. The verdict follows as a comment.Delivery
novox/hq@912fd428fb89— delivered since 2026-10-14T23:26:04ZDelivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.