keeping score
A generative event score machine for the present moment. Each score is an instruction — spare, imperative, tender, or melancholic. A clock runs. Perform before time expires and the score is logged. Don't, and it destroys itself line by line. The next one arrives unrequested.
Lineage
Event scores. George Brecht. 1963.
Yoko Ono. 1964.
Fluxus.
What is different here
The scores are generated by a language model running entirely in your browser — no server, no API, no network request after the initial model download. The model has no knowledge that it is making art. It follows an instruction to produce a particular kind of structured text. The gap between that instruction and what arrives is part of the work.
Each score has a duration derived from its content. A score about waiting runs longer. A score containing an impossibility drops faster. The timer is not neutral.
To perform, hold. The hold is the performance. The machine records whether you did.
Non-performance is logged as UNREAD or MISSED. The session accumulates. The ratio is kept but not interpreted for you.
Once per session, the model is bypassed entirely. The machine speaks about its own condition. This is also a score.
When generation fails completely, the failure is exposed as a score in its own right. The error becomes the instruction. Nothing is hidden.
Technical
WebLLM · Phi-3.5-mini-instruct · WebGPU · single HTML file · no backend · Chrome 113+ or Edge 113+
After Brecht · After Ono · After Maciunas