Stop building coding loops with Jev — it's a general-purpose semantic judgment function

SpreadUsual4084 · reddit · 2026-10-13

The author observes that nearly all Jev projects are coding use cases, but argues the pattern has nothing to do with coding — developers just build coding loops first.
Core thesis: Jev's real role isn't generation. It sits inside a loop answering small, bounded questions — which action, which file, keep or drop, safe or not, which model to route to. Long text and deep reasoning still belong to big models.
Using WorkBuddy, his non-coding harness, as an example: Jev decides whether a document warrants the expensive model, whether a spreadsheet row needs human confirmation, which queue a message goes to. Jev is the repeatedly-called judgment node; WorkBuddy is the loop framework. Neither replaces the other.
Conclusion: Jev isn't a chatbot competitor but a general-purpose semantic judgment function — state plus bounded question in, probability/score/options out. What determines output quality is the standards you put inside the loop, not the model.
Open question left by the author: which steps should stay outside the loop? His only answer so far is acceptance criteria.

More from coding & agent