X (Twitter)
The fastest pulse. Threats, complaints, and on-the-ground reports surface here first. Each post is read by the AI classifier and tagged Critical, High, Medium, or Low — with a written reason you can challenge.
No single feed tells you whether an event is safe. A weather alert alone misses the protest. A protest alone misses the wildfire smoke. SignalGuard fuses 70+ live signals across four pillars — Chatter, Environment, Movement, Context — scores each one against the same severity scale, and consolidates the picture for the people running the event.
This page is a plain-English tour of every signal grouped the same way they're grouped in the dashboard, the per-signal alert mute list on /notifications, and the executive PDF brief — so the taxonomy you learn here is the taxonomy you run the product against.
People talk about events before, during, and after they happen. Ten different platforms, ten different communities, ten different vantage points — from open-platform shouting to allowlist-curated channels and the global news cycle — plus a derived crowd-surge classifier that re-reads all of that chatter for the language of a developing crush. We pull from all of them so the read isn't dominated by any one platform's tone.
The fastest pulse. Threats, complaints, and on-the-ground reports surface here first. Each post is read by the AI classifier and tagged Critical, High, Medium, or Low — with a written reason you can challenge.
Long-form context. Local subreddits ("r/LasVegas", "r/Coachella") are where attendees vent about logistics, organize meetups, and post warnings. Threat-coded keywords are scored the same way as X posts.
Smaller user base, but disproportionately journalists, civic organizers, and infrastructure-watchers. Catches stories X misses or buries.
Decentralized — many independent servers. Strong overlap with international and activist communities. Useful for events with cross-border attendance or political dimension.
Allowlisted public channels — protest coordination, resale rings, counter-demo callouts, and football-firm chatter. Channel set is operator-curated, not crawled.
Short-form video chatter — flash-mob style mobilization, ticket-plug accounts, walkout planning. Severity weights views-per-hour velocity, not raw view count.
Public posts and status threads from Truth Social, scored the same way as the other chatter feeds — mobilization language, named targets, and event-specific coordination — for an audience that doesn't overlap much with the mainstream platforms.
Video uploads about the venue, recent incidents, or recurring event franchises. Comment threads on those videos often contain protest plans, ticket-fraud warnings, and rumors that don't appear in text-only feeds.
A 24-hour-refreshed global news index that reads thousands of news outlets and flags articles mentioning protest, violence, terror, unrest, and security around the event, venue, or location. Tone-scored — a wave of negative coverage is itself a signal, even if no single headline is alarming.
A dedicated threat-intelligence sweep across known extremist, resale, and coordination channels — distinct from the general Telegram chatter feed. Messages are scored for direct threats against the venue, artist, or event and ranked by how on-target they are.
Tor-indexed hidden-service mentions of the venue, event, or artist, surfaced via the Ahmia index. Hits are de-duplicated by onion address and ranked by whether they're direct, on-target references versus passing mentions.
A derived classifier — no new feed. After the chatter sources resolve, every post is re-read for crowd-dynamics intent and distress: gate-rushes, oversell, ingress-crush, stage-surge, and the explicit distress language ("can't breathe," "people going down," "barrier's bending"). The strongest categories dominate the score, so one credible distress report outweighs a hundred routine hype posts.
Public Instagram posts tied to the event via its hashtags, with captions read by the same threat classifier as the other chatter sources. Scoped to each event's official hashtags (Instagram has no public keyword or location search), with promo- and giveaway-caption filtering so marketing noise doesn't register.
A derived read — no new feed. It compares this scan's chatter volume, and the count of flagged Medium+ posts, against this event's own baseline from earlier scans. The question isn't how loud the conversation is right now, it's whether it's multiplying — and whether the multiplier itself is accelerating.
A derived read — no new feed. It watches the flagged-post log for the same author or handle resurfacing across scans and across events. A single hostile post is noise; a handle that keeps coming back is a fixation pattern — and a direct input to the subject-centric Persona view.
What's happening in the physical environment around the venue — the forecast and active warnings, wind and gusts, lightning, heat stress and UV, air quality, severe-weather outlooks, active fires, recent ground motion, and how far the show's own noise carries to the neighbours. These don't lie and don't trend. When the environment is the threat, every other signal is downstream.
Authoritative US government forecast plus active warnings (heat, severe storms, flood, wildfire smoke, hurricane, tornado). Includes the day-of-event high/low, wind, and rain probability for the venue.
Live US AQI plus per-pollutant readings (PM2.5, PM10, ozone, NO₂, SO₂, CO) and a 24-hour forecast. Covers wildfire smoke, ozone alerts, dust, and inversion smog — anything that makes the air harder to breathe.
NOAA Storm Prediction Center categorical outlooks for today and tomorrow — checks whether the venue's location falls inside an SPC risk polygon (TSTM through HIGH risk for tornadoes, hail, and damaging wind).
Satellite-detected active fire hotspots within a configurable radius of the venue, with distance, fire radiative power, and detection confidence. Pairs with the Air Quality card — FIRMS sees the fire, AQI sees the smoke.
The authoritative "is there an official warning in effect HERE, right now" layer — tornado, severe-thunderstorm, flash-flood, extreme-heat, red-flag fire, and winter-storm watches and warnings issued for the venue's point. Severity tracks the worst active alert: Extreme reads Critical, Severe High, Moderate Medium.
Live wind and gust speed at the venue, scored against the thresholds outdoor events actually plan to: gusts of 25 mph read Medium (secure loose staging), 40 mph High (a common stage-evacuation / load-out trigger), and 58 mph Critical — the NWS severe-thunderstorm wind criterion.
Real-time strike detection from the Blitzortung network, scored by the nearest strike in the last 30 minutes. It encodes the outdoor-event "30/30 rule": a strike within ~10 miles reads Critical (suspend-play range), within ~30 miles High, within ~50 miles Medium.
Wet Bulb Globe Temperature — the heat-stress index that factors humidity, wind, and solar load, not just air temperature. Pulled directly from the NWS forecast gridpoint where available, estimated from Open-Meteo elsewhere. Scored against the same work-rest thresholds the NCAA, US military, and OSHA use.
Current UV index at the venue on the WHO global solar scale. A daytime crowd-health and duty-of-care read: 11+ (Extreme — burn in minutes) reads High, 6–10 (High / Very high) Medium, below that Low. A background-tier signal that informs posture but never drives it on its own.
A simplified ISO 9613-2 propagation model that predicts the show's A-weighted level at nearby noise-sensitive receptors — hospitals, care homes, schools, residential — pulled from OpenStreetMap, and flags exceedances of each type's limit. The wind term is live: sound carries downwind and is lost upwind, so which neighbours are exposed changes as the wind rotates, recomputed roughly every half hour.
Seismic events from the last 7 days within range of the venue, with magnitude, depth, and distance. Severity escalates with both magnitude and proximity — a M5 quake 10 km away reads very differently from a M6 quake 200 km away.
A land/vegetation fire-danger read for the venue — the Fosberg Fire Weather Index computed from temperature, humidity, and wind over the show window, escalated by any active NWS Red Flag Warning or Fire Weather Watch.
Flood, flash-flood, and river-stage risk — active NWS flood products (warning → Critical, watch → High, advisory → Medium) plus the nearest USGS stream gauge with its current stage and rising/falling trend.
Wildfire-smoke transport and PM2.5 air-quality forecast over the show window — current and peak US AQI with the hour it crosses Unhealthy, so you see smoke arriving before it lands. Adds trajectory and lead time to the current-only Air quality signal.
A derived signal — no new feed. It converts the live Wind & gusts read into a per-structure operational margin against demountable-structure action levels: go, caution, reduce, or stop, with the headroom in mph against the configured limits for stages, rigging, screens, and temporary structures.
A derived go/caution/no-go window for pyrotechnics, naked flame, and special effects — combining the live wind, lightning, and fire-danger signals against their environmental limits. NO-GO on lightning in range, an active Red Flag, extreme fire danger, or gusts over the pyro wind limit.
How trustworthy the venue forecast is — not what it says, but how much the models agree. We read a multi-model weather ensemble across the show window and measure the spread between members for temperature, rain, and wind. A tight spread means the forecast is solid; a widening spread means the models diverge and the plan should carry both branches.
A planning-horizon read on tropical cyclones bearing on the venue days out. Every active National Hurricane Center system is checked for proximity within a lead radius, surfacing the nearest storm, its category, and its distance. Unlike the same-day weather reads, this is built to show up on lead-up scans a week ahead.
A derived read — no new feed. It sizes the predicted heat-illness presentation load on medical: the heat band (WBGT) weighed against crowd size, exposure hours, and the receiving hospitals' emergency-department headroom — banded into a none/low/medium/high operational load so the crowd-medical plan matches the real exposure, not just "it's hot."
What's actually moving in the physical space around the venue — aircraft overhead, the drone airspace picture (no-fly zones, LAANC ceilings, stadium TFRs, and flight conditions), traffic on access roads, the health of the drive approaches, the egress terrain and how fast a crowd can clear, hostile-vehicle approach geometry, transit disruptions, flight restrictions and notices from the FAA, live emergency-services chatter, and cellular network health. These are the leading indicators that something has changed on the ground while the world was still posting about it. The count is of scored signals; the two drone map layers below are visualizations of the FAA drone source, not separate scored reads.
Live aircraft positions over the venue — helicopters circling, low-altitude overflights, aircraft squawking emergency codes, persistent loitering. We don't see consumer drones (those broadcast a different signal), but everything with a transponder shows up.
Active Temporary Flight Restrictions issued by the FAA near the venue. These get issued for VIP visits, protests, wildfires, hazards, and major sporting events. Often the first formal acknowledgement that an area is sensitive.
Notices to Airmen — the official FAA advisory layer that covers VIP movement notices (often issued BEFORE a TFR drops), drone / UAS activity, airshows, parachute ops, airspace restrictions, and runway closures. Every TFR is a NOTAM, but most NOTAMs aren't TFRs.
Live road incidents in a tight ring around the venue — accidents, road closures, jams, lane closures, road work, weather hazards. Filterable by category so you can isolate "just road closures" or "just accidents."
Public police / fire / EMS scanner feeds for the venue's county, sourced from Broadcastify. By default the card surfaces a click-through to the county feed listing — with an API key it enriches to a live feed list with listener counts.
Carrier coverage and network technology (5G / LTE / rural) at the venue coordinates. A weak or congestion-prone cell environment is an operational risk in its own right — radios, payment terminals, and incident-reporting apps all degrade when the network does.
Hostile-vehicle-mitigation mapping — the vehicle-as-weapon read on your perimeter. We derive a set of crowd points from the venue footprint, pull the drivable road network from OpenStreetMap, and for every approach compute three things: standoff distance to the crowd, the longest straight acceleration run, and the achievable impact speed. Each approach gets its own severity; a closure or barrier within the access point neutralises it.
Drive-time isochrones around the venue — the 5/10/15-minute reachable-area contours from the road network. We read the 10-minute area as a planning proxy for egress constraint: a small reachable area means roads choke the dispersal (water, mountains, a single arterial), a large one means the crowd can clear quickly in many directions.
Traffic-aware health of the drive approaches into and out of the venue. Where the Traffic signal reads point-incidents, this samples the four cardinal approaches ~6 km out, routes each into the venue with live traffic, and compares the live drive time and per-segment congestion against free-flow. The worst of the four approaches sets the band.
The physical egress terrain immediately around the venue — nearby water and rail barriers (chokepoints) and the surrounding road mix, through-arteries versus embedded service and lot roads. A static planning read: if you had to clear this venue, what does the ground around it look like?
Public-transit service disruptions near the venue — rail, subway, and bus suspensions, delays, and detours — read from agency GTFS-Realtime service-alert feeds where the venue falls inside a covered metro. Severity tracks the effect: a full line suspension reads higher than a minor delay.
How open the sky over the venue is to a drone, scored from the FAA no-fly zones and LAANC ceiling grid: OPEN SKY (drones legal to 400 ft), a capped ceiling, or PROTECTED (no-fly / 0 ft overhead). The single read on counter-drone exposure.
Whether a federal stadium Temporary Flight Restriction is in effect — the standing 14 CFR §99.7 ban on UAS within 3 nm and below 3,000 ft during major-league (NFL / MLB / NCAA / NASCAR) games. Matched by venue and league.
Whether a drone can physically fly over the venue right now — FLYABLE, MARGINAL, or GROUNDED — derived from live wind, gusts, precipitation, and visibility. Favorable weather enables drone ops; high wind or rain suppresses the threat.
The FAA's drone no-fly polygons near the venue — national security areas, prohibited zones, and special-use airspace where UAS are banned outright. Rendered as a toggleable layer on the map and flagged when the venue falls inside one.
The FAA UAS Facility Map — the LAANC ceiling grid that sets how high a drone may legally fly in each cell of controlled airspace, from 0 ft (no authorization) up to 400 ft. A toggleable map layer; the venue's containing cell drives the drone-airspace score.
The last-service cliff: tonight's final rail departures from stations near the venue, measured against the event's end time. Distinct from the live transit-disruption read — this reads the published timetable itself, an egress risk even on a perfectly healthy network. It scores the best nearby hub, since the crowd is only stranded when every hub's service has ended.
A derived read — no new feed. It fuses the egress inputs the movement pillar already holds — the last-service cliff, transit disruptions, road incidents, and weather in effect — into one end-of-night stranding and compression index for getting the crowd out.
A derived, predicted crowd-movement window — no new feed. It flags the density spike as the crowd surges toward the main stage at the headliner set change and disperses afterward. There's no per-act lineup schema yet, so v1 derives the window from the event window (headliner modelled roughly two-thirds through) scaled by venue capacity. It never claims act-by-act precision.
The backdrop the rest of the signals get read against — federal advisories, baseline crime, active disaster declarations, grid and power status, how fast emergency services can reach you, and what else is happening around the venue commercially. Same chatter, same airspace, same weather reads differently in front of a different backdrop.
The current advisory from the Department of Homeland Security's National Terrorism Advisory System — the modern successor to the old color-coded threat level. Three tiers: Bulletin (informational), Elevated Alert, Imminent Alert. Most of the year there's no active advisory; when one is in effect we surface it as a banner above every brief.
The State Department's country travel advisory level (1–4) for the event's country, with the underlying advisory text. For international events it's a baseline read on the operating environment; when an advisory is active we surface it as a banner beneath the NTAS bulletin on the brief.
Annual violent and property crime rates for the venue's city compared to the national average. Not a real-time signal — a backdrop. Tells you whether you're operating in a low- or high-risk environment by default.
Federally-declared disasters currently in effect for the venue's state — Major Disaster, Emergency, and Fire Management Assistance declarations. Authoritative, county-deduplicated, and grouped by incident.
Counter-event detection — every ticketed concert, sports game, theater show, or family event within 10 miles of the venue in the days around your event. Includes sold-out status, venue capacity tier (large / medium / small), distance, and same-day overlap flag.
Points of interest within 500 m of the venue — bars, clubs, transit hubs, hotels, hospitals, police precincts, adjacent crowd magnets. Categorized so you can read crowd flow at a glance: lots of bars within 300 m = pre-event drinking cluster; transit hub within 200 m = ingress chokepoint.
How fast help can arrive. We find the nearest hospital, police station, and fire station around the venue and compute each one's free-flow drive ETA to the gate. A nearest hospital beyond 15 minutes reads High; the nearest PD or fire beyond 10 minutes reads Medium — the planning answer to "if something goes wrong, how long until help is here?"
Electrical-grid and utility outages near the venue — customers out, by county and utility, within range of the site. The source is provider-pluggable: a commercial county-granularity feed or free utility outage layers drop in by configuration, no code change. Until a source is wired for a deployment the card reports honestly as out of coverage rather than a false all-clear.
The receiving-hospital picture for the venue — nearest emergency departments with their trauma-center level and capability, the backbone of a casualty plan. Confirms where casualties actually go before an incident, not during one.
Region-level internet backbone health — major CDN, cloud, and BGP-routing status near the venue, drawn from public provider status pages and internet-outage observatories. A region-scale read, not a venue-specific one.
A predictive read on how hard the electric grid serving the venue is working — demand versus the day-ahead forecast and the recent peak for the venue's balancing authority (EIA Grid Monitor). Distinct from the Power outages signal: the leading indicator of strain before a brownout, not a realized outage.
Live health of the major ticketing and entry platforms, read from their public status pages — Universe (Ticketmaster), Ticket Tailor, Spektrix, Skiddle, Weezevent, extensible by configuration. A degraded component on the platform your tickets live on shows up here before the queue at the gate does.
A derived read — no new feed. It propagates confirmed Medium+ threats from prior stops of this event's tour forward as elevated context: the same protective subject or threat pattern following the same artist down the road. A Persona-synergy signal.
Geomagnetic-storm and solar-radio-blackout conditions from NOAA's Space Weather Prediction Center — the NOAA G/S/R scales plus the live planetary K-index. A geomagnetic storm quietly degrades GPS timing (show clocks, timecode, drone RTK positioning) and HF/UHF radio comms.
A derived composite — no new feed. It fuses the five signals that describe the operational and comms substrate a show runs on — Power outages, Power-grid stress, Internet/CDN, Cellular, and Space weather — into one "can we run the show and keep comms up?" index.
A derived read — no new feed. Every other signal reports what it found; this one reports what it stopped finding — sources that were succeeding and now fail this scan, and a normally-active chatter environment that has gone silent against its own baseline.
A derived read — no new feed. It scores this scan's per-signal readings against this venue's own history across prior scans. "Unusual for this venue" is a sharper question than "unusual anywhere" — a stadium that runs medium every night is normal; a quiet amphitheatre suddenly running medium is not.
A derived read — no new feed. It counts how many independent pillars carry a High+ signal in this scan, after tier caps. Independent sources agreeing is materially stronger evidence than any single chip — this makes that agreement an explicit, reviewable signal in its own right.
A derived advisory recommendation — no new feed. It maps the live posture band and the stop-relevant signals in this scan (crowd surge, hostile vehicle, flood, fire, lightning, structural wind, direct threat) onto the documented Code of Practice §5.3 show-stop matrix and frames the call — run, monitor, prepare-to-hold, or recommend a show-stop review — naming which decision class each firing factor argues for.
The 70+ signals above are raw data — what's true, where, and how recently. Two AI-generated panels sit on top of them and do something the data alone can't: tell you the story across the sources, and what to do about it. Both are produced in a single Claude Haiku 4.5 call after the scan finishes. The model sees a compacted version of every signal at once, with its severity scores and key metrics.
A 3–4 sentence narrative that reads all 70+ signals together and explains what's actually happening. It identifies the genuine concerns, the false alarms, and the connections between sources — for example, the active FEMA fire declaration plus a forecast wind shift plus a current AQI reading combining into one operational risk. Sits at the top of every brief and as the lead block on the PDF cover.
Two to four concrete next steps, each starting with a verb and referencing specific data from the brief. On a quiet day this collapses to a single line: "Continue routine monitoring; no action required." On a busy day it's a checklist a security lead can hand to the team. Sits below the Mastodon card on the FE and at the top of the Intelligence Summary section in the PDF.
The model sees a compact summary (severity scores, headline metrics, top items per source) — not the full payload. It is asked to use only the data given and never to invent specifics. If the AI service is unavailable or the API key is missing, both panels degrade silently — the rest of the brief still renders fine.
Any one of these signals lies if you read it alone. Social chatter is noisy. Crime baseline is stale. Weather can be a quiet day on a high-tension week. News lags. Aircraft circle for ordinary reasons. A single TFR could be a routine presidential-visit notice with no bearing on your event.
Together, they triangulate. Three of these flagging at the same time is a real signal. One flagging is something to watch. None flagging is what an actual quiet day looks like — and knowing the difference is the whole point.
Each scan rolls all 70+ signals into a single overall score, alongside the per-source detail so you can see exactly what's driving the number. If you disagree with the call, the reasoning is on the page; you can override it on the spot.