Jev-Driven SRE Diagnosis: What Worked and What Failed
matt_d
21 points
4 comments
October 07, 2026
Related Discussions
Found 5 related stories in 84.4ms across 8,687 title embeddings via pgvector HNSW
- Jev vs. Kev: open-source Jev alternative tested side by side felix089 · 12 pts · September 25, 2026 · 57% similar
- We Tested Jev on 100 Agent Tool Calls arseny_info · 11 pts · September 21, 2026 · 54% similar
- Jev Can't Be Calibrated alexmolas · 44 pts · September 23, 2026 · 53% similar
- Reverse-engineered Jev-like model rochansinha · 110 pts · September 16, 2026 · 53% similar
- Jev and System One Models: Calibration Beats Accuracy pansuriyakartik · 11 pts · September 25, 2026 · 53% similar
Discussion Highlights (4 comments)
clintonb
> Ultimately, we believe that incorporating Jev-driven diagnosis into an SRE agent’s workflow is a significant step toward effectively combining System One and System Two models. Why? What’s the end goal? Lower cost? Faster analysis? I configured an agent to respond to pages via Slack. It has access to ClickStack (for telemetry), Kubernetes, and GitHub. It runs one of the Sonnet models. The cost is so low, responding to less than a dozen pages a day (mostly from a very sensitive error count alarm) that swapping got Jev makes zero sense. This is especially true if the results are less trustworthy.
beebmam
It seems to me that Jev is designed for when many quick decisions, with low input context, need to be made. SRE work is probably best suited for very few critical decisions that need to be made, with high input context.
N_Lens
Lots of hype-mongering around Jev atm. Color me sceptical.
soltanov
Premise is flawed: SRE is not a throughput problem, it is an accuracy problem.