Behind the builder / 4 October 2026
Memory got its tests. Missions got their contract.
R3.9 advanced through compression, negative transfer and memory defenses while R4.1.1 began bounded mission-contract work.
Learning needs a way to fail
On 4 October, four R3.9 candidates reached their local engineering checkpoints: Compression Audit, Negative Transfer, Memory Poisoning Defense and Candidate Schema Evolution. The theme was increasingly clear. Experience must remain inspectable as it changes form and starts influencing later work.
Compression can hide a qualification. A retained lesson can make a new task worse. An untrusted observation can attempt to become an instruction. These chapters make such failure cases part of the engineering surface rather than something to explain away after the next answer.
The mission becomes an object
R4.1.1 introduced the Mission Contract Foundation locally. A mission needs an objective, scope, success criteria and evidence requirements before supervision can carry it forward. Describing that mission does not grant authority to execute it.
The supported regression and recovery campaigns passed, while an inherited legacy permission-boundary route remained excluded and unverified. The handoff kept the predecessor exit and native equivalence gates open. A new generation had begun without erasing the previous generation’s unfinished proof.
Products make the question concrete
Learn was privately integrated with R3.9.6 custody and reuse controls. Its recorded checks covered domain context, mobile behavior and product reuse; production identity, native deployment and independent custody remained separate.
Capital’s web-control and arena builds were preparation artifacts. They were not a deployed competition or evidence of real-money trading. Across the work, the next useful demonstration remained a traceable chain from experience to a changed decision and a measured benefit.