SEV3 — ElevatedCLOSEDWeather✓ Corroborated · 5 sources3d ago

Tornado Warning — Us Southeast

Active Tornado Warning and Tornado Watch are in effect across the US Southeast, a region hosting approximately 986,000 contact-center seats, 2.5 million back-office seats, and 4.9 million knowledge-worker seats across major hubs including Miami-Fort Lauderdale, Houston, and the DC-Virginia corridor. Tornado warnings represent an imminent life-safety threat that can force immediate site evacuations, disrupt power and communications infrastructure, and cause unplanned staffing absences across affected facilities. Operations leaders should activate site safety protocols, assess real-time shelter-in-place or evacuation postures at impacted locations, and prepare contingency routing plans to redistribute volume to unaffected sites.

Impact Summary

Active Tornado Warning and Tornado Watch are in effect across the US Southeast, a region hosting approximately 986,000 contact-center seats, 2.5 million back-office seats, and 4.9 million knowledge-worker seats across major hubs including Miami-Fort Lauderdale, Houston, and the DC-Virginia corridor. Tornado warnings represent an imminent life-safety threat that can force immediate site evacuations, disrupt power and communications infrastructure, and cause unplanned staffing absences across affected facilities. Operations leaders should activate site safety protocols, assess real-time shelter-in-place or evacuation postures at impacted locations, and prepare contingency routing plans to redistribute volume to unaffected sites.

Domain
Weather
Region
US South, US
Opened By
watchkeeper
Jul 28, 2026, 09:00 PM UTC
Validated By
auto
Jul 28, 2026, 09:00 PM UTC
Event Cluster
7 events
OVIX Score
10.0
Closed
foreman(resolved/transient-warning-expired-v1 (FOREMAN 2026-07-30))
Jul 30, 2026, 03:09 AM UTC

Timeline8

Incident openedby watchkeeperJul 28, 2026, 09:00 PM UTC
Declared from 2 signals. OVIX 10. News 3. BPO 3. Acute severe-weather floor (agents-028): authoritative short-fuse warning, declared at SEV3 regardless of resolved BPO footprint.
Severity validatedby autoJul 28, 2026, 09:00 PM UTC
Auto-validated: SEV3 per policy.
Note addedby watchkeeperJul 28, 2026, 09:00 PM UTC
External corroboration: corroborated (5 sources via Exa). patch.com, wsls.com, jsonline.com, wtmj.com, yahoo.com
Note addedby watchkeeperJul 28, 2026, 09:30 PM UTC
Merged new cluster (2 signals, OVIX 10, regions Us Southeast) — same underlying episode. Weather episode tornado:us/south — merged across provinces (agents-036 Gate 3, <7d window). Re-emission of already-tracked events only — material clock NOT advanced (agents-046 G5, quiet clock continues toward close).
Note addedby watchkeeperJul 29, 2026, 12:00 AM UTC
Merged new cluster (1 signals, OVIX 10, regions Us Southeast) — same underlying episode. Weather episode tornado:us/south — merged across provinces (agents-036 Gate 3, <7d window). Re-emission of already-tracked events only — material clock NOT advanced (agents-046 G5, quiet clock continues toward close).
Note addedby watchkeeperJul 29, 2026, 12:30 AM UTC
Merged new cluster (1 signals, OVIX 10, regions Us Southeast) — same underlying episode. Weather episode tornado:us/south — merged across provinces (agents-036 Gate 3, <7d window). Re-emission of already-tracked events only — material clock NOT advanced (agents-046 G5, quiet clock continues toward close).
Note addedby watchkeeperJul 29, 2026, 03:30 AM UTC
Merged new cluster (1 signals, OVIX 10, regions Us Southeast) — same underlying episode. Weather episode tornado:us/south — merged across provinces (agents-036 Gate 3, <7d window). Re-emission of already-tracked events only — material clock NOT advanced (agents-046 G5, quiet clock continues toward close).
Note addedby watchkeeperJul 29, 2026, 04:00 AM UTC
Merged new cluster (1 signals, OVIX 10, regions Us Southeast) — same underlying episode. Weather episode tornado:us/south — merged across provinces (agents-036 Gate 3, <7d window). Re-emission of already-tracked events only — material clock NOT advanced (agents-046 G5, quiet clock continues toward close).

Evidence / Why this?

