Question 1

Are the council votes real model output or fixtures?

Accepted Answer

Both, depending on the key. In live mode each submission makes one request containing 36 independent questions and the votes come back from the model. Without a key the app offers four scripted demo proposals whose votes are authored fixtures, clearly labelled in the app, exported cards and copied text, and a failed live request never becomes a synthetic vote. Nothing is persisted locally, but proposals are sent to TypeSafe.

Question 2

Does the enthusiasm score mean the model was confident or correct?

Accepted Answer

Neither. Confidence is a property of the answer distribution, not a measured accuracy percentage, and enthusiasm and confusion answer different questions so they can legitimately disagree. Each member answers three separate questions: a Choice for approve, oppose or baffled, a four-level enthusiasm Score displayed on a 0-100 scale, and a Noul giving the probability the character struggles to understand the idea or its relevance.

Question 3

What does the room score actually measure?

Accepted Answer

A game score, not a quality metric: 100 times (1 minus the yes/no imbalance over total yes plus no) times the share of members voting at all, rounded, and zero if every member is baffled. A clean yes/no split scores 100, so a unanimous vote scores zero. The inspector is the place to look at the underlying distributions and token counts rather than the score.

Question 4

Is it safe to deploy this publicly with my own key?

Accepted Answer

The key is read server-side from .env.local as TYPESAFE_API_KEY, with TYPESAFE_MODEL optional and defaulting to jev-latest, and it must never carry a NEXT_PUBLIC_ prefix; the dev server needs a restart after changes, and a deployment without a key still serves the scripted demos. Proposals and votes are not persisted, though they are sent to TypeSafe. Note the bundled burst guard is per instance, not a global quota, so add platform rate limits and a provider spending limit for public live voting.

Question 5

How do I run it, and what does it need?

Accepted Answer

Node.js 22, 22.13 or newer, with the major pinned in .nvmrc and package.json, plus npm. Then git clone, npm ci and npm run dev, and open the printed URL, normally http://localhost:5173. The develop path is npm test, npm run typecheck, npm run build and npm start, which serves the production Next.js build on port 3000. It is React with the native Next.js App Router and a Node.js API route, and it needs no database and no authentication service.

Question 6

Who are the twelve members, and how would I add one?

Accepted Answer

An accountant, a golden retriever, a vampire, a kindergarten teacher, a pirate, an HOA president, an astronaut, three raccoons in a suit, a knight, a chef, a houseplant and an IT wizard. To add one, edit lib/council.ts with a personality, a display identity and a few captions per vote, add a portrait, and update the fixed demo fixtures; lib/engine.ts is where the typed questions are constructed. The layout and the export are deliberately built for twelve members rather than any number.

Question 7

What can I take away from a session?

Accepted Answer

Save card downloads a PNG containing the proposal, the portraits, the votes and a live or demo label. Copy verdict copies a short summary and deliberately does not post anywhere. Peek inside opens the decision inspector with the returned distributions, confidence, model identifier, token counts and server-measured duration. Supported browsers can also expose an optional convene_council WebMCP tool that calls the same action as the visible interface.

Extremely Specific Council

About this project

Highlights

Questions about this entry

More Jev resources like this

From the Jev guides

From the Jev community