devwithjevJev-Triaged Access Ticket Workflow
Kaustav Banerjee describes an access-ticket workflow in which Jev triages the request and reviews the diff, while an LLM edits one line of configuration.
Kaustav Banerjee@entropy1996𝕏
An access ticket came in. Here's the workflow that closed it, step by step, with what each step cost.20 steps. 4 judgment calls go to @typesafeai 's Jev, not an LLM. The LLM runs once. Whole ticket: ₹0.16. Jev's share: under 1 paisa. What ran: 1. Code pulls the repo + ticket (free) 2. Jev triages: config change, 100% conf, 326 ms 3. LLM edits one line of config on a branch (30s, ~15 paise) 4. Jev reads the diff before the push: safe 95% 5. Code pushes, comments on the ticket 6. Spawns a monitor fot git and Jira The pattern: → code first, for anything with an algorithm → Jev for judgment: typed
Code pulls the repository and ticket, then pushes the change and comments on the ticket. The workflow also spawns a monitor for Git and Jira.
Also filed under Agents & browsers
- Building a Harness with Jev
Building a Harness with Jev Learn all about Jev, a new System One model from TypeSafe AI, and how you can use it in your agent harness. Jev is up to 200x ...
- How To Build A Harness With Jev | A LangChain x TypeSafe Conversation
How To Build A Harness With Jev | A LangChain x TypeSafe Conversation Hear from Sydney Runkle, Product Manager, OSS at LangChain, Allie Laabs, Founding Developer Advocate at TypeSafe AI, and ...
- Open-Weight Jev-Inspired Decision Model
tev1 is an open-weight Jev-inspired decision model fine-tuned from Qwen3.5 4B.
- MCP Proxy for Screening Agent Tools
Agent Chaperone is an MCP proxy that uses Jev to screen agent tool calls and tool results.