Jev in practice: typed decisions, scoped authority
niyikiza
28 points
6 comments
September 23, 2026
Related Discussions
Found 5 related stories in 75.4ms across 7,510 title embeddings via pgvector HNSW
- Introducing System One Models and Jev albelfio · 1080 pts · September 15, 2026 · 61% similar
- Jev: The Model That Gives AI the Properties of Code zenlikethat · 17 pts · September 15, 2026 · 60% similar
- Show HN: jevals – replacing LLM judges with typed Jev decisions gbayomi · 15 pts · September 20, 2026 · 59% similar
- Jev, Prolog, Pi, and the dream of probabilistic logic programming schmuhblaster · 16 pts · September 21, 2026 · 58% similar
- Kev: Tiny Jev-like family of decision models built on top of Qwen3.5 tosh · 426 pts · September 21, 2026 · 58% similar
Discussion Highlights (5 comments)
fuzzumms
Interesting way to guarantee some sort of safety for automated decisioning
dj0_
The task bound idea is interesting. I’m starting to hear more of this theoretically on AI enterprise architecture. Has anyone actually implemented it successfully?
ozs
Interesting to experiment with. As AI agents get faster and cheaper (and thus more accessible) having good governance around their actions becomes more important to cut down on shadow agents/runaway agentic actions and consequences
gyre007
Shockingly vibed blog post. Actually hurt my brain reading this and I had to stop.
chstr_9
Haven't seen many attempts to govern agents using task bound authority. Curious to see how this holds up in real world implementation.