Using Jev to build cheap verifiers for an agent harness
The author used Jev to build a custom verifier for the /goal feature in their agent harness, checking after every turn whether the goal is complete so long-horizon verification becomes cheap enough to scale.
One of the craziest use cases I’ve found for Jev: verifiers. I am so excited about this that I at least wanted to share the high-level idea. I used Jev to build a custom verifier for the /goal feature in my agent harness. It checks whether the goal is actually complete after every turn, making continuous verification cheap enough to scale. This means I can run more of these verifiers (previously handled by another expensive reasoning model) more frequently to keep the agents on track. System One models are perfect for verification. I think of this as scaling harnesses further by cleverly combining System One and System Two models. I have a feeling this will enable a new wave of scalable test-time compute methods. Watch this space closely. I've just started to experiment with this and am already seeing really good results. I need to explore and figure out a way to benchmark it. I will share more once I have more results. This is an insane unlock for long-horizon agents. You heard it here first. And you can expect to see more harnesses embracing this new pattern. Full guide dropping in the next couple of days.
I also realize that this is the most boring use case for Jev. All the flashy, unrealistic demos you see on X will never make it into production, so I wrote this to encourage deeper exploration that may not maximize engagement on X but will elevate results with your harness.