Behind the builder / 6 October 2026
The control plane learned to govern its surroundings.
R4’s local environment and authority work advanced while Capital and the jazz manuscript remained preparation candidates.
Execution has an environment
The amended 6 October close recorded selected local and recovery checks for R4.12 through R4.15. Environment management, migration, capability authority and information flow bring the surroundings of execution into the mission’s control plane.
A worker needs more than a good prompt. It needs a declared environment, a bounded grant and rules for information crossing its boundary. Moving work between environments must preserve what was authorized and what evidence belongs to it.
Passing locally leaves work to do
The release-inheritance comparisons remained blocked, with native integration, independent review and formal acceptance open. Those limits stayed in the record alongside the successful local campaigns.
The control ledger also lagged the later engineering packets. The useful response is reconciliation: preserve the newer evidence and repair the summary deliberately. A dashboard should not become a shortcut around the underlying release gates.
Preparation is a distinct milestone
Capital v0.7 passed its private preparation checks without establishing connected models, deployment or browser acceptance. The jazz-crossword manuscript retained its complete grid structure but was still not publication ready.
Archive verification also advanced without claiming a deletion had occurred. These are concrete kinds of progress. Each leads to a different next test: a connected execution path, a reader’s judgment or a verified restore. Counting all of them as launches would obscure the work that remains.