jev-harness
A Pi agent harness built around TypeSafe's Jev (System One model): router, context picker, gate, verifier. Tested on Neon Postgres branches.
10 ★ on GitHub
What it is
An agent harness built around a System One model. Pi runs the agent loop, a Gemini model does the work, and TypeSafe Jev makes the small decisions around it: which model to use, which rules to load, whether a tool call may run, and whether the agent's report holds up. The agent works on a real Postgres database, and…
Getting started
From the README:
cp .env.example .envWhere the decision sits
jev-harness calls the hosted decision API rather than running its own weights. That keeps the project small and means its behaviour moves whenever the vendor ships a new model version. It also means an API key and a network round trip sit in the path of every decision.
Models it references: Jev, jev.
How active it is
Created 2026-09-24, last pushed 2026-09-24, 10 stars and 5 forks when we read it on 2026-11-02. Everything in this category is weeks old at most, so a stale push date means something different here than it would on a mature project. Check the repository before you depend on it.
Find out what your data actually supports
We turn your historical decisions into a frozen test set, then tell you which model, which threshold, and how much of it you can safely automate.