Overview & result
Mr. Buzzoni previews a 14-page PDF describing a proposed Jev-and-Claude workflow. Jev handles typed judgments for triage, context selection, command screening and evaluation; Claude handles work that needs generation, while code owns the branches. The original post includes a PDF flip-through video and links a related article.
From the original post
JEV + OPUS 5.5 IS INSANE FOR BUILDING A COMPANY BRAIN
I pulled the whole architecture out of the TypeSafe and Anthropic docs and packed it into a 14-page PDF
the 10 steps:
1. meet the pair
> Opus 5.5 thinks, Jev decides, your code holds the branch
2. stop asking a text generator for a yes or no
> Jev returns a typed answer with a calibrated probability in 0.44s for $0.00035
3. ask everything at once
> Choice, Score and Noul run in parallel, so the fourth question costs almost nothing
4. branch on the number
> 0.999 goes straight into the if statement. ~99% of turns end right here
5. stop routing blind
> Opus 5.5 to Sonnet and back costs 5.84 against 3.32 for staying on 5.5
6. keep one context warm
> cache reads at $0.20 per Mtok are 20x cheaper than a fresh load
7. escalate the hard part
> the toughest 1% goes to Opus 5.5 with 1M context and 66.4% on Terminal-Bench 4.0
8. score every chunk on every query
> keep whole, summarize or drop. the context gets rebuilt each turn
9. gate the actual command
> every bash call gets classified before it runs, inside your own code
10. judge 100% of runs
> $3.50 a day for 10,000 traces, and it matched the human label on all 500 decisions
the result: a while loop that paid a frontier model for every tiny call turns into a brain that spends a fraction of a cent to notice and pays properly only when it has to think
the person who brings this into their team walks into the budget meeting with the AI bill cut and the output up
the PDF maps the company brain. the loop side of it - how Jev takes a Claude bill from $765 to $3 a month - is in the article below ↓
How Jev fits in the loop
- The author proposes using Jev for repeated bounded judgments and escalating harder work to a generative model.
- Independent questions can cover routing, context relevance and risk, while application code owns execution and branching.
- The related article discusses command gates, stop checks and triage filters. The source is a learning resource, not evidence of a deployed company system.
How to reproduce
- Watch the PDF preview in the original post.
- Open the author’s quoted article, Loop Engineering Meets Jev Engineering, for the related loop examples.
- Check current TypeSafe and Claude documentation before adapting the architecture. No direct public PDF download link was present in the inspected post.
Why this build matters
Offers a map of where repeated decisions sit in an agent workflow, so readers can identify a small pattern to investigate first.
Limitations
- The full downloadable PDF was not available from the inspected source; this entry links the preview and related article.
- Cost savings, latency, model benchmarks and perfect label agreement in the original post are author claims, not independently verified results.
- The proposed command checks and model routing have not been independently run or validated by JevForAgents.