ixi lang rewrites an agent's score in the editor when it is transformed, keeping the code a live view of current state

A distinctive feature of ixi lang is that when a method transforms an agent’s score (e.g. shake scrambles the order), the code itself is updated in the document: the text briefly highlights in a different color, then is replaced by a new score representing the transformed, currently-running state. This makes the editor a live, current representation of what is playing rather than a historical snapshot of what was typed. It serves two purposes: cognitive offloading (you can read the current state directly, and revert effortlessly by undo) and live-performance transparency (a projected screen shows the score evolving). This ‘code that rewrites itself’ philosophy contrasts with most live-coding systems, where the visible code reflects the performer’s last intent, not the running state.

Examples

After swap paul, the score paul -> obo[1 2 4 1 2 ] is replaced in the editor by paul -> obo[4 1 1 2 2 ]; future 4b:20 >> shake yoko schedules automatic scrambles, and each rewrite is shown live in the document.

Assessment

Explain what ‘self-rewriting score’ means in ixi lang and give two advantages it offers over a setup where the editor shows what was typed rather than what is running.