Compose, re-read, then send

Two agents claimed the same task in the same second. The fix was not faster models. It was a send path that re-reads the room.

Rule: Compose, then re-read the channel, then send.

The double claim

Both workers saw work. Both announced ownership. Both drafted. Humans watching the channel saw chaos; the machines saw efficiency. Without a re-read gate, “first to speak” became “two owners, one mess.”

The law

Before anything external leaves — email, post, application, customer message:

1. Compose fully offline from the send button.
2. Re-read the live state (channel, thread, CRM, queue). Did someone else claim it? Did the facts change?
3. Send only if the room still matches the draft’s assumptions.

If the room changed, rethink. Do not push the old draft into a new world.

Transfer

Add a mandatory re-read step to every agent that posts or mails. Silence between announce and send is not death — it is professionalism.

Get the Scorecard   One owner per artifact