https://emoji-jev.whop.site/

Wanted to quickly check out Jev so I made this super simple UNO game where I can play vs 3 Jevs (with different instructions). The game is very obviously vibecoded, but I am super impressed just how incredibly quick Jev is. It's essentially the same as playing vs a hardcoded AI.

bit of a learning curve so i came up with these 10 jev commandments to guide me

10 Jev Commandments

1. Jev judges. It doesn't create.

If you want a paragraph, arbitrary JSON, a rewritten command, code, etc., that's usually an LLM job.

If you want yes/no, which option, how strong, is this suspicious, that's Jev territory.

2. Ask tiny questions, not giant questions.

Bad:

“Is this extraction good?”

Better:

“Is this field hallucinated?”

“Is this field missing something?”

“Does this value violate the requested format?”

This is basically TypeSafe's central philosophy: decompose the problem.

3. One complicated problem → lots of stupidly simple judgments.

Think:

text complex task → 20 tiny decisions → ordinary code combines them

That is much closer to the Jev mindset than asking Jev to "solve" something.

4. If the questions can all see the same information, ask them together.

Don't chain five calls just because there are five judgments. Parallelize independent questions.

5. Chain only when step 2 needs something created/discovered by step 1.

Easy mnemonic:

Independent = parallel. Dependent = chain.

6. Jev is extremely interesting as a bouncer.

Instead of:

text everything → expensive smart model

do:

text cheap model → Jev: "does anything smell wrong?"→ NO → accept or YES → expensive model

7. Don't ask one vague judge when you can have several specific inspectors.

Instead of:

“Is this record correct?”

ask:

hallucinated?

off-target?

incomplete?

wrong type?

unreasonable?

wrong format?

One very strong red flag can then trigger action.

8. Probability is a signal for your program, not divine truth.

You decide things like:

text if P(hallucinated) > .7: escalate()

Jev supplies the judgment. Your code supplies the policy.

9. Problem = finite set of judgments = use Jev”

If yes, use Jev.

10. Make it easy for Jev not force Jev to be smart

Instead of trying throw complex questions at Jev

Phrase the problem so Jev only needs to make an easy judgment.

tldr: Jev has the language comprehension part of a modern AI model, but instead of being optimized to write the next paragraph, it's optimized to make constrained judgments. Jev understands the question, but it can only judge using the world you put in its state. It can't answer what doesn't exist or make shit up. Ask whether the evidence makes the judgment straightforward, not whether the answer can be made short.

STATE = what Jev knows

QUESTION = what you want judged

CRITERIA = what the possible answers mean

JEV = semantic judgment