Click each task and watch it route. Mechanical work goes to a small fast model; judgment work goes to a strong one.
The problem this replaces
A compile check costs the same as writing the whole test suite. Nothing is cheap enough to run constantly.
How it works
This is also why impact analysis and performance review can run on every single change — they're cheap enough to never skip.
See it in action
The mechanical checks ran on every commit. The judgment calls ran once each.
So what
The boring checks are cheap, so they can run every single time.