Jev Broadcast Lab

An operator lab for TypeSafe Jev, built after the team joined the TypeSafe waitlist: a chess match as the flagship page, a row of smaller judgment booths that reuse the same client, and a separate Fast Flag catalog. It runs in public without putting the API key in the browser.

As jev-latest on POST /v1/systemone, sending a state plus named questions. Each question is a Choice (one key from a closed criteria map), a Score (a number on a labeled scale) or a Noul (a 0-to-1 mass). Independent questions in one request cannot see each other's answers.

Three layers: a static site under web/ that is never allowed to hold TYPESAFE_API_KEY; a local Python server that attaches the key from .env for operators; and a Cloudflare Worker that holds the key for the public site. GitHub Actions also refuse a tree that looks like it contains a TypeSafe key or a personal email.

A tight schema under pressure. chess.js 1.4 owns legality and Jev only picks among a closed LAN list (cap 255); Stockfish.js 18 lite WASM runs in the browser for an operator HUD. Engine centipawns, best move, PV, accuracy and captures never go into Jev's payload, keeping judgment and facts separate.

The same contract is reused on tickets, safety, search, chat, emotion, debate, cheating cases, tool names, PGN snippets and a tiny grid. Gates live in page code: the safety filter has Jev propose pass, review or block, then the page applies a confidence floor.

No. The README says the team applied to the TypeSafe Jev waitlist and was accepted, and the lab is independent work meant to show what System One can do under a tight schema, not to speak for TypeSafe. It explicitly says it is not a chess engine and not a chatbot.

A second product: dump-gated Roblox ClientAppSettings packs with a Picker and a Builder at /flags/, on black and white pages that do not share the esports HUD of the broadcast booths. The captured README does not describe how Jev is used there.