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.
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.