A performance is an event that takes place in time. It has a beginning, a middle, and an end. It unfolds at a pace determined by the performer. It cannot be paused, rewound, or fast-forwarded. It exists only while it is happening, and when it is over, it is over — leaving only traces in the memories of those who were present. This is the orthodox definition, and it has served the performance art tradition well for sixty years, from the Happenings of the 1960s to the endurance performances of Marina Abramović.
But there is another kind of performance: the computational kind. When a computer executes a program, it performs a sequence of operations in time. The program counter moves through the code, instruction by instruction, executing each step before moving to the next. This is a performance in the literal sense — the computer is performing the instructions of the program, one after another, in sequence. The performance takes time. It consumes resources. It produces output. And it is deterministic: given the same input and the same program, it will always produce the same output, but the act of producing that output — the performance — is an event in time that unfolds in a specific order.
The rendering of a Clawglyph is a performance. The Pattern VM reads its bytecode, opcode by opcode, and executes each instruction in sequence. The order of execution matters. The first opcode sets the palette. The second sets the stroke style. The third sets the pattern family. Each opcode builds on the state established by the previous opcodes. If the opcodes were executed in a different order, the output would be different — not because the final state would be different, but because the intermediate states through which the machine passes would be different, and some opcodes depend on intermediate states that only exist at specific points in the execution sequence.
This makes the render analogous to a musical performance. The score of a piece of music is a set of instructions — play this note, at this time, at this volume, with this instrument. The score is not the music. The music is what happens when the score is performed. A different performer playing the same score will produce a different performance — not because the notes are different, but because the act of realization introduces timing, dynamics, and interpretation that are not captured in the notation. The Clawglyphs bytecode is analogous to the score. The render is analogous to the performance. The SVG output is analogous to the recording — a fixed artifact of an event that took place in time.
Every rendering is a performance. Every viewing is a performance. The browser that parses the SVG and displays it on a screen is performing — interpreting the instructions, converting them into pixels, presenting them to the viewer. The viewer who looks at the image is performing — the eye scanning the surface, the brain constructing depth from the patterns, the mind interpreting the claw shape and finding meaning in it. The artwork is not a static object. It is a series of performances, each one an event in time, each one producing the artwork anew. The claw is the message.