Traced to source — read-onlyUpdated Jul 29, 04:00 AM UTC
Why declaredmergeDeterministic
Incident dedup / merge keys (entity, episode, network, region+title)v4
Checked in order against open same-domain incidents (never an aggregate-titled bucket): (1) ENTITY key, region-independent, incident active <14d (updated_at): shared CVE id, OR (cyber) >=2 shared distinctive vendor/product tokens (1 suffices when it carries a digit, i.e. a product model), OR (travel, agents-039) same travel operator/system key (travelSystemKey — airline/ATC/GDS/rail identity with a disruption cue), OR same network/AS key (agents-022). (2) EPISODE key (weather/environmental/disaster + travel per agents-039 + environmental air-quality per agents-040), incident active <7d: same hazard family (weather: heat/tornado/flood/cyclone/winter/wildfire/storm; travel: strike/ground_stop/airspace/it_outage/transit; environmental air-quality: air_quality/smoke — a multi-day wildfire-smoke wave, split cleanly from the weather wildfire FIRE family) AND same macro-region (eu | us/<census region> | country code) — a multi-day strike series, rolling ground stop, or smoke wave refreshes ONE incident, not dailies. (3) Legacy region-overlap + title-word dedup, active <24h (v5 unchanged). Merge unions affected_regions + related_signal_ids + material_event_keys, bumps event_count, renders the merged regions into the description ("Affected regions:" trailer), logs stage=declare decision=merge (engine deterministic), and unions the evidence projection’s signal sources. agents-046 (v4): a merge advances the material clock (last_material_event_at) ONLY when it brings GENUINELY-NEW material event keys (newMaterialKeys over the incident's material_event_keys, agents-010 Fault B) — an EVOLVING situation. Re-emission / continued press coverage of already-tracked events accumulates ids/regions/event_count but HOLDS the material clock (agents-019 §C), so a wallpaper advisory's quiet clock can finally elapse toward close. This is the evolving-vs-wallpaper discriminator the earned-rights lifecycle backstop (incident_lifecycle v1) reads.
key
tornado:us/south
via
episode
domain
weather
regions
["Us Southeast"]
signal ids
[35418]
max severity
10
union regions
["Us Southeast"]
incident age h
0
new material keys
0
material clock advanced
no
Why SEV3SEV3score 3Deterministic
Incident severity level (SEV1–SEV4) at declarationv5
agents-043 (v4): a Gate A workforce-footprint declaration (geoExposureFloor) is scored on VALUE = magnitude × footprint via workforceFootprintSeverity, NOT the base mapSevLevel: catastrophic (sev>=9) × MAJOR hub (bpo>=3) → SEV1 (the Manila 7.0-quake worked example — this deliberately supersedes the single-event cap per ALERTING-PHILOSOPHY.md / Ted's criteria); sev>=9 × moderate hub (bpo==2) → SEV2; sev>=8 × bpo>=2 → SEV3. SEV1/SEV2 remain human-gated at declaration (validation pending). Every other path keeps the base mapSevLevel below unchanged. agents-046 (v5): the named-tropical-system active-threat arm (workforceFootprintSeverity tropicalActiveThreat, sev 7–7.99 × bpo>=2) → SEV3 — a tracked storm approaching a footprint coast is a genuine 0–72h disruption a WFM leader pre-positions for (same SEV3 honesty as the acute-severe-weather floor). The flag is a no-op for sev>=8 (those hit the higher branches), so hurricanes are unaffected. Base: SEV2 if sev>=9 AND news>=2 AND bpo>=1; else SEV3 if sev>=8 AND (news>=1 OR bpo>=1); else SEV4. Acute severe-weather (agents-028): if sev>=9 floor to SEV3 (SEV2→SEV3); minor/transient watches+advisories drop SEV2/SEV3→SEV4. Single-event cap: any SEV2 caps to SEV3 absent sustained multi-day BPO-region corroboration (SEV2 promotion is human-gated via revalidation). Systemic-travel floor (agents-039): a travelSystemicFloor declaration (multi-signal aggregate on member-relevant geography, sev 6-7 by design) floors SEV4→SEV3 — a region-level operational disruption, same honesty argument as the acute-weather SEV3 floor. It never raises anything to SEV2: SEV2 keeps its base intensity+news+human gating. Environmental air-quality floor (agents-040): an enviroAirQualityFloor declaration (multi-city cumulative air-quality/smoke aggregate on member-relevant geography, sev 6-7 by design) likewise floors SEV4→SEV3, and never raises anything to SEV2. score = numeric SEV (1=most severe … 4); SEV3/SEV4 auto-validate, SEV1/SEV2 require human validation.
domain
weather
bpo score
3
news score
3
persistent
no
max severity
10
auto validated
yes
acute weather floor
yes
travel systemic floor
no
Geo Provenance
Tierprecise
Sourcesignal_coords
Deterministic

Related Signals4

[Us Southeast] weather 10.0 — Tornado Warningsentinel3d ago[Us Southeast] weather 10.0 — Tornado Warningsentinel3d ago[Us Southeast] weather 10.0 — Tornado Warningsentinel3d ago[Us Southeast] weather 10.0 — Tornado Watchsentinel3d ago

External Corroboration

✓ Corroborated · 5 sourcesChecked Jul 28, 2026, 09:00 PM UTC
Tornado Warning Issued As Tornado Watch Covers NoVA, D.C. Region | Fredericksburg, VA Patchpatch.comJul 28, 2026, 08:45 PM UTCTornado warning expired for parts of Tazewell, Bland, Wythe Countieswsls.comJul 28, 2026, 07:28 PM UTCNWS issues tornado warning for Waukesha, Jefferson and Dodge countiesjsonline.comJul 27, 2026, 12:00 AM UTCTornado Warning issued for Waukesha, Jefferson and Dodge Counties - WTMJwtmj.comJul 27, 2026, 12:00 AM UTCTornado warning issued for severe storms in southeastern ...yahoo.comJul 27, 2026, 09:00 PM UTC

Affected Regions

Us Southeast