novox/hq
18
0
Fork 0
Code Issues Pull Requests 2 Releases Wiki Activity

Playbook 07: the fixed scope and fixing what you open agree, a blocking issue still goes in
mesh/merge-gate head aa56e9b9e7c5 merged into trunk abdd364f091d — pass: the change touches no module of the mesh's graph
Details
mesh/repo-check head aa56e9b9e7c5 merged into trunk abdd364f091d — pass: its merge-check.sh passed
Details
mesh/delivery delivered
Details

Browse Source
This commit is contained in:
jochen
2026-10-21 14:42:27 +02:00
parent 4f8c469329
commit aa56e9b9e7
1 changed files with 6 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
00-META/process/07-feature-branches.md
+6 -5
View File
@@ -64,16 +64,17 @@ built, no milestone of another design starts: its issues stay `open`, and nobody
lead who finds another design's milestone already in `fixing` asks its owner before starting its own. A small
fix ([playbook 08](08-small-fixes.md)) and an issue that is in no design's milestones are not held by this rule.
**Scope is fixed at the prepare step.** An issue found during a feature goes to the next milestone or the next feature,
never into the running one, unless it blocks the running one.
**Scope is fixed at the prepare step.** An issue found during a feature never goes into the running milestone, unless it
blocks the running one: it is fixed in between or right after the delivery, as the next paragraph says, or goes to the
next milestone or the next feature.
**An issue opened along the way is fixed by the session that opened it** (the operator, 2026-10-21): it is never only
listed under "Opened along the way" and left. A small one (one repository, about an hour) is fixed in between, as a
small fix ([playbook 08](08-small-fixes.md)) while the milestone waits on a check, an Approve or a delivery plan; the
rest are fixed right after the milestone's delivery, before the next milestone starts, together on one branch where
they share a repository. Either way it stays out of the running milestone's branch and pull request, so the scope
above holds. Only an issue owned by another design's running milestone, or one that needs a decision or the
operator first, waits, and the report says which and why. Each report's line "Opened along the way" says for every
they share a repository. Either way it stays out of the running milestone's branch and pull request, unless it blocks
the running milestone, so the scope above holds. Only an issue in another design's milestones (one design is built at
a time), or one that needs a decision or the operator first, waits, and the report says which and why. Each report's line "Opened along the way" says for every
issue whether it is being fixed in between, after the delivery, or waits, and on what.
## Step 0 — Prepare (the lead, larger model)