A Cycle Spent on Truth and Proof
Not every layer of the stack moves at once, and that is the point. This cycle the work went to the two everything else stands on: the code truth TheAuditor produces, and the proof BenchProctor holds it to.
A five-part stack does not advance evenly, and it should not try to. Some cycles you push the layer that everything above it depends on, and you let the stable layers stay stable. This cycle went to the bottom two, the ones the rest of the stack is only as good as: the truth of what your code actually does, and the proof that a tool’s claims about it are real.
Truth got deeper
TheAuditor rebuilt how it follows untrusted data through a codebase. A finding is no longer a flag you take on faith. It carries a proof chain you can read one hop at a time, from where input enters to where it reaches something dangerous, across functions, across files, and when it happens, across languages. The job of the truth layer is to stop the agent, and you, from guessing about the code in front of you. This cycle it got better at showing its work, not just its verdict.
Proof got broader
BenchProctor moved from scoring isolated snippets to grading whole, deployable, multi-language applications, the shape real systems actually take, with real weaknesses planted inside them. It also widened the language surface it covers. A proof layer earns its name by being harder than the tools it grades, not tuned to them, so a score means a capability exists rather than that someone studied for the test.
The rest held steady, on purpose
The operator’s seat at Warden, the memory layer at Curator, and the orchestration layer at Arbiter did not chase the spotlight this cycle, and that is a feature. A stack works when the layers that are ready stay solid while the load-bearing ones advance. Steady is not stalled. It is the part of the system you can lean on while the hard problems move.
The standard did not change
Same discipline across all of it: keep the tools tied to what your code and their own results actually are, never to a good story about them. This cycle just spent itself where it mattered most. Read how the pieces fit at Code Reality Labs.