jev-demo
Project / 项目 · In the catalogue / 在目录中查看
What Jev decides here · Jev 在这里做什么决定
Support triage (工单分拣), Model routing (模型路由)
choice, noul, score: read in the code by a model, not yet by a person 由模型在代码里读到，尚无人复核
a model read the call site; no person yet 模型读过调用点，尚无人复核 · · Cited file / 引用的文件: shared/jev.ts
Summary · 摘要
Three Spanish-language demos of one pattern, Jev decides and code acts: Jira ticket triage that applies, marks for review or escalates; a pre-flight pass that flags functions before Claude explains only those; and a PR router sending each pull request to rules, Haiku or Sonnet.written by a model
三个西班牙语演示，展示同一模式：Jev 决策、代码执行。Jira 工单分诊，按结果直接应用、标记复核或升级；预检扫描先标出有问题的函数，再只让 Claude 解释这些函数；PR 路由把每个 pull request 分给规则、Haiku 或 Sonnet。模型撰写机翻
Notes · 备注
Calls real services only, with no mock mode: Claude through claude -p, Jira Cloud and the GitHub CLI. No LICENSE file. Row drafted from the discovery queue (issue #14) by an AI assistant that read the README and the cited file on 2026-11-04; a maintainer has not yet read the call site.
只调用真实服务，没有模拟模式：通过 claude -p 调用 Claude，并使用 Jira Cloud 和 GitHub CLI。仓库没有 LICENSE 文件。本条目由 AI 助手根据发现队列（issue #14）起草，于 2026-11-04 阅读了 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/jev-demo-soyjorgepilo.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 · 同一模式的其他产品
spring-ai-typesafe
A community Spring AI starter bringing typed decisions to Java, with a builder API over the three question types.
jevelry
CLI, TUI and library keeping questions for Jev in small files called jevels; seventeen ship, for tickets, issues, pull requests, logs, alerts and failing tests. Each answer's certainty becomes act, mark for a person, or fall back, and every decision is logged so thresholds can be tuned on outcomes.
jev-triage
Go command-line tool that sorts messages by urgency: one Jev request per message asks a choice of kind (bug, billing, feature request, account, other), a 0–3 urgency score and a noul on whether the sender sounds frustrated. Below 0.8 category confidence a message goes to a review-by-hand list.
Jev on AI/ML API
Another gateway route, notable because its endpoint path and request envelope differ again from both the native API and Cloudflare's.
Jev on Cloudflare Workers AI
Workers AI binding and REST samples asking a noul, a choice and a score in one call, with the full response including per-answer confidence.