Build blueprint
Adaptive Game NPC Director
A runtime director selecting tactics, attention, difficulty response, and group coordination every tick interval.
- Problem
- Game encounters rely on authored condition trees or expensive generative agents.
- Why Jev
- Games need many typed decisions, not dialogue, under tight latency and cost constraints.
- Architecture
- World state → parallel NPC Choices/Scores → deterministic behavior trees → animation/action.
- Current alternative
- Behavior trees, utility AI, or LLM-driven NPCs.
- Jev advantage
- Probabilistic judgment could complement authored action execution at much higher frequency.
- Unknowns
- Network dependence and determinism requirements for games.
Why this confidence: Doom and MAGI demonstrations suggest interest, not production readiness.
This is an authored hypothesis derived from the research corpus. Nothing here demonstrates product demand, or that Jev performs well on this particular workload. Run the validation experiment before building past the MVP.
Sources
Limitations
- Network dependence and determinism requirements for games.
- This is a research hypothesis, not evidence of product demand or Jev performance in this workflow.
Supporting research
- Probabilistic predicate + deterministic action PlausibleJev supplies fuzzy predicates while TypeScript, policies, and workflows execute constrained actions.
- Confidence-gated agent control loops Authored HypothesisUse Jev repeatedly to route, verify, and decide whether an agent should continue or escalate.
- The strongest near-term architecture is Jev as a complement and control layer around generative models. PlausibleJev produces decisions rather than prose, and Vercel exposes it through an evaluation-oriented API.
- Parallel decision matrix PlausibleOne state is evaluated against many named questions, replacing repeated prompt/parse cycles.