<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Jev on Tokenise</title><link>https://tokenise.rosvetic.com/tags/jev/</link><description>Recent content in Jev on Tokenise</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Thu, 29 Oct 2026 17:54:00 +0000</lastBuildDate><atom:link href="https://tokenise.rosvetic.com/tags/jev/index.xml" rel="self" type="application/rss+xml"/><item><title>Stop waking the agent for flaky CI: a Jev confidence gate in under 50 lines of TypeScript</title><link>https://tokenise.rosvetic.com/posts/ci-failure-triage-jev-confidence-gate/</link><pubDate>Thu, 29 Oct 2026 17:54:00 +0000</pubDate><guid>https://tokenise.rosvetic.com/posts/ci-failure-triage-jev-confidence-gate/</guid><description>&lt;p&gt;A pull request goes red at 4:40pm. The agent you wired to CI failures wakes up, reads 3,000 lines of log, forms a theory about a TypeError and starts editing files. The real cause was a registry timeout during &lt;code&gt;npm ci&lt;/code&gt;. Twelve minutes of tokens later, you have a diff nobody needed. Flip the case: a genuine failing assertion gets a blind re-run, fails again, and the PR sits another 10 minutes.&lt;/p&gt;</description></item><item><title>Jev won't write your code. Here's where it fits in an agent pipeline anyway</title><link>https://tokenise.rosvetic.com/posts/jev-decision-model-agent-pipeline-fit/</link><pubDate>Thu, 29 Oct 2026 17:50:00 +0000</pubDate><guid>https://tokenise.rosvetic.com/posts/jev-decision-model-agent-pipeline-fit/</guid><description>&lt;p&gt;Jev doesn&amp;rsquo;t write code, doesn&amp;rsquo;t chat and doesn&amp;rsquo;t summarise anything. TypeSafe AI&amp;rsquo;s own docs say so, and add that it isn&amp;rsquo;t a model to swap in behind Claude Code, Cursor or Copilot. That sounds like a reason to skip it. It&amp;rsquo;s closer to the opposite: the useful part of Jev is the part of your pipeline that currently burns a full LLM call to answer a question with three possible answers.&lt;/p&gt;</description></item></channel></rss>