What it is
Editorial checks that run while editors write.
What it does: A schema author attaches named questions to a field, for example "Is this easy to read?" as a Noul, an evidence scale as a Score, or a tone label as a Choice. Jev reads only that field, and the answer appears as a chip under it. The answer is stored in a sibling field, so it can be queried. Warn and require rules turn the answer into a warning or a publish block.
Why it belongs in the showcase: A CMS integration that turns Jev answers into stored, queryable editorial gates instead of free-text feedback.
Caveats: Beta release; no published accuracy numbers; handle the gateway key with care.
Evidence
Public MIT repo and npm package (0.2.0 at intake); the README documents three question types, warn and require rules that turn an answer into a field warning or a publish-blocking error, and re-evaluation shortly after a field is edited; calls go to Jev through Vercel AI Gateway; screenshots show example chips such as Readable 90% and Tone Casual.
Caveats
- Beta: the README says 0.x releases may change until stored value shapes are frozen at 1.0.0
- The gateway key set in the Studio tool can end up in dataset exports and backups; the README advises a dedicated key with a spend limit or a proxy server
- No accuracy evaluation is published; thresholds are set by the editor team
Unofficial case page. Stars / list position observed for heat; do not treat heat as a quality SLA. Review the upstream README before you depend on it.