The codex as a composing score

A codex gives the reader a local language for making and reading the poem. Its key establishes a sound field; its seed names the pressure that starts the work; its engine says what may happen to that seed. The symbols can remain visible in the finished poem. They can also be used as a working score from which the poet writes another realization. Neither version has to be treated as a defective copy of the other.

A poem can expose its own rules, recruit letters as operators, and let an operation change the subject. The opening declaration is therefore part of the composition. The poet chooses how much explanation a reader needs and how much uncertainty to leave in the performance.

In the example, a weight becomes a wait through a declared sound relation. The association with a queue then shifts the subject from measuring objects to distributing time. The final question returns to weighing, but its object is now an unequal human experience. The sequence supplies a reason for the return; simply repeating the opening word would not produce that change.

Watching /weɪt/

⟦prepare⟧ weight / wait
⟦mutate⟧ weight → wait
⟦propagate⟧ wait ↝ queue ↝ numbered ticket
⟦release⟧
The scale has no setting
for the last person served.

Making and checking the poem

Define K, Θ and E first. Write preparation, mutation, propagation and release as distinct decisions, then compose or retain the score as the poem. Keep a legend beside unfamiliar marks. Read every arrow aloud. A formal change needs a rule; an associative arrow needs a persuasive connection.