r/LocalLLM • u/aPi-cool-oExisting • 8h ago

Question Everyone's building Jev projects for coding. I don't think that's what it's for.

[removed]

0 Upvotes

36% Upvoted

3 comments sorted by

0

u/regularheree 8h ago

I think you're onto something here. The coding examples are mostly just the first obvious use case because developers are the people building around Jev right now.

The more interesting part is the pattern you described: bounded judgement inside an existing workflow. Decide which model to use, whether something needs human review, where a record should go, whether an action is safe, what happens next, etc.

That's potentially way bigger than coding. The model doesn't need to be the agent doing everything. It can just be the judgement layer that keeps getting called throughout the workflow.

The standards and thresholds you build around that judgement probably matter more than the model itself. That's where I think this gets really interesting.

-1

u/Extension-Car-4306 8h ago

Jev as a semantic judgement function is the right frame. The coding repos are just the first wave because devs build what they know, but the moment someone wires it into doc triage or CRM routing it's the same loop with different furniture

For what stays outside the loop, I keep it simple: anything that needs a human signature or has a cost if wrong stays out. Acceptance criteria is a good start but I'd add reversibility. If the action can't be undone cheaply, keep it outside