Question 1

How is Jev used in THE HUNDRED EYES?

Accepted Answer

For each of 100 fictional observers the artwork asks one Choice question plus four Score questions; the 500 answers drive the animated eye reactions and the later analytics view, and are sent as four parallel batches of 25 with the previous result kept on failure.

Question 2

Can the artwork run without a Jev API key?

Accepted Answer

Yes. Without a key it uses a simple in-device rule-based judgment. Setting TYPESAFE_API_KEY and JEV_MODEL in .env.local enables real Jev decisions, and only the posted text is sent -- never interim typing.

Question 3

How do I run the artwork locally?

Accepted Answer

npm ci, then npm run dev -- --port 3001 and open http://localhost:3001. With no key it falls back to a provisional in-device judgment. To connect Jev, set TYPESAFE_API_KEY and JEV_MODEL in .env.local, which is git-ignored, and take .env.example as the sample. The README explicitly says not to put the key in NEXT_PUBLIC_ variables or in source.

Question 4

What actually happens after I post something?

Accepted Answer

One blink travels once from the near eyes to the far, and four fixed intuitions surface first as the voices most likely to land. Jev's visibility score can be low without removing that character's reach. Opening post-analytics lights the same 100 eyes and shows head counts for six intuitions, reported exactly as judged whether indifference is common or rare, plus an inside-100 view listing each eye's image and four emotions. Rewrite resends to the same 100 and shows the change against the previous result.

Question 5

How much of the piece is authored rather than generated?

Accepted Answer

The characters, their short lines, the situations set for them and the voice staging are all defined by the author; Jev never freely generates dialogue. Counts of people seeing nothing and people criticizing are not fixed, and model confidence is deliberately not used as emotional magnitude. Blink order and speed are staging and do not report Jev's processing order or measured latency. The 100 observers are fictional, not real people or X statistics.

Question 6

What is the licensing and endorsement boundary?

Accepted Answer

Code, production material and screenshots are MIT licensed, while fonts and external libraries keep their own licences. Jev's model and API are not included in the repository, so each visitor sets their own TypeSafe key. The README states the piece is not an official TypeSafe production, publication or approval, and that past design notes in docs and git history describe an older implementation with fixed counts and per-keystroke judging.

Question 7

How is the artwork tested, and does it degrade gracefully?

Accepted Answer

npm run lint, npm run build and npm run test:e2e. Ordinary tests use the provisional judgment or synthetic answers and post nothing to Jev or to X; browser tests cover desktop-sized and mobile-sized Chromium plus some WebKit, and you need npx playwright install first. The piece itself handles phones, a reduced-motion setting and a lightweight mode for devices without WebGL, with sound off by default and toggled from the control at the top right.

THE HUNDRED EYES

About this project

Highlights

Questions about this entry

More Jev resources like this

From the Jev guides

From the Jev community