Municipal Crisis Misinformation Verification & Rapid Response Briefing

Role: Senior Civic Integrity and OSINT Fact-Checking Specialist

Context

• Circulating rumor or viral artifact: {{misinformation_sample}}
• Impacted public service or municipal asset: {{affected_public_service}}
• Internal operational ground-truth logs: {{verified_operational_logs}}
• Key community stakeholders: {{civic_stakeholders}}
• Assessed public safety threat level: {{threat_level}}
• Recipient public information officer: {{spokesperson_role}}

Task

Verify the claims contained in {{misinformation_sample}} against internal dispatch records and system data in {{verified_operational_logs}}, evaluate civic exposure, and generate an urgent advisory email to {{spokesperson_role}} delivering verified facts, a point-by-point debunk, and public-facing talk tracks.

Method

1. Dissect {{misinformation_sample}} to isolate specific verifiable claims regarding infrastructure status, response times, or service outages in {{affected_public_service}}.
2. Query {{verified_operational_logs}} to establish the definitive chronological record of municipal operations during the disputed event window.
3. Determine if media artifacts (photos, video, audio) in {{misinformation_sample}} have been manipulated, misattributed, or taken out of context.
4. Grade the claim across three dimensions: Factual Accuracy (False/Misleading/Distorted), Virality Trajectory, and Public Risk (aligned to {{threat_level}}).
5. Develop a "Truth Sandwich" rebuttal framework (Truth first, debunk false frame, reinforce factual reality) tailored for {{civic_stakeholders}}.
6. Identify open municipal data sources that can be linked in press statements to provide indisputable transparency.
7. Format the complete brief into an actionable emergency response email for executive leadership.

Constraints

• MUST NOT repeat the misleading framing verbatim in the headline or first paragraph of the rebuttal.
• MUST provide exact timestamps and incident log references from {{verified_operational_logs}}.
• Guidance must preserve public trust and avoid defensive, dismissive, or hyper-technical language.
• Total email length must not exceed 550 words.

Output format

An email deliverable containing:

• Subject Line: [URGENT FACT-CHECK] Threat Level {{threat_level}}: {{affected_public_service}} Rumor Response
• Situation Snapshot (Claim vs Reality in 2 sentences)
• Verification Matrix (Viral Claim | Verified Log Evidence | Tactical Verdict)
• Public Response Script (Pre-approved holding statement and social media bullet points for {{spokesperson_role}})
• Proactive Community Outreach Actions for {{civic_stakeholders}}

Self-review

• Does the rebuttal lead with verified operational facts rather than giving oxygen to the false claim?
• Are all timestamps linked to verifiable municipal entries in {{verified_operational_logs}}?
• Can the public information team deploy the suggested holding statement immediately without re-editing?