An autonomous live edit should carry exactly one concept-id and never bundle two ideas into one save

A standing constraint over the whole autonomous decision table is one concept-id per save: each edit realizes exactly one idea and never bundles two changes into a single save. Bundling makes an edit illegible — the audience (and the agent’s own later evaluation) cannot attribute the perceptual change to a specific move — and it violates the cadence diff-size ladder that keeps edits bounded. Single-concept edits keep the performance legible and reversible: if a move does not land, exactly one thing must be undone. This constraint holds regardless of which row of the decision table fired.

Examples

Adding a hi-hat layer and simultaneously opening a filter sweep in one save bundles two concept-ids and is disallowed; the two moves should be two separate saves on successive cycles.

Assessment

State the one-concept-id-per-save rule and explain how it keeps a live edit legible and reversible.