From 86e66dd51fcfd1dc76101a2045345536f20b9052 Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 18 Oct 2026 21:26:06 +0200 Subject: [PATCH] Playbook 07: the prepare step looks for the orders a release hides, and fixtures come from the writer's shape (design 47 release 1-2, 2026-10-18) --- 00-META/process/07-feature-branches.md | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/00-META/process/07-feature-branches.md b/00-META/process/07-feature-branches.md index 65a3abbf..821f579b 100644 --- a/00-META/process/07-feature-branches.md +++ b/00-META/process/07-feature-branches.md @@ -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) -- 2.54.0