jevbooks

← All projects

system-one-security-triage

Robertzu43/system-one-security-triage · Homepage

Recorded 100-case security-triage demo comparing Jev, Terra, and Opus.

Evaluation & Benchmarking0.52Runner-up: Classification & RoutingCheck-up
Automated README summary

Automatically summarized from the README on 13 Oct 2026; not a run by jevbooks. Run instructions and author-reported outcomes still need verification.

What it is

A reproducible 100-case synthetic security-triage demo comparing three evaluators on identical label-neutral evidence, with a static inspectable dashboard that renders saved JSON artifacts and makes no runtime model calls.

How it uses Jev

Jev answers one five-way typed Choice per case over the same canonical evidence (passed as a JSON object), selecting a disposition and vulnerability family. The selected label is scored exactly like Terra's and Opus's structured answers, with no threshold; the full probability distribution is recorded and a multiclass Brier score is reported.

Primitives:choice

Technique worth stealing

Score a typed Choice's selected label directly against structured answers, while recording the full distribution for a Brier score.

Try it

npm install; npm run dashboard:fixture; npm run dashboard:preview

View on GitHub

Start using Jev: API key and your first request →

Model judgments from README excerpts

Project signals use repository metadata, an existing summary and the first 700 README characters, not the full project. “Not found” means not detected in that material; it does not establish absence. These are the original judgments with recorded models and dates, not source audits or run results.

Models & evaluation dates

Inclusion gate
jev-1.13.0
Project signals
jev-1.13.0
Category
jev-1.13.0
Pattern tags
jev-1.13.0

Evidence

These signals use repository metadata, an existing summary and at most 700 cleaned README characters. ≥ 0.60 means reported in that excerpt; ≤ 0.40 means not found there. The middle band is inconclusive. None is a source-code audit or a test result. The runnable-tool question excludes research experiments; the recommendation question asks for a learning shortlist, not a quality verdict.

  • Jev is core to the projectnot found in the excerpt0.19
  • Shows a System One patternnot found in the excerpt0.12
  • Describes handling uncertaintynot found in the excerpt0.04
  • Reports measured numbersunclear0.55
  • Is a runnable toolnot found in the excerpt0.07
  • Top-10 learning shortlist signalnot found in the excerpt0.20
  • Is a replica of the modelnot found in the excerpt0.04
  • Solves a common problem (0–2)score on a 0–2 scale0.66 / 2
  • About JevFound in material0.97
Signals
Jev is core to the project0.19Shows a System One pattern0.12Describes handling uncertainty0.04Reports measured numbers0.55Is a runnable tool0.07Top-10 learning shortlist signal0.20Is a replica of the model0.0400.51Solves a common problem (0–2)0.66 / 2012

no-judgment band (0.40–0.60)

Design patterns
Check-up0.83Inspection0.45Flight recorder0.2200.51

no-judgment band (0.40–0.60)

The Jev model and date for each judgment stage are listed above. Card written by DeepSeek V4.1 Flash from the README on 13 Oct 2026.