adhere
Project / 项目 · In the catalogue / 在目录中查看
What Jev decides here · Jev 在这里做什么决定
noul, choice: read in the code by a model, not yet by a person 由模型在代码里读到，尚无人复核
a model read the call site; no person yet 模型读过调用点，尚无人复核 · · Cited file / 引用的文件: src/providers/jev.ts
Summary · 摘要
Linter for rules a normal linter cannot check, written as Markdown with should and should-not examples. It asks Jev whether each file breaks each rule and reports those above a threshold with the part of the file Jev points at; adhere validate flags rules a linter could check or that contradict.written by a model
用来检查普通 linter 查不了的规则的 linter，规则以 Markdown 写成，附“应当”和“不应当”的示例。它询问 Jev 每个文件是否违反每条规则，报告概率高于阈值的规则并标出 Jev 指向的代码片段；adhere validate 会找出本可由普通 linter 检查或彼此矛盾的规则。模型撰写机翻
Notes · 备注
Jev is the default provider; a config can name another key or model. adhere lint estimates the cost and asks before sending when run in a terminal. The npm package is @drkmttr/adhere. A coding agent can write the rules (adhere rules create). Row drafted from the discovery queue (issue #14) by an AI assistant that read the README and the cited file on 2026-11-06; a maintainer has not yet read the call site.
Jev 是默认的模型提供方，配置中可指定其他密钥或模型。adhere lint 会估算费用，在终端中运行时发送前先询问。npm 包名为 @drkmttr/adhere。规则可由编程智能体编写（adhere rules create）。本条目由 AI 助手根据发现队列（issue #14）起草，于 2026-11-06 阅读了 README 和所引文件；维护者尚未亲自阅读调用点。
Launches · 发布记录
Not launched yet. 还没有发布过。 Launch it / 发布它 ↗ · How a product launches / 怎样发布一个产品
Makers · Maker
Made this? Confirm or correct its entry / 这是你做的？确认或更正条目 ↗
The same form takes the product's one line and a demo link, in its maker's own words. 同一个表单也可以补上产品的一句话和演示链接，用 Maker 自己的话。
Badge for its README · README 徽章
[](https://kydlikebtc.github.io/awesome-jev/products/adhere.html)One line for the product's README, linked to this page. The picture says that it is listed; while it is on the launch board, that it is launching; after a week in the top three, its place. It is rebuilt with the site, so the line never needs changing. 放进产品 README 的一行，链接到本页。图片显示已收录；在发布榜上时显示正在发布；进过某周前三后显示名次。它随网站一起重建，这一行不用再改。
Also under this pattern · 同一模式的其他产品
latitude-llm
Open-source observability for AI agents that flags where agents fail in their traces. A shadow provider asks Jev one noul per flagger dimension, at most 11 per call; the cited file does not show whether those answers change any flag, and the README does not mention Jev.
reticle
Checks an agent's "done" by driving the running app and returning pass, fail or cannot tell. Its benchmark harness asks Jev, in one call on captured evidence, five nouls (did the intended consequence happen, is the capture clean, did the app error), a pass/fail/unknown choice and a severity score.
celesto
Secure and persistent computer for AI agents -- build your own Grokbot, and Muse.
atomic
Coding-agent runtime in which workflows are versioned TypeScript stages with executable checks, review gates and human approvals. Its AI package lists Jev from models.dev as a System One decision model on five providers, apart from the chat models; the README does not say where a workflow calls it.
abide
Hooks into Claude Code, Codex, OpenCode and Pi and, on every edit or turn, asks Jev one yes-or-no question per rule in AGENTS.md or CLAUDE.md, showing only the rule and the diff; a broken rule goes back to the agent to fix. On 93 replayed sessions Jev flagged 39 edits; a reviewer confirmed 10.