Play a phrase.
Cue the next one.
A pattern editor lets someone enter notes and listen. A performance brief asks how changes behave while someone is playing. That difference reaches timing and interaction design.
Edited build brief
Keep the four pitches, eight-step pattern, modest synthesis gain and accessible controls. Reframe this as a small live performance instrument. Offer three named pattern slots, keyboard shortcuts and touch controls for cueing the next slot, and switch only at a loop boundary. Make tempo changes preserve the musical position. Show what is playing and what is queued. Add a clear stop-all control that silences both current and scheduled notes. Explain these controls in the interface and test them during playback.
How it feels
The reader plays a musical phrase, cues its next move and shapes the performance as it continues.
What the agent needs to build: interface
Playing and queued states, large cue controls, discoverable shortcuts and an immediate stop control matter more than adding rows of decorative knobs.
What the agent needs to build: structure
Store which pattern is playing and which is queued. The scheduler must switch at the end of a loop and arrange notes on the audio clock. Save the three slots as separate patterns, and validate all their rows and values on restore.
Acceptance check
Cue a slot halfway through a loop. The old pattern should finish the loop before the new one starts. Stop while notes are scheduled and verify silence and cleared highlights.
Design exercise: try a new build from this edited brief. Status: proposed; implementation and testing pending.