Catch contract drift hidden in OpenAPI prose

01 · Role in the system

What Jev does here

Structural compatibility is checked deterministically; the semantic layer sends bounded questions to Jev about what changed in descriptions, examples, defaults, retry behavior, ordering, pagination, authorization, and error semantics. Jev never writes a review and never changes a specification - it returns typed decisions with probabilities, and deterministic Python decides whether to pass, request review, or block. The output is a counts table plus per-operation findings, available as markdown or SARIF. A dry-run mode needs no API key: it shows exactly which changed prose would be sent for semantic review. The reproducible benchmark suite exercises ten semantic-only contract changes, and a separate repository verifies the published GitHub Action and SARIF upload from a real consumer workflow. Ships on PyPI and the GitHub Marketplace as an independent, unaffiliated community project.

02 · Control boundary

Where Jev sits

Deterministic diff first; bounded semantic questions to Jev second; deterministic code turns typed answers into pass, review, or block with SARIF output.

Code owns the loop, permissions, thresholds, validation, and side effects. Jev owns only the bounded judgments described above.

03 · Known limits

What this evidence does not prove

• Semantic review needs an API key and sends the changed prose of your specification to the provider; the dry-run shows the scope before you enable it.
• The benchmark suite is ten hand-built semantic changes, not a corpus study.
• An independent community project, explicitly unaffiliated with TypeSafe AI, in early status.

04 · Attribution

Public sources

This is a Community record: the project was published by a third-party community author.

• ShuhanSun ↗Community · github · public · checked 2026-09-23