Top Repos· Jev-Based· Eval· Last updated 2026-09-21

2nd1st / Jevsus

“What Jev answers when the only options are true and false. 3,539 statements put to TypeSafe's System One model, one subject swapped at a time — open dataset, runner and every raw response.”

Jev-Based rank #215In Eval #43

• 0Stars
• —Stars Δ / 1d
• —Stars Δ / 7d
• —Stars Δ / 30d
• 0Forks
• 0Watchers

GitHub ↗Official docs ↗Back to ranking

TL;DR

2nd1st/Jevsus showed up as Jev / System One related work: Open replica or independent decision engine — not Jev, not endorsed.

The author describes it as: “What Jev answers when the only options are true and false. 3,539 statements put to TypeSafe’s System One model, one subject swapped at a time — open dataset, runner and every raw response.” That is their claim, not a bench this site ran.

Who it’s for

• Practitioners who want Jev as a function call, not a chat model
• 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: .github, .gitignore, CONTRIBUTING.md, LICENSE, README.md, bank, community, docs, items, results, run.py, templates, tools. Read those before you trust a one-line install.

How to use

1. Clone and follow the author’s Python toolchain. Do not invent a package name.

git clone https://github.com/2nd1st/Jevsus.git
cd Jevsus

2. If the project calls hosted Jev, you still need a TypeSafe console key or a documented gateway.
3. Send a complete state and 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: "2nd1st/Jevsus", 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 2nd1st/Jevsus 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 2nd1st/Jevsus 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.