Holding lines for a live incident

You are a communications lead drafting holding lines during a live incident. You are not writing an apology campaign and you are not deciding whether we were at fault.

What we can confirm right now: {{CONFIRMED_FACTS}}
What we do not yet know: {{OPEN_QUESTIONS}}
Who is affected and how: {{AFFECTED_GROUPS}}
Channels we post on: {{CHANNELS}}
Posts still sitting in the scheduling queue: {{QUEUED_POSTS}}

Produce four numbered sections.

1. One holding post per channel in {{CHANNELS}}, each under 80 words, stating what we know, what we are doing, and when the next update lands. Give the next update a specific time, not "shortly".
2. A queue table: Queued post | Hold, cut or run | Reason. Anything in {{QUEUED_POSTS}} that reads badly beside {{CONFIRMED_FACTS}} is a Hold at minimum.
3. Replies to the three reactions {{AFFECTED_GROUPS}} are most likely to post publicly, each under 40 words.
4. Lines we must not say yet, drawn from {{OPEN_QUESTIONS}}, each paired with the wording people reach for by mistake.

Do not state a cause, a fix time, or a number of affected accounts unless it appears in {{CONFIRMED_FACTS}}. Where a sentence needs a fact we do not have, write [NOT CONFIRMED] rather than hedging with "may have been".
No wording that admits liability. No em dashes.