06-reference

indy dev dan 10 levels of jev

2026-09-28·reference·source: IndyDevDan (YouTube)·by IndyDevDan
jevtypesafesystem-one-modelsagentic-engineeringharness-engineering

"10 Levels of Jev For Agentic Engineers" — IndyDevDan

Full transcript: [[2026-09-28-indy-dev-dan-10-levels-of-jev-transcript]].

Why this is in the vault

IndyDevDan is a tracked tier-1 channel for RDCO's agent-harness practice, and Jev/TypeSafe is already an actively-tracked topic in the vault (10+ prior entries in the last two weeks, plus an installed typesafe:typesafe-ai skill and a completed security review of the TypeSafe skills plugin). This video is the first entry to lay out a concrete, ordered decision framework — "when does a narrow classifier replace an agent call, and when does it just support one" — that's directly reusable for RDCO's own gate/guardrail design.

Episode summary

Dan walks through 10 escalating use-levels of Jev (TypeSafe's "System One" fast/cheap JSON-programmed decision model), starting from a simple yes/no classifier (prompt-injection detection) through composite scoring, confidence-gated bash-command blocking, model/agent routing, in-agent guardrail hooks, self-compaction triggers, and finally "agentic Jev" — where the coding agent itself decides when and what to ask Jev. Screen-recorded live demos run each level against a real Pi coding agent, with cost comparisons showing Jev at a fraction of a cent versus dollars-to-thousands for calling a frontier LLM at the same volume.

Key arguments / segments

Notable claims

Guests

Solo — no guests.

Mapping against Ray Data Co

Levels 4 and 6 land squarely on RDCO's own harness-engineering practice: the bash-command reversibility gate and the pre-tool-call "Jev guard" hook are the same shape as AGENTS.md's own auto-mode classifier hard-gate (feedback_automode_classifier_hard_gate.md — deploy/production-write denial as a hard stop) and the allow-listed-command discipline already in place for wrangler.sh and other gated scripts. Level 8/9's "cheap file reads without loading the file into context" is a cheaper, narrower cousin of AGENTS.md hard rule #4 (route long artifacts through subagents) — where RDCO currently pays a subagent-dispatch cost to keep context lean, Jev-style classification could answer a yes/no or triage question about a file for a fraction of a cent without any agent dispatch at all, which is worth prototyping against the newsletter/YouTube ingestion pipelines' pre-filter steps. Jev itself is not new to RDCO — the typesafe:typesafe-ai skill is already installed and the topic has 10+ prior vault entries in the last two weeks — so this video's specific contribution is the ordered "level" framework for deciding when a narrow classifier should replace an agent call versus merely gate one, which is a reusable design checklist rather than a new tracked concept.

Related