novox/hq
13
0
Fork 0
Code Issues Pull Requests 1 Releases Wiki Activity

Merge pull request 'Playbook 07: the prepare step looks for the orders a release hides, and fixtures come from the writer's shape' (#426) from docs/prepare-checks-release-orders into main

Browse Source
This commit was merged in pull request #426.
This commit is contained in:
mesh-tools
2026-10-18 19:33:32 +00:00
parent a353ed21c0 86e66dd51f
commit f7915f7f29
1 changed files with 13 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
00-META/process/07-feature-branches.md
+13 -1
View File
@@ -111,7 +111,19 @@ never into the running one, unless it blocks the running one.
2026-10-17), into issues of about 30 minutes each, one change each, in the order they land: the bound of a
fixing agent's issue is then a real bound. On 2026-10-17 one issue held four changes sized at four to six
hours; it ran past its 30-minute bound for over an hour, and the reports could only say "still on part D".
6. **Move the issues to `fixing`**, `by` naming the feature's agent for that repository.
6. **Look for the orders a release hides, before any agent starts** (2026-10-18: design 47's release 1-2 was cut
as one milestone and its prepare step found three orders inside it, each a cut of its own). Read, for each
repository of the release, what it takes from the others and how: an SDK change still ships before its users
(they vendor a pinned SDK, and a pin to a commit no branch holds is a download that fails later, issue 1148);
a new key on the wire between the controller and the node-engine is sent only to a node that says it reads it,
since the node-engine's decoder refuses an unknown key; the first module of a repository the catalogue has never
built registers only by the route the controller allows for it; and a part that needs something the bus or a
manifest cannot yet give (an event only a system account hears, a bucket whose keys expire) needs its decision
first. Each order found is said to the operator with the cut it asks for, never built around.
7. **Write fixtures from the shape the other side writes, never from memory** (2026-10-18: a watchman's tests
mirrored a build key the controller never writes, and every test passed): copy a value from the writer's code or
from the live bus, and name where it came from.
8. **Move the issues to `fixing`**, `by` naming the feature's agent for that repository.
## Step 1 — Develop (one fixing agent per repository, smaller model)