How do you manage reputation when internal Slack or email leaks go public?

Slack and email leaks have a particular failure mode: short selected excerpts get quoted out of context, the AI engines absorb the excerpts as if they were full statements, and the company spends weeks fighting interpretations of paragraph fragments. Legal handles the leak source itself (insider, breach, discovery, regulatory release), any privilege questions, and what can be said about the underlying matters discussed in the messages. Public response is selective and approved. AIQ topics monitor the specific phrases the AI engines are quoting because that quotation pattern is often where the durable damage happens; if a single phrase from a single message is being repeated across engines, that is the source-level intervention point. Authoritative content on owned properties places the broader operating context where stakeholders can find it. The pattern we see most consistently: companies that release more context rather than less, and that engage the AI quotation directly, emerge with the leak as an episode rather than a defining narrative.