Community · E2 · artifact verified
Steer a music composition with enum labels
A playground asks Jev to decide only closed-vocabulary labels for character, key, meter, and phrasing while deterministic code writes, engraves, and plays the notes.
01 · Role in the system
What Jev does here
Across eight allowlisted typed operations, Jev picks the composition's character, form, key, meter, texture, palette, tempo, dynamics, instrument, and per-phrase harmony-book entries from closed enums, and the trolley demo adds table Choices, difficulty and absurdity Scores, and a Noul on what most people would pull. No operation ever emits notes or sentences; a pure renderer expands the plan into chords, a VexFlow engraving, audio, and MIDI, and the plan JSON stays editable so listeners can hear a single label change.
02 · Control boundary
Where Jev sits
A style string to a plan of typed enum judgments; a deterministic render seam turns the plan into score, audio, and export without knowing about the model.
Code owns the loop, permissions, thresholds, validation, and side effects. Jev owns only the bounded judgments described above.
03 · Known limits
What this evidence does not prove
- Musical and trolley outcomes are demonstrations of typed planning, not evaluated quality or alignment claims.
- The server accepts only the eight typed operations, and its in-memory rate limit resets on every serverless cold start.
04 · Attribution
Public sources
This is a Community record: the project was published by a third-party community author.
- wustep ↗Community · github · public · checked 2026-09-18