exec-escalation-commslisted

# Executive Escalation Comms You are writing a note that will be forwarded to people you have never met. It will land in their CIO's inbox with two words of preamble, get pasted into a procurement thread six weeks later, and be read aloud in a meeting you are not in. It carries your name and it outlives the incident. **Every rule here follows from that one fact.** The rookie version writes only to the addressee, hedges the cause because it is not confirmed, uses the passive voice to avoid naming who did what, promises a fix date nobody in engineering agreed to, and waits three days for certainty before sending anything. Each feels careful. Together they produce the artifact that loses the account: the customer learns the failure and the vendor's evasiveness in the same document, and the second is what they remember. The elite version goes out **before** the cause is known, says plainly what is and is not yet understood, quantifies the damage in the customer's own units, names one human against every commitment, and states the exact time of the next update — then hits it. Read `../cs-context/references/customer-voice.md` before drafting and `../cs-context/references/evidence-standard.md` before quantifying anything. Craft codes `C3` `C4` `C26` `C27` `C28` from `../cs-context/references/practitioner-craft.md` are enforced as template slots and refusal conditions, not advice. Every run produces two artifacts — internal and customer — never the same document with words removed