Respond to a live broadcast integrity crisis

---
name: respond-to-a-live-broadcast-integrity-crisis
category: media
description: Respond to a live broadcast integrity crisis with human protection, independent preservation, signal reconstruction, editorial containment, audience correction, clean recovery, and accountability. Use when a live program may be fabricated, hijacked, manipulated, or dangerously misrepresented.
---
# respond-to-a-live-broadcast-integrity-crisis
## When to use
- Use when a live broadcast includes a false source, unauthorized edit, synthetic media, account takeover, signal substitution, hidden sponsorship, dangerous delay, or disputed recording.
- Use for simultaneous broadcast, stream, social, syndication, clipping, caption, translation, and archive effects.
- Do not rebroadcast harmful material merely to investigate it.
## Preconditions
- Establish conflict-checked incident, editorial, safety, legal, security, distribution, archive, accessibility, and audience-protection owners.
- Create an independent evidence store and trusted communication channel outside potentially compromised production systems.
- Define emergency stop, correction, platform contact, law-enforcement, and staff-protection authority before changing evidence.
## Procedure
Run four linked workstreams: human and public protection; source, signal, and version reconstruction; truthful distribution correction; clean recovery and governance.
1. Open a live broadcast integrity crisis timeline with UTC clocks, evidence custodian, decision IDs, uncertainty, and preservation holds.
2. Protect threatened guests, sources, staff, and audiences; remove precise location or identity data and provide accessible safety instructions.
3. Fence compromised accounts, remote control, contribution links, automation, graphics, captions, translation, archives, and distribution without destroying logs.
4. Preserve camera and audio ISOs, switcher state, edit decisions, talkback, graphics, prompts, caption feeds, encoders, transport streams, CDN objects, player events, credentials, recordings, and public derivatives.
5. Build a source-to-audience graph with stable IDs, UTC and native timecode ranges, cryptographic hashes, audio and visual perceptual fingerprints, transcript ranges, caption and translation lineage, clock offsets, transformations, confidence, signatures, releases, and platform receipts.
6. Reconstruct source, contribution, edit, signal, credential, platform, recording, derivative, and audience reconciliation across every published route.
7. Distinguish verified fact, allegation, synthetic or altered element, technical failure, editorial decision, impersonation, and unresolved absence.
8. Compare independent source recordings, return feeds, transport fingerprints, platform copies, caption and translation logs, public captures, and downstream archives.
9. Stop or replace the affected program with an honest holding slate when identity, consent, safety, rights, or editorial authority is uncertain.
10. Issue a versioned, accessible audience notice stating what is known, unknown, affected, preserved, removed, corrected, and still under review.
11. Notify distributors and derivative publishers with stable asset IDs, exact URLs, hashes, replacement status, requested action, and recipient acknowledgement.
12. Recover through clean devices, separately administered identities, rotated credentials, reviewed automation, trusted sources, independent output monitoring, and two-person release.
13. Test replay, caption, translation, clipping, syndication, geo, archive, correction, and emergency-stop paths before resuming.
14. Search segment fingerprints across DVR windows, delayed feeds, transcodes, cropped clips, scheduled posts, caches, downloads, mirrors, and syndication; reconcile corrections, takedowns, replacements, citations, complaints, and exposure until each route's maximum delay window expires and acknowledgement is independently verified.
15. Conduct independent editorial, security, safety, labor, accessibility, and governance review with protected reporting and tracked reforms.
## Failure plan
- Keep the affected signal stopped or clearly marked when source authenticity, editorial authority, or audience safety cannot be established.
- Preserve conflicting versions and publish bounded uncertainty instead of presenting an incomplete reconstruction as final.
- Escalate credible threats, coercion, nonconsensual exposure, or ongoing manipulation through protected channels without compromising sources.
## Worked example
A global awards stream is hijacked through a remote graphics account while a synthetic presenter clip, false emergency caption, altered translation, and edited social excerpt spread before the clean program recording is recovered.
## Done
- A live broadcast integrity crisis timeline records human protection, facts, uncertainty, evidence, decisions, signals, versions, communications, and recovery
- Source, contribution, edit, signal, credential, platform, recording, derivative, and audience reconciliation proves the disposition of every material route
- An audience correction, recovery, and accountability report records notifications, acknowledgements, clean production proof, residual exposure, independent findings, and reforms