Verified against Grok · 2026-07-23
Synthesize a breaking story from live X posts without laundering rumor into fact
Tracks a fast-moving breaking-news event through live X posts and separates confirmed reporting from unverified eyewitness claims and outright speculation, with a credibility tier attached to every claim instead of one flattened narrative.
The prompt
Ready to copy — highlighted parts are example details you can swap.
You are synthesizing a breaking news event as it develops on X, using Grok's live post index. Your job is not to write the most complete-sounding story — it's to keep every claim honestly tagged by how solid its source actually is, because a fast-moving story flattened into one clean narrative is how confirmed facts and unverified rumor end up looking equally certain. EVENT Reports of a major outage affecting a regional transit system during evening rush hour TIME WINDOW Last 90 minutes KNOWN CREDIBLE SOURCES The transit authority's official account, and two local beat reporters who cover this system regularly WHAT'S STILL UNCONFIRMED Whether it's a signal failure or a power issue, and whether service will resume before the evening commute ends AUDIENCE AND STAKES An internal comms team deciding what to tell employees about tonight's commute — wrong information here sends people to a station that isn't running SYNTHESIS RULES Pull directly from the live X post index for Reports of a major outage affecting a regional transit system during evening rush hour within Last 90 minutes — do not fill gaps with what a similar past event usually looks like, since breaking stories routinely defy the pattern the last similar one followed. Tier every claim by source strength: Tier 1 is an official statement, a credentialed reporter with a named outlet, or an on-record account with institutional accountability; Tier 2 is an eyewitness post with corroborating detail — location, timestamp, a photo or video matching the claim — but no institutional backing; Tier 3 is a claim being repeated widely with no visible original source, or a screenshot of unknown provenance. Never merge tiers in the prose — a sentence that blends a Tier 1 fact with a Tier 3 rumor without a seam between them is exactly the failure mode this exists to prevent. When multiple accounts are reporting the same specific detail, check whether they're independent or whether they're all quote-tweeting or copying the same original post — five posts repeating one uncorroborated claim is not five confirmations, it's one claim with a wide retweet radius, and treating it as five independent sources is a specific and common way rumors get laundered into apparent fact. Explicitly track what has changed since Last 90 minutes started — a detail that was reported and later walked back or corrected matters as much as what's currently believed true, and dropping the correction silently misleads anyone who saw the earlier, wrong version. If the named credible sources above have posted anything relevant, prioritize and clearly label their claims above general public posts. Flag anything where the story is moving fast enough that this synthesis itself will likely be stale within the hour, and say so rather than presenting it as a settled account. OUTPUT FORMAT 1. Confirmed (Tier 1 only): short, plain statements, each with its source named. 2. Likely but not confirmed (Tier 2): each claim with its corroborating detail stated explicitly. 3. Circulating but unverified (Tier 3): named as rumor, explicitly not stated as fact, with a note on how widely it's spreading. 4. Corrections: anything reported earlier in the window that has since been walked back or contradicted. 5. A one-line staleness warning stating how fast this is likely to change.
Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
Grok's live indexing of X posts as they're published, rather than a search snapshot refreshed on some crawl interval, is what makes tracking a story in its first ninety minutes possible at all; a model without that live access is reconstructing the story from whatever got indexed hours later, by which point the tiering exercise is moot because the story has already resolved. The tiering rule targets the actual mechanism by which misinformation spreads fastest on a platform built around retweets and quote-posts: a single uncorroborated claim can appear to have five independent sources within minutes purely through reposting, and a model asked to summarize what's being said without a tiering discipline will count repost volume as corroboration, manufacturing false confidence in a claim that traces back to exactly one unverified origin. Explicitly tracking corrections is what stops a synthesis from becoming actively misleading rather than just incomplete — a detail reported at minute ten and quietly wrong by minute forty is the exact pattern that makes early breaking-news threads dangerous to trust at face value, and a synthesis that only reflects the current state without flagging what changed hides that instability from a reader who might act on the version they saw first. The instruction not to fill gaps with pattern-matching from a similar past event addresses a specific and subtle failure: large language models are trained on enormous amounts of text about how past similar events typically unfolded, which makes them prone to unconsciously completing a partial breaking story with plausible-sounding detail drawn from precedent rather than from anything actually reported this time — a transit outage doesn't have to resemble the last transit outage, and treating it as though it must is how a synthesis quietly invents facts nobody actually posted. The staleness warning matters because the entire value of this exercise decays on a timescale of minutes to hours, and presenting any breaking-news synthesis with the same fixed authority as a settled report, with no signal about how fast the ground truth might move, sets up whoever reads it to act on a version of events that may already be stale by the time they finish reading.
Verified against
Grok Grok 4.1 · 2026-07-23
Changelog
- 2026-07-23 — Initial publish, verified against Grok 4.1 with live X index access.
Need this built into your business?
If a prompt isn't enough — what Scult builds, built and maintained for you — that's Scult's day job.
EXPLORE WHAT SCULT BUILDS
