REPOSITORY ANALYSIS

jev-chess

Chess moves, evaluations, persona opponents, and game classification using TypeSafe AI System One models. Resolves natural language move intents into legal moves, evaluates positional sharpness and king risk in parallel, and powers historical persona opponents (Tal, Capablanca, Petrosian).

E2 · source reviewedPublic material or source evidence was reviewed. A fixed-version source review requires checking a pinned revision; this is not a reproduction, performance endorsement, or safety guarantee.
Stars
2
Forks
0
License
—
Last commit
2026-09-21

What Jev does here

jev-chess invokes Jev primitives via `@typesafe-ai/sdk` for natural-language move resolution, multi-dimensional position evaluations, and persona style scoring.

Adds structured choices or scores to the workflow; performance and cost benefits have not been independently verified.

Pinned client and browser bundle reviewed. No-key outputs come from a handcrafted simulator, not measured Jev probabilities. The bundled SDK rejects browser initialization, while the live wrapper supplies no browser opt-in; entering a key is not a verified working live path. No browser run or playing-strength test was performed here.

What task does this project fit?

Map a player's natural-language chess intent to an already legal move set.

Material analysed:

From input to action

  1. Generate legal moves with the chess engine.
  2. Use the no-key simulator or inspect the intended live-wrapper path; the bundled browser path has an SDK initialization guard.
  3. Apply a permitted move or show alternatives when confidence is insufficient.

Implementation details that matter

Legality is provided by the chess engine

The model selects among verified legal moves rather than inventing board coordinates. This constrains syntax and legality, not move strength.

Inspect the supporting source ↗

The no-key client is a handcrafted simulator

typeSafeClient.ts switches between LiveTypeSafeClientWrapper and SimulatedTypeSafeClient. The simulator derives values from move features and even sets fixed confidence values; those are not measured Jev probabilities.

Inspect the supporting source ↗

The bundled browser demo's live path is blocked

LiveTypeSafeClientWrapper constructs the SDK with only apiKey. The checked-in public/app.js SDK rejects browser initialization by default; setApiKey stores the key before constructing the wrapper. This static mismatch means the wrapper's existence does not prove that entering a key enables live inference.

Inspect the supporting source ↗

When to choose it

Use the project to study an intent interface and explanation rubrics. Use a dedicated chess engine when move quality or tactical correctness is the goal.

How to inspect it yourself

Compare setApiKey/getTypeSafeClient with the SDK browser check in public/app.js. Do not paste a real key into the static demo; an integrator should use a server-side proxy that keeps credentials off the page.

Limits of this review

  • No game or paid evaluation was run here.
  • A legal candidate can be strategically bad; confidence does not prove playing strength.
  • The SDK/browser mismatch was established by static inspection; the browser demo was not executed.
Primary material used in this analysis