The operator asked (2026-10-14) for the feature rules to live in playbook 07, which already said one branch name, one worktree per repository and one MR per repository at the end. Feature 57 had been worked the other way, a pull request per issue into protected branches, and lost most of a day to merge checks.
Added:
the second failure, as seen;
the feature branch is never protected and takes no pull request mid-feature;
the issue is the unit of work, its commits name it; no PR, check, review or delivery per issue;
one independent review per repository, checks once, one delivery plan at the end;
a section on several agents: lead holds the feature worktrees, agents land by fast-forward under a lock, at most five issues at once, an issue partly done goes back to open, two issues in one file, fetch by name, a progress report every ten minutes with active times, lessons added here;
a check that issues' commits are on the feature branch and no PR into it exists.
The mesh-wide instruction proposed today becomes a pointer to this playbook once it merges.
MESH_CATALOG_DIR=../mesh-catalog sh merge-check.sh passes. No node names (hq is public).
The operator asked (2026-10-14) for the feature rules to live in playbook 07, which already said one branch name, one worktree per repository and one MR per repository at the end. Feature 57 had been worked the other way, a pull request per issue into protected branches, and lost most of a day to merge checks.
Added:
- the second failure, as seen;
- the feature branch is never protected and takes no pull request mid-feature;
- the issue is the unit of work, its commits name it; no PR, check, review or delivery per issue;
- one independent review per repository, checks once, one delivery plan at the end;
- a section on several agents: lead holds the feature worktrees, agents land by fast-forward under a lock, at most five issues at once, an issue partly done goes back to open, two issues in one file, fetch by name, a progress report every ten minutes with active times, lessons added here;
- a check that issues' commits are on the feature branch and no PR into it exists.
The mesh-wide instruction proposed today becomes a pointer to this playbook once it merges.
`MESH_CATALOG_DIR=../mesh-catalog sh merge-check.sh` passes. No node names (hq is public).
Feature 57 was first worked as a pull request per issue into protected
branches and lost most of a day waiting on merge checks. Record the issue
as the unit, a review and checks once at the end, landing by fast-forward
under a lock, and the lessons met on the way.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Deliverynovox/hq@071fc1c29dce — delivered since 2026-10-14T19:56:05Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-14 19:53 (new) → proposed (announced): novox/hq#354's head announced
2026-10-14 19:54 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-14 19:54 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-14 19:56 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 19:56 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@071fc1c29dce` — **delivered** since 2026-10-14T19:56:05Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-14 19:53 (new) → proposed (announced): novox/hq#354's head announced
- 2026-10-14 19:54 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-14 19:54 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-14 19:56 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 19:56 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`.
A finished issue left in fixing until the feature's delivery breaks playbook 03 and the glossary. The new bullet says "An issue is never left in fixing while nobody works on it" and, one sentence later, "A finished issue stays in fixing until the feature's delivery". The finished issue's agent is gone, so after a day its worker is stale (03 step 2, glossary), and with no pull request of it open it is abandoned (glossary, ADR 0294): anyone may take it over without a reason. Say who holds it: for example, the lead moves each landed issue to fixing with by set to the lead (take-over, reason "landed on the feature branch") and notes the landing commit; fixed-by then names the feature's pull request once it opens (03 Rules: a commit or a pull request, never a branch). The bullet then also agrees with the approved instruction that keeps an issue in fixing only while its branch is actively worked.
The lead is never defined. "The lead holds the feature branch" is the first mention, and the glossary has no such word. Say in one sentence who the lead is (the session that names the feature, sends the agents and opens the pull requests in step 4), and say that the lead does the push in step 4, since "the agents never push".
A delivery group needs at least two repositories. The glossary and ADR 0239 §2 define a delivery group as two or more deliveries sharing a head branch name. A feature in one repository is one delivery, not a group. Write "when the feature touches more than one repository, its pull requests share the branch name and form one delivery group (ADR 0239)". "Delivered as one delivery plan" is also loose: each delivery has its own delivery plan, and the group delivers them as one unit.
"The design's table of what waits for what" assumes a design that has such a table. A reader coming to this cold should be pointed at the tracker's depends-on links (as the next bullet already uses them), with the design's table as the source when one exists.
Markdown (minor). The continuation lines added under steps 1, 3 and 4 follow the item's text with no blank line, so they render as part of the same paragraph ("…within the feature. The feature branch is never protected…"). Put a blank line before each, kept at 3-space indentation, so each renders as its own paragraph inside the item. It renders correctly as it is, just without the paragraph break.
Checked and fine: there are no node names in the added lines. Glossary words are used correctly (merge check, delivery plan, pull request; the playbook's older lines say MR, and this change mixes in no new word). The issue statuses open and fixing and the depends-on link match playbook 03 and the approved instructions. Fetching by explicit refspec is right. In a worktree of this head, MESH_CATALOG_DIR=…/mesh-catalog sh merge-check.sh exits 0 (records, index, cycle and words all pass).
Verdict: CHANGES at c2d5323dea5ac2b9f60e77138a523082bb60b791
1. **A finished issue left in `fixing` until the feature's delivery breaks playbook 03 and the glossary.** The new bullet says "An issue is never left in `fixing` while nobody works on it" and, one sentence later, "A finished issue stays in `fixing` until the feature's delivery". The finished issue's agent is gone, so after a day its worker is **stale** (03 step 2, glossary), and with no pull request of it open it is **abandoned** (glossary, ADR 0294): anyone may take it over without a reason. Say who holds it: for example, the lead moves each landed issue to `fixing` with `by` set to the lead (`take-over`, reason "landed on the feature branch") and notes the landing commit; `fixed-by` then names the feature's pull request once it opens (03 Rules: a commit or a pull request, never a branch). The bullet then also agrees with the approved instruction that keeps an issue in `fixing` only while its branch is actively worked.
2. **The lead is never defined.** "The lead holds the feature branch" is the first mention, and the glossary has no such word. Say in one sentence who the lead is (the session that names the feature, sends the agents and opens the pull requests in step 4), and say that the lead does the push in step 4, since "the agents never push".
3. **A delivery group needs at least two repositories.** The glossary and ADR 0239 §2 define a delivery group as two or more deliveries sharing a head branch name. A feature in one repository is one delivery, not a group. Write "when the feature touches more than one repository, its pull requests share the branch name and form one delivery group (ADR 0239)". "Delivered as one delivery plan" is also loose: each delivery has its own delivery plan, and the group delivers them as one unit.
4. **"The design's table of what waits for what"** assumes a design that has such a table. A reader coming to this cold should be pointed at the tracker's `depends-on` links (as the next bullet already uses them), with the design's table as the source when one exists.
5. **Markdown (minor).** The continuation lines added under steps 1, 3 and 4 follow the item's text with no blank line, so they render as part of the same paragraph ("…within the feature. The feature branch is never protected…"). Put a blank line before each, kept at 3-space indentation, so each renders as its own paragraph inside the item. It renders correctly as it is, just without the paragraph break.
Checked and fine: there are no node names in the added lines. Glossary words are used correctly (merge check, delivery plan, pull request; the playbook's older lines say MR, and this change mixes in no new word). The issue statuses `open` and `fixing` and the `depends-on` link match playbook 03 and the approved instructions. Fetching by explicit refspec is right. In a worktree of this head, `MESH_CATALOG_DIR=…/mesh-catalog sh merge-check.sh` exits 0 (records, index, cycle and words all pass).
A finished issue's agent is gone, so left in fixing it goes stale; the lead
takes it over until the feature is delivered. One repository is one
delivery, not a group; readiness comes from depends-on links (review
comment 12466).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Finding 1 (finished issue in fixing) is fixed. The lead takes the finished issue over, so its by names a current worker. When the feature's delivery is done, the issue is resolved with fixed-by naming the feature's MRs, which agrees with playbook 03 (resolve only from fixing; fixed-by names a pull request, never a branch). Non-blocking: a worker with nothing done on an issue for a day goes stale (glossary). For a feature that runs longer than a day, the lead could add an issue-tracker.note per landed issue at least daily. "Keeps working it" covers this, but does not say it outright.
Finding 2 (the lead undefined) is fixed. The lead is now defined, and the lead does the push.
Finding 3 (delivery group) is fixed. The text now says a delivery group needs two or more repositories (ADR 0239 §2), and that a feature in one repository is one delivery. Non-blocking: "delivered as one delivery plan" is still loose, because each delivery has its own delivery plan and the group delivers them as one unit.
Finding 4 (which issue is ready) is fixed. Readiness now comes from the depends-on links, which a cold reader can follow.
Finding 5 (markdown) is fixed. Each continuation paragraph now has a blank line before it at 3-space indentation, and renders as its own paragraph inside the item.
The playbook names no nodes. In a worktree of this head, MESH_CATALOG_DIR=…/mesh-catalog sh merge-check.sh exits 0 (records, index, cycle and words all pass).
Verdict: APPROVE at 071fc1c29dce270f0f687275f9781a64b084f4dc
1. **Finding 1 (finished issue in `fixing`) is fixed.** The lead takes the finished issue over, so its `by` names a current worker. When the feature's delivery is done, the issue is resolved with `fixed-by` naming the feature's MRs, which agrees with playbook 03 (resolve only from `fixing`; `fixed-by` names a pull request, never a branch). Non-blocking: a worker with nothing done on an issue for a day goes stale (glossary). For a feature that runs longer than a day, the lead could add an `issue-tracker.note` per landed issue at least daily. "Keeps working it" covers this, but does not say it outright.
2. **Finding 2 (the lead undefined) is fixed.** The lead is now defined, and the lead does the push.
3. **Finding 3 (delivery group) is fixed.** The text now says a delivery group needs two or more repositories (ADR 0239 §2), and that a feature in one repository is one delivery. Non-blocking: "delivered as one delivery plan" is still loose, because each delivery has its own delivery plan and the group delivers them as one unit.
4. **Finding 4 (which issue is ready) is fixed.** Readiness now comes from the `depends-on` links, which a cold reader can follow.
5. **Finding 5 (markdown) is fixed.** Each continuation paragraph now has a blank line before it at 3-space indentation, and renders as its own paragraph inside the item.
The playbook names no nodes. In a worktree of this head, `MESH_CATALOG_DIR=…/mesh-catalog sh merge-check.sh` exits 0 (records, index, cycle and words all pass).
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.
The operator asked (2026-10-14) for the feature rules to live in playbook 07, which already said one branch name, one worktree per repository and one MR per repository at the end. Feature 57 had been worked the other way, a pull request per issue into protected branches, and lost most of a day to merge checks.
Added:
The mesh-wide instruction proposed today becomes a pointer to this playbook once it merges.
MESH_CATALOG_DIR=../mesh-catalog sh merge-check.shpasses. No node names (hq is public).Delivery
novox/hq@071fc1c29dce— delivered since 2026-10-14T19:56:05ZDelivery 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.Verdict: CHANGES at
c2d5323deafixinguntil the feature's delivery breaks playbook 03 and the glossary. The new bullet says "An issue is never left infixingwhile nobody works on it" and, one sentence later, "A finished issue stays infixinguntil the feature's delivery". The finished issue's agent is gone, so after a day its worker is stale (03 step 2, glossary), and with no pull request of it open it is abandoned (glossary, ADR 0294): anyone may take it over without a reason. Say who holds it: for example, the lead moves each landed issue tofixingwithbyset to the lead (take-over, reason "landed on the feature branch") and notes the landing commit;fixed-bythen names the feature's pull request once it opens (03 Rules: a commit or a pull request, never a branch). The bullet then also agrees with the approved instruction that keeps an issue infixingonly while its branch is actively worked.depends-onlinks (as the next bullet already uses them), with the design's table as the source when one exists.Checked and fine: there are no node names in the added lines. Glossary words are used correctly (merge check, delivery plan, pull request; the playbook's older lines say MR, and this change mixes in no new word). The issue statuses
openandfixingand thedepends-onlink match playbook 03 and the approved instructions. Fetching by explicit refspec is right. In a worktree of this head,MESH_CATALOG_DIR=…/mesh-catalog sh merge-check.shexits 0 (records, index, cycle and words all pass).Verdict: APPROVE at
071fc1c29dfixing) is fixed. The lead takes the finished issue over, so itsbynames a current worker. When the feature's delivery is done, the issue is resolved withfixed-bynaming the feature's MRs, which agrees with playbook 03 (resolve only fromfixing;fixed-bynames a pull request, never a branch). Non-blocking: a worker with nothing done on an issue for a day goes stale (glossary). For a feature that runs longer than a day, the lead could add anissue-tracker.noteper landed issue at least daily. "Keeps working it" covers this, but does not say it outright.depends-onlinks, which a cold reader can follow.The playbook names no nodes. In a worktree of this head,
MESH_CATALOG_DIR=…/mesh-catalog sh merge-check.shexits 0 (records, index, cycle and words all pass).