1816586742-stack / jev-craft
“让 Agent 长出「操作杆」:用 System One 模型(Jev)承担高频判断、多模态模型当眼睛。给思路 + 可跑的参考实现(75 条离线断言,零依赖零 key)”
Jev-Based rank #212In Demo #42
- 0Stars
- —Stars Δ / 1d
- —Stars Δ / 7d
- —Stars Δ / 30d
- 0Forks
- 0Watchers
GitHub ↗Official docs ↗Back to ranking
TL;DR
1816586742-stack/jev-craft showed up as Jev / System One related work: Runnable demo or product experiment that uses Jev as a decision layer.
The author describes it as: “让 Agent 长出「操作杆」:用 System One 模型(Jev)承担高频判断、多模态模型当眼睛。给思路 + 可跑的参考实现(75 条离线断言,零依赖零 key)” That is their claim, not a bench this site ran.
Who it’s for
- Agent / harness authors who need a typed gate, route, or prune step
- Anyone who needs the unofficial line: jev.pro does not issue keys and is not TypeSafe
What’s inside
Top-level entries on GitHub at generation time: .gitignore, LICENSE, README.md, docs, impl, verify.mjs. Read those before you trust a one-line install.
How to use
- Clone and follow the author’s JavaScript toolchain. Do not invent a package name.
git clone https://github.com/1816586742-stack/jev-craft.git
cd jev-craft
- If the project calls hosted Jev, you still need a TypeSafe console key or a documented gateway.
- Send a complete
stateand typed questions. Code owns control flow after the probabilities.
Hosted Jev still looks like a function call — wrapper or not:
{
model: "jev-1.13.0",
state: { source: "1816586742-stack/jev-craft", brief: "..." },
questions: {
gate: { type: "noul", instructions: "Should we act on this state?" },
route: { type: "choice", instructions: "Pick one next system.", criteria: ["code", "review", "human"] },
},
}
Try this
Put Jev on one real brief
Wire 1816586742-stack/jev-craft so one real state (ticket, diff, or utterance) becomes a Choice plus a Noul. Do not ask Jev to write the user-facing reply.
Schema-safe ≠ correct
On a case 1816586742-stack/jev-craft gets wrong, write down the schema-legal answer it returned and the human label. Do not “fix” it by asking Jev to generate an explanation.
FAQ
Does this replace the TypeSafe SDK?
Only if the author implemented a full client. Most harnesses still call the vendor SDK or raw HTTP.
Are the star chips live?
Star, fork, and watcher chips refresh from the public GitHub API via a scheduled job. The prose on this page is editorial.
Sources
Public repository metadata and TypeSafe documentation. No private claims.