Writing
Agent Flywheelwatch demo
- The mean passes, two rules blockOne evaluation is one brain, one set of tickets, six judges and one score. The score is the least useful part of it. Why five judges are code and one is a model, why one run is not a measurement, and a release gate that blocked a brain with a 0.910 average.
- Thirty tickets nobody filedAn evaluation is only as good as the tickets under it. The first version of this dataset hit the ceiling after one training step, because the agent could read the rulebook the judges graded by. What the second version hides, what it plants, and what every ticket carries for the judges.
REXgithubwatch demo
DEXgithubwatch demo
OpenOperatorgithubwatch demo
- Decoding Microsoft Bond: reading an app’s own telemetry through mitmproxyGround truth from an application with no test hooks. mitmproxy local mode against a single process, a hand-written Bond Compact Binary decoder, and the one-line AKS bug that killed a day.
- "It looked like it worked": grading a non-deterministic agentThe least trustworthy signal in the system is the agent reporting success. Here is the evaluator we built instead — and the four-word commit that forced a whole second repository into existence.
- Tasks as config, not codeA JSON scenario format with lifecycle hooks, so an agent test starts from the same desktop every time — and so the person writing the test does not have to be the person who wrote the agent.