SEV4 — AdvisoryCLOSEDWeather✓ Corroborated · 4 sources16d ago

Flood Warning and Tornado Activity — San Antonio, TX — Contact-Center Operations at Risk

A Flood Warning (Sev 10) is active for San Antonio alongside confirmed tornado activity and heavy rainfall across South Texas, with an NWS tornado warning also issued for parts of the adjacent Texas Hill Country. San Antonio carries an exceptionally dense operations footprint — approximately 34,500 contact-center seats, 60,000 back-office seats, and 110,000 knowledge-worker seats — making any site-access or power-disruption event high-consequence. Operations leaders should monitor employee commute safety, assess site accessibility, activate remote-work contingencies, and watch for utility outages that could affect service-level delivery.

Impact Summary

A Flood Warning (Sev 10) is active for San Antonio alongside confirmed tornado activity and heavy rainfall across South Texas, with an NWS tornado warning also issued for parts of the adjacent Texas Hill Country. San Antonio carries an exceptionally dense operations footprint — approximately 34,500 contact-center seats, 60,000 back-office seats, and 110,000 knowledge-worker seats — making any site-access or power-disruption event high-consequence. Operations leaders should monitor employee commute safety, assess site accessibility, activate remote-work contingencies, and watch for utility outages that could affect service-level delivery.

Domain
Weather
Region
San Antonio, US, US
Opened By
watchkeeper
Jul 16, 2026, 01:30 AM UTC
Validated By
auto
Jul 16, 2026, 01:30 AM UTC
Event Cluster
1 event
OVIX Score
10.0
Closed
watchkeeper-auto(resolved)
Jul 16, 2026, 02:00 PM UTC

Timeline4

Incident openedby watchkeeperJul 16, 2026, 01:30 AM UTC
Declared from 1 signals. OVIX 10. News 2. BPO 3. High-confidence (auto).
Severity validatedby autoJul 16, 2026, 01:30 AM UTC
Auto-validated: SEV4 per policy.
Note addedby watchkeeperJul 16, 2026, 01:30 AM UTC
External corroboration: corroborated (4 sources via Exa). sa.gov, forecast.weather.gov, expressnews.com, ksat.com
Incident closedby watchkeeperJul 16, 2026, 02:00 PM UTC
Auto-closed: no new material events within 12h for this incident.

Evidence / Why this?

Traced to source — read-onlyUpdated Jul 16, 01:30 AM UTC
Why declareddeclareHybrid
Incident declaration (deterministic floor + LLM relevance gate + quality gates)v3
DECLARE when deterministicFloor AND (llm.declare OR acuteWeatherFloor OR geoExposureFloor) AND NOT aggregateTitle AND NOT footprintZero AND NOT cyberDeny, and no open same-domain incident merges it (see incident_dedup v1). footprintZero (Gate 1, agents-036) = cluster is geo-scoped (any real region) AND bpoScore=0 (resolved exposure negligible/unmatched) — suppresses declaration INCLUDING via acuteWeatherFloor; the event becomes a brief; logged stage=relevance decision=suppress with the exposure inputs. No national-significance escape hatch (revisit with data). cyberDeny (Gate 2, agents-036, domain=cyber only) = isNonCcCyberAsset OR isNonSpecificCyberHeadline over the cluster signal titles (the same asset-class check the Impact Engine gates at 0.15x) — hard deny, logged stage=relevance decision=deny. Additionally a cyber declaration at SEV2 requires active-exploitation/CX-nexus evidence matching /actively exploited|exploited in the wild|under active exploitation|known exploited|kev|ransomware|breach(ed|es)|outage/i in the CLUSTER’S OWN signal titles+messages (never domain-wide news context, never LLM output), else it caps at a brief. Replaces the disabled agents-009 cyberFloor (dead code removed). Geo honesty (agents-036): location_* comes from the declaring event’s own region (top-severity signal), never from a different max-exposure member; cyber declarations set location_* null (exposure cities live in affected_regions only). deterministicFloor = maxSeverity>=8 AND (newsScore>=1 OR bpoScore>=1 OR acuteWeatherFloor). acuteWeatherFloor = maxSeverity>=9 AND any signal is an acute severe-weather WARNING (tornado/severe-thunderstorm/flash-flood) — overrides the LLM footprint-based suppression but NOT the footprint gate. geoExposureFloor (agents-034) = domain in {geopolitical, financial, labor, supply_chain, travel, infrastructure, seismic, disaster, environmental, health} AND maxSeverity>=8 AND bpoScore>=3 (density_class high/very_high — a major member hub); implies footprintZero=false. Weather + cyber excluded. aggregateTitle (grab-bag "Multiple/Several/Various…") is refused (agents-019 §D). Asset-class deny (military/war-zone, WFM-37) suppresses earlier.
domain
weather
regions
["San Antonio"]
bpo score
3
news score
2
llm declare
yes
max severity
10
signal count
1
density class
high
llm rationale
Declare:true — active Flood Warning at Sev 10 with confirmed tornado in San Antonio directly threatens one of the highest-density WFM operations footprints in the dataset; this is a distinct acute event from the already-open 'Tornado Warning — Us South Central' incident given its specific San Antonio urban-core and flood dimension.
footprint zero
no
aggregate title
no
high confidence
yes
geo exposure floor
no
acute weather floor
no
deterministic floor
yes
exposure region label
San Antonio, US
model claude-sonnet-4-6 · prompt watchkeeper-declare-2026-06
Why SEV4SEV4score 4Deterministic
Incident severity level (SEV1–SEV4) at declarationv1
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). score = numeric SEV (1=most severe … 4); SEV3/SEV4 auto-validate, SEV1/SEV2 require human validation.
domain
weather
bpo score
3
news score
2
persistent
no
max severity
10
auto validated
yes
acute weather floor
no
Geo Provenance
Tierprecise
Sourcesignal_coords
Deterministic

Related Signals1

[San Antonio] weather 10.0 — Flood Warningsentinel16d ago

External Corroboration

✓ Corroborated · 4 sourcesChecked Jul 16, 2026, 01:30 AM UTC
City Responds to Tornado and Severe Weathersa.govJul 16, 2026, 12:18 AM UTCNational Weather Serviceforecast.weather.govJul 14, 2026, 01:30 AM UTCSeveral flash flood warnings active in South Texas. Here's where.expressnews.comJul 15, 2026, 01:20 PM UTCReported tornado touches down in northwest Bexar County; Damage at multiple businesses near The Rimksat.comJul 15, 2026, 01:12 PM UTC

Affected Regions

San Antonio