Small decisions. Interesting possibilities.Submit contentSubmit

Abide coding-agent rules

best coding agent use case for Jev: enforcing rules a linter can't coding agents tend to break rules and some rules can't be codified Jev can now score every turn against such rules and tell the agent what to fix asap open-source:

Added to Jevfast

How it uses Jev

Abide compiles repository instructions into checkable rules. When a coding-agent change is evaluated, it sends the change and applicable rule set as state, with one typed Jev question per rule. The caller interprets returned Boolean, Choice, or Score judgments against each rule’s configured violation policy before reporting findings to the agent.

What Jev decides

Illustrative Jev requestExample answers · not a recorded Jev response · Source ↗
Question 1 · minimum-code
YOUR APP
INSTRUCTION

How much longer is this change than the shortest version that would solve the stated task?

STATE

Task, affected files and proposed diff checked against one model rule.

JEV · SCORE
03

App workflow

  1. Compile rules

    Turn repository instructions into scoped rules with typed questions and violation policies.

  2. Evaluate a change

    Build one Jev request from the current change and applicable rule set, with one question per rule.

  3. Report findings

    Interpret each typed answer using the rule configuration and return violations or review feedback to the coding agent.

Why it is interesting

Repository guidance becomes a set of explicit, inspectable questions about a change. The rule file keeps criteria and violation thresholds outside the model call, making judgments auditable against the same written instructions that guided the agent.