jevbooks

← All projects

jev-doom-agent

lukaske/jev-doom-agent

Browser Doom agent: Jev picks tactical macros from structured state.

Game & Simulation0.66Runner-up: Agent DecisionsInspection
Automated README summary

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

What it is

A browser-native experiment where two isolated Chocolate Doom 3.1.1 WebAssembly instances play the same Freedoom map from identical initial state, with live decision telemetry and composable AI controls.

How it uses Jev

The server sends structured game state (health, armor, ammo, damage, coordinates, kills, line-of-sight monsters, visible pickups), model "jev-latest", and a typed choice question to the TypeSafe API. The returned choice, probabilities, and confidence are validated; low-confidence or failed calls are marked FALLBACK. The chosen tactical macro is executed by a local motor controller as Doom inputs.

Primitives:choice

Technique worth stealing

Convert engine observations into a bounded tactical schema and let a typed Choice model select macros, with explicit fallback labeling.

Try it

npm install && npm run dev, open http://127.0.0.1:5173/compare, click Connect Jev and paste a TypeSafe API key.

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 projectFound in material0.71
  • Shows a System One patternFound in material0.70
  • Describes handling uncertaintynot found in the excerpt0.05
  • Reports measured numbersnot found in the excerpt0.04
  • Is a runnable toolFound in material0.86
  • Top-10 learning shortlist signalunclear0.44
  • Is a replica of the modelnot found in the excerpt0.07
  • Solves a common problem (0–2)score on a 0–2 scale0.01 / 2
  • About JevFound in material0.98
Signals
Jev is core to the project0.71Shows a System One pattern0.70Describes handling uncertainty0.05Reports measured numbers0.04Is a runnable tool0.86Top-10 learning shortlist signal0.44Is a replica of the model0.0700.51Solves a common problem (0–2)0.01 / 2012

no-judgment band (0.40–0.60)

Design patterns
Inspection0.91Fail open, fail closed0.69Funnel0.2400.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 19 Oct 2026.