Jev decisions

Jev reads a state and answers named questions with probabilities, never prose: yes/no, one of a set, a level on a rubric, or a box in an image. It is a classifier you program in plain language, fast (roughly 70-500 ms) and cheap (input tokens only, output is free), so it can sit on every turn, every tool call and every ticket. It decides; it does not write, compute or plan.

The shape of every system built on it:

gather (code, or an LLM that reads and writes)  ->  compute exact facts (code)
  ->  judge (Jev, one call, many questions)  ->  gate the probabilities (code)  ->  act (code)

An LLM may think and draft, Jev decides, code acts. Nothing consequential happens because a model said so in text. When an LLM writes the plan Jev's choices follow, the plan names exact values and steps and only what the menus can express; without a detailed plan Jev struggles with even elementary tasks.

Apply only the routes and checks for the selected job. Read a linked skill's named file from its installed folder when available, or from the linked source. Report an unavailable required reference instead of inventing it. [skill-authoring, DISTRIBUTION.md#composing-skills]