home/ atoms/ livecoding-patch-vs-rewrite-decision

A wholesale section rewrite is only warranted when at a section boundary, the target shares few voices, and a patch would cost more edits

The default livecoding move is a patch (smallest change that achieves the intent). A wholesale rewrite is only warranted when all three conditions hold: (1) the set arc has reached a section boundary, (2) the target state shares few voices with the current state so patching would require more edits than rewriting, and (3) the audio path can absorb it (Strudel swaps gaplessly; the risk is legibility, not a dropout). Never wholesale-rewrite mid-phrase to fix a small mistake — patch the offending line and keep the groove.

Examples

Entering a drop section where the current dense techno texture shifts to sparse ambient: few shared voices, section boundary reached, Strudel can swap gaplessly → section rewrite justified.

Assessment

State the three conditions that together justify a wholesale section rewrite in livecoding, and describe the correct action when a small mistake occurs mid-phrase.

“Reach for a wholesale rewrite only when *all* of:”
context/ · L6-craft/cadence.md · chunk 1