Author: William Tygart

Storm Updates: Gulf Coast Slight Flood, Quiet Severe Pulse — Saturday, October 3, 2026 (Morning)

This is the Saturday morning Storm Tracker desk for October 3, 2026. Overnight into this morning the organized severe window stayed closed. The Storm Prediction Center 1300 UTC Day 1 convective outlook, updated 8:16 a.m. CDT by Guyer and Dean and valid 1300 UTC Saturday through 1200 UTC Sunday, carries no severe thunderstorm areas. The summary line is short: severe thunderstorms are not expected across the U.S. through tonight.

These are county- and ZIP-scale leftovers and a coastal water board, not a mainland hurricane landfall. The live restoration ticket this morning is rain already aimed at the central Gulf Coast and the lower Texas coast, not a new convective watch. Conditions change fast. Verify with the National Weather Service for the specific county or ZIP before you roll.

What is live this morning

No convective watches are currently valid. SPC’s watch page, updated 12:35 UTC Saturday, lists none. The most recently issued watch is Severe Thunderstorm Watch 676, a Wednesday, September 30 product for west-central Texas. Nothing from Friday night carried into Saturday morning as a severe thunderstorm or tornado watch.

SPC local storm reports for the 1200 UTC Friday through 1159 UTC Saturday window, and for the new Saturday convective day that opened at 1200 UTC, show no tornado, hail, or wind reports received. The overnight severe hit list is empty. Pre-dawn thunderstorms were ongoing across the Dakotas ahead of a cold front, but the Day 1 discussion keeps severe potential virtually nil even if a stronger gust occurs this afternoon.

What is organized is water. The Weather Prediction Center Day 1 Excessive Rainfall Outlook, updated 0738 UTC Saturday and valid 12 UTC Saturday through 12 UTC Sunday, holds a Slight Risk of excessive rainfall for the central Gulf Coast and the lower Texas coast. Forecaster Wegman left the coastal Slight Risk in place and added a higher-end Slight Risk from New Orleans through much of the western Florida Panhandle, citing urban impacts and rainfall volume rather than a change in the underlying front.

Hotspot 1 — Central Gulf Coast

A tropical wave moving across the Gulf is funneling record to near-record atmospheric moisture into much of the Gulf Coast on Saturday. A 15 to 25 knot southerly flow at 850 mb supports numerous showers and thunderstorms moving into the central Gulf Coast today and tonight. Precipitable water is at or above 2.5 inches for many areas. Extensive cloud cover and the October sun should limit instability with any reasonable distance from the coast, so convection that hits the coast is not expected to travel far inland without significant weakening.

The coast can expect 3 to 6 inches of rain today, with locally higher amounts. Flash-flood guidance is high and soils have been dry, but WPC still flags widely scattered flash flooding where that volume lands on urban drainage, especially from New Orleans through the western Florida Panhandle. Mississippi and Alabama coastal counties sit in the same Slight Risk envelope.

Cities and counties to watch: New Orleans, the south shore and east bank parishes, coastal Mississippi from Hancock through Jackson County, Mobile and Baldwin counties in Alabama, and the western Florida Panhandle from Pensacola toward Panama City. Inland rows are a weaker pulse. The front that stretches from the Carolinas southwest toward the Texas coastal plain is the broader thunderstorm focus, but weak vertical shear and modest lapse rates should limit organized severe convection along and south of it.

Restoration read: water first, and only where a warning or a measured street flood actually verifies. Stage extractors, air movers, and moisture meters for urban low spots, underpasses, and slab-on-grade first floors. This is not a wind or hail board. Do not staff a regional roof crew on a Slight Risk of excessive rainfall. Photograph standing water only if the road is already closed and it is safe to be there.

Hotspot 2 — Lower Texas coast

The second Slight Risk remains along the coast of Deep South Texas. Onshore northeasterly flow of the same deep tropical moisture may reach urban areas such as Brownsville. Because this stretch of coast sits roughly perpendicular to the mean flow, WPC expects the onshore push to let convection move a few miles inland before it dissipates. No change was made to the area included in that Slight Risk on the 0738 UTC update.

Friday afternoon’s central Texas story is a different board. The prior desk held a Slight Risk of excessive rainfall on the I-35 corridor from Dallas–Fort Worth toward San Antonio, plus flood advisories in Comal, Guadalupe, and Hays counties and a flood watch that included coastal and inland Jackson County until early Friday evening. Those were time-limited products. They are not the Saturday morning Slight Risk. If a river or areal flood warning is still up in central or south-central Texas this morning, treat it as yesterday’s water still in the channel, not as a new convective watch.

Restoration read: Brownsville and the lower Texas coast are the new water ticket if cells train against the coast. Central Texas and southwest Kansas remain aftermath boards from Thursday and Friday. Do not send the same crew to both stories without checking which county actually has a warning now.

Northern Plains scatter, and what expired

Progressive westerlies cover the northern half of the country through tonight, with a fairly substantial shortwave trough amplifying over the northern Plains and Upper Midwest. As the cold front shifts east, a modest increase in moisture, steepening lapse rates, and increasing lift support isolated thunderstorms, including the pre-dawn activity across the Dakotas. SPC allows that some stronger, convectively enhanced wind gusts could occur this afternoon. Severe potential is expected to remain virtually nil. There is no Marginal, Slight, Enhanced, Moderate, or High Risk on the Day 1 categorical map.

Friday afternoon flash-flood warnings on the Georgia–Florida line, including Clinch and Echols counties in Georgia and Columbia County in Florida, were issued by National Weather Service Jacksonville with expiration times Friday evening. They are not a live Saturday morning warning. A separate river flood warning on the lower Fox River near New Munster, affecting Lake County, Illinois, and Kenosha County, Wisconsin, was continued Friday afternoon until Monday morning for minor flooding. That is a river-stage ticket, not a convective watch.

Tropics — not a U.S. land desk

National Hurricane Center Advisory 25 at 2:00 a.m. MST Saturday places Hurricane Rachel near 19.4°N, 111.8°W, about 270 miles south-southwest of the southern tip of Baja California, moving west at 5 mph, with maximum sustained winds of 90 mph and a minimum pressure of 969 mb. Rachel has weakened slightly and continues westward. There are no coastal watches or warnings in effect. A turn toward the west-northwest is expected today, with additional slow weakening. Swells will affect the coast of west-central Mexico and the Baja California Peninsula through the weekend and can produce life-threatening surf and rip currents. That is a marine hazard, not a U.S. landfall.

Hurricane Nolo is a Central Pacific system, near 23.3°N, 170.4°W at 2:00 a.m. HST, moving west at 13 mph with winds of 110 mph. It is not a U.S. mainland threat. The Atlantic basin has no tropical cyclones this morning. The Gulf Coast rain is tied to a tropical wave and deep moisture, not to a named storm making landfall.

Pulse table

Region	Main threats	SPC / WPC / NWS level	Status this morning
Central Gulf Coast (SE LA, coastal MS/AL, western FL Panhandle)	Heavy rain, urban flash flood	WPC Slight, higher-end on the coast	Live today and tonight; 3–6 inches, locally higher
Lower Texas coast (Brownsville)	Onshore heavy rain	WPC Slight	Live; cells may push a few miles inland
Northern Plains / Dakotas	Isolated storms, gusts	No severe area	Pre-dawn storms; severe potential virtually nil
Southeast / Deep South front	General thunderstorms	No severe area	Weak shear, modest lapse rates
Central Texas / southwest Kansas	Yesterday’s water	Aftermath, not a new watch	Verify any leftover flood warning before rolling
Fox River near New Munster	Minor river flood	Flood warning to Monday morning	River stage, not convective
U.S. mainland tropics	None	Rachel west of Baja; no coastal warnings	Swells and rip currents in Mexico only

What this means for restoration teams

There is no wind-driven roof board on the Day 1 outlook. A 3-to-6-inch coastal rain is wet drywall, flooring, and a 24-to-48-hour mold clock only where water actually enters. High flash-flood guidance and dry soils mean many miles of the Slight Risk will not produce a claim. Staff the warning, not the polygon. Urban New Orleans through the western Florida Panhandle is the higher-end piece of the same Slight Risk because of drainage, not because a watch is up.

Southwest Kansas and central Texas are still yesterday’s water if a flood statement is still valid. Friday’s flash-flood emergency language in Ford County and the I-35 flood advisories do not automatically roll into Saturday. Check the office product before a crew leaves the yard. The empty SPC report page means there is no new hail or tornado survey from overnight.

Next check

The next Day 1 convective outlook is scheduled by 1630 UTC. Day 3, valid Monday, also carries no severe thunderstorm areas, with the more robust low-level moisture staying on the Gulf Coast and winds aloft remaining weak. The afternoon desk should re-read the WPC Slight Risk and any new flood warnings on the central Gulf Coast before treating the morning polygon as still live.

Sources and how to verify

Primary sources: NOAA Storm Prediction Center 1300 UTC Day 1 Convective Outlook for Saturday, October 3, 2026; SPC current watches (none valid; last issued watch 676); SPC storm reports for October 2 and October 3 (no tornado, hail, or wind reports received); Weather Prediction Center Day 1 Excessive Rainfall Outlook, updated 0738 UTC Saturday; National Weather Service watches, warnings, and advisories summary; National Hurricane Center Advisory 25 on Hurricane Rachel, 2:00 a.m. MST Saturday. Prior desk: Storm Updates: Central Texas Slight Flood, Kansas Water — Friday, October 2, 2026.

Disclaimer: This is a morning desk summary of public National Weather Service, Storm Prediction Center, Weather Prediction Center, and National Hurricane Center products. It is not a warning, not a forecast for a specific address, and not a substitute for local NWS products. Watches and warnings expire and get replaced. Confirm the county or ZIP on weather.gov before travel or work.

October 3, 2026

The night job mailed six empty CSVs

The useful failure this week was not a downed site. The cluster answered 200. The failure was a job that kept completing.

Every night the citation desk mailed six CSV attachments to the internal ops inbox. Every attachment was a header row. The run logged itself, marked the task unchanged, and went back to sleep. From the outside that looks like a report. From the inside it is a sign-in wall wearing a receipt.

The export that refused to invent numbers

Bing Webmaster Tools publishes an AI Performance gradesheet. The nightly job is supposed to pull that gradesheet for six cluster domains and hand the files to the desk that builds inventory, persona, and buyer one-pagers. It cannot. The environment that runs the job is not signed into Webmaster Tools. The download fails. The job does the one honest thing left: it writes a header-only stub and says so.

The receipts are boring, which is how you know they are real. September 25 through October 1, the same sentence, sometimes twice in a morning because the scheduler double-fired: six stub CSVs, Sign In wall, no fabricated numbers, status unchanged. October 1’s receipt is the cleanest version. Zero real downloads. Session not signed in. Attachment count still six.

I would rather have the empty file than a confident one. A stub cannot be quoted in a client note. A made-up citation count can. The patch that held is the refusal. The patch that did not land is the session. Nobody sat down in that environment and authenticated Webmaster Tools, so the one-pagers the work order actually wants are still blocked. The weekday Claude citation scan was correctly scoped away from this. It watches Anthropic hubs. It does not magically become a Bing login.

We already wrote the public version of this wall: the gradesheet exists, and the supported export path is a signed-in human. This week proved the corollary. If you automate the unsigned path, you do not get a gradesheet. You get a mailer that is punctual about having nothing.

The hang that has been a verify for six days

The Houston restoration property has a standing daily hang: health, redirects, interlink, verify. Since September 23 that hang has been a verify. The admin session the bot can reach greets the wrong account. The account that can write redirects is the one that says Howdy to the operator. Until that session is the one in the chair, the Redirection plugin does not get a new rule, and the bot is under orders not to assign itself the job and not to ping for it.

October 2 was day six of that skip. The receipt at about 8:21 AM Pacific is the whole story. The hubs answered 200 with a single H1: home, water, mold, fire, the storm restoration guide, the water guide. The short storm path 301’d, via the Redirection plugin, to the flood restoration URL, which also answered 200. Older full redirects held: the duplicate water guides, the hurricane aliases, the flood alias. The machine can see. It cannot hang.

What it cannot fix is still 404. /storm-damage-houston/ is parked until the right admin session and an explicit go, and the post IDs after 1538 stay untouched. The short /guide-2-2/ and /guide-2-3/ paths are still hard 404s, same as September 28, so they are not a new break. They are a break we have agreed to keep looking at. Site health itself is fine: WordPress 7.1.2, PHP 8.5.4. Four plugin updates are waiting and explicitly not hung, because they sit behind the same admin wall. Elementor, Elementor Pro, Microsoft Clarity, WP All Export. Four theme updates waiting beside them. A green health API next to a parked redirect is not a clean site. It is a site whose write path is a person.

Rank Math did not see the week

The Friday morning cluster scorecard, 7:45 UTC, found every live WordPress node up. That is the sentence that gets you in trouble, because up is not indexed.

On the agency site the public count moved from 3,372 to 3,376. Thursday shipped four posts, under the daily cap of five. Week 40 sat at 22 of 25 with Friday and Saturday still open. Rank Math’s index lastmod was still September 29 at 19:45 UTC. Inside post-sitemap1 the newest internal stamp was September 27 at 05:14 UTC. All 22 week-40 URLs were absent from the post sitemaps. The pages exist. The map the crawler is handed does not mention them. Draft counts could not even be read on that run: the cloud secret injected for the agency site is a 14-character stub, not an application password, so the desk stayed on the public REST API.

The restoration magazine moved 175 to 179, plus four on Thursday, week 40 at 15 of 25. Its sitemap is current. Its body is not. Three identical titles are still live on IDs 437, 445, and 451. Two flash-flood duplicates, 524 and 525, both return 200. The homepage still renders three H1s. A current sitemap full of duplicates is a different failure than a stale sitemap, and it is not the nicer one.

The coverage hub is the one that actually broke a rule we wrote down. Thursday it went from 66 posts to 102. Thirty-six in a day, against a daily cap of five and a weekly cap of 25. The dump landed in a window from about 17:01 to 20:29 UTC, in the CAT, reinsurance, workers-comp, and hard-soft market clusters. The scorecard’s proposed write, not applied, was freeze and triage: no more batch, human review for thin template copy, 410 the thinnest before a recrawl. That is the scaled-content fingerprint this operation already paid for once on the agency site. The desk did not publish, send, pay, or trash anything on that run. It wrote the receipt and stopped. Correct. Late.

What I would not repeat

I would not resolve a person by first name and send.

On October 1 the standing send gate failed twice. Outbound mail went to a same-first-name contact who is not the operator the draft was for. The rule had been written the day before: full name, address from the contact record, exact recipient and full draft shown, explicit approval, then send. Memory did not hold it. The task was reopened the same day. Guessing an address is now a stop, not a lookup. I am not putting the names or the addresses in a public post. The operational fact is enough. A first-name match is not an identity. An agent with a mailbox and a fuzzy memory will pick the wrong one, and it will do it twice if you only correct it in chat.

The coverage-hub dump is the same shape in a different pipe. A cap that lives in a scorecard and not in the publisher is a wish. Thirty-six posts is not a content strategy. It is a scheduler that was allowed to finish.

The patch that did land

Sonnet 5.5 shipped September 28. The pricing hubs did not need new URLs. The work order was a current-model identity patch: keep the slugs, bump Last verified to October 1, mark Sonnet 5.5 as the current Sonnet at the same $2 / $10 list rate, leave Sonnet 5 on the page as legacy. Seat prices, the Fable inclusion line, and the Code weekly allotment were out of scope on purpose. By the October 2 poll the live pricing hub already carried the October 1 verified date, and the reopen note was stale against the page. Closed. No new essay. That is the patch shape I want: a delta, a slug you already rank, a date a stranger can check.

GitHub this week did not carry the incidents. The org commits since September 25 are content adds on two public repos, plus a repair commit that labeled trade sketches as illustrative and pointed them at the live essay. No issues opened. No application-password or environment file in any of that, and none will be described here. The breaks were in Notion receipts and public HTTP, not in a pull request.

Still open

The Howdy wall is still open. Until the restoration admin session is the operator’s account, /storm-damage-houston/ stays 404, the short duplicate guides stay 404, and the plugin updates stay queued. The Bing session is the same kind of open. Header-only CSVs will keep arriving at 2 AM until a human signs the job in. Rank Math on the agency site still owes the week-40 URLs a sitemap line. The coverage hub still owes a triage, not another batch.

None of these need a new tool. They need a session that is allowed to write, a login that is actually logged in, and a publisher that can count to five.

October 2, 2026

Storm Updates: Central Texas Slight Flood, Kansas Water — Friday, October 2, 2026

This is the Friday afternoon Storm Tracker desk for October 2, 2026. The organized severe window is still closed. The Storm Prediction Center 2000 UTC Day 1 convective outlook, updated 2:54 p.m. CDT by Karstens and Thornton and valid 2000 UTC Friday through 1200 UTC Saturday, carries no severe thunderstorm areas. The 20Z update made no changes to the 1630 UTC package. The summary line is unchanged: severe thunderstorm potential should remain low through tonight.

What is organized this afternoon is water, not wind. The Weather Prediction Center Day 1 Excessive Rainfall Outlook, updated 11:56 a.m. EDT and valid 16 UTC Friday through 12 UTC Saturday, keeps a Slight Risk of excessive rainfall for portions of central Texas, focused on the I-35 corridor from the Dallas–Fort Worth metroplex toward San Antonio. Kansas is an aftermath board: river flood warnings and closed roads from Thursday’s rain, not a new convective watch. Restoration exposure is water first — urban runoff, low crossings, and saturated ground in central Texas, plus standing water and minor river flood in Kansas. Isolated gusty storms are possible on the Mid-Atlantic front. They are not a watch. Conditions change fast. Verify with the National Weather Service for the specific county or ZIP before you roll.

What is live this afternoon

No convective watches are currently valid. SPC’s watch page, updated 19:12 UTC Friday, lists none. The most recently issued watch is Severe Thunderstorm Watch 676, a Wednesday, September 30 product for west-central Texas. It is not a Friday product. No mesoscale discussions were in effect on the midday SPC board. Today’s preliminary local storm report board, covering 1200 UTC Friday through 1159 UTC Saturday, has received no tornado, hail, or wind reports as of this desk.

SPC’s 1630 UTC discussion, left in place at 20Z, puts an upper trough progressing east across the Northeast and Mid-Atlantic, with a surface cold front advancing east-southeast over those regions and the Southeast and southern Plains. Twelve-Z soundings ahead of the front from the Mid-Atlantic to the Southeast showed very poor lapse rates aloft, on the order of 4 to 5.5 C/km in the 700–500 mb layer. That limits instability and updraft strength. Locally gusty winds could still occur with low-topped showers and thunderstorms across the Mid-Atlantic where low- and mid-level west-southwesterly flow is modestly enhanced. Organized clusters capable of severe or damaging wind still look unlikely. Weaker flow across the Tennessee Valley and central Gulf Coast states limits organization, but marginally greater instability supports isolated to scattered thunderstorm coverage through the afternoon along and ahead of the front.

The flood overlay is the live product. WPC’s 16Z update trimmed the Slight Risk out of southern Oklahoma, where rates had eased and probabilities of exceeding flash-flood guidance dropped. The higher-end Slight across central and southern Texas stayed on track. A moist environment and low-level convergence near the front have supported slowly propagating, efficient rain from near Dallas toward the Rio Grande. The I-35 corridor from Dallas–Fort Worth to San Antonio remains the focal point. WPC noted a couple of additional inches already down this morning over areas with flash-flood guidance under half an inch per hour, with another 1 to 3 inches possible today. The Marginal Risk was trimmed on the eastern and northern Tennessee and Ohio Valley edges, where rain is mostly stratiform, and expanded east along the I-10 corridor to include the Jacksonville metro, where guidance shows 2 to 3 inches or more in a tropical air mass with daytime heating.

Hotspot 1 — Dallas–Fort Worth to San Antonio, the Slight

This is the afternoon staffing line. WPC’s previous discussion described the southern end of the front across Texas becoming a slow-moving warm front, with very moist southeasterly flow running into it and 2 to 4 inches already down along I-35 yesterday. The return of the front was expected to drop another 1 to 3 inches from San Antonio and Austin up to the Metroplex. Saturated soils and urban drainage are the reason the Slight stayed in place. Instability is limited, so instantaneous rates should not be extreme, but the slow front still allows training.

National Weather Service Austin/San Antonio issued a Flood Advisory at 2:25 p.m. CDT Friday for Comal, Guadalupe, and Hays counties, in effect until 5:30 p.m. CDT, for flooding caused by excessive rainfall. Farther east, a Flood Watch covering portions of south-central and southeast Texas, including coastal and inland Jackson County, remained in effect until 7 p.m. CDT. Over the prior 24 hours much of that watch area had seen 3 to 6 inches, with a swath of 6 to 8 inches or more from southwestern Montgomery County through western Harris County. The watch text allows embedded training rates of 2 to 4 inches per hour in a deep tropical air mass through this evening.

Restoration read: water, not wind. Extraction and content work in Bexar, Hays, Comal, and Guadalupe counties is a continuation of Thursday’s closed crossings plus whatever this afternoon’s advisory adds. Harris and Montgomery are the heavier 24-hour totals if crews are already in Houston. Do not treat a Flood Advisory as a Flash Flood Emergency. Do treat a flooded low crossing as closed. Turn around, don’t drown.

Hotspot 2 — Kansas water, after the emergency

Thursday’s Flash Flood Emergency for Dodge City and central Ford County expired Thursday evening. It is not a live warning this afternoon. What is still on the board is river and areal flood from rain already down. National Weather Service Goodland extended a Flood Warning at 8:18 a.m. MDT Friday for Greeley and Wichita counties in west-central Kansas until 3 p.m. MDT / 4 p.m. CDT. Emergency management reported multiple roads still flooded. Between 3 and 7 inches had fallen. No additional rainfall was expected. Locations named in the product include Leoti, Tribune, Horace, Selkirk, Lydia, and Marienthal.

National Weather Service Topeka, in a 1:33 p.m. CDT Friday flood statement, extended a Flood Warning for the Solomon River near Glasco until Sunday evening. At 12:47 p.m. CDT the stage was 21.8 feet, with minor lowland flooding described along the river from the Cloud and Mitchell county line toward Niles at 22 feet. Separate Topeka products continued minor flooding on the Little Blue River near Barnes, affecting Marshall and Washington counties, and on the Black Vermillion and Big Blue in Marshall County. Kansas City/Pleasant Hill extended minor flooding on the Missouri River, including St. Joseph, Glasgow, Napoleon, Waverly, Leavenworth, Miami, and Boonville, into the weekend. Lowland flooding, not a convective watch, is the language.

Restoration read: Thursday’s Ford, Geary, Riley, McPherson, and Marion water is still a drying clock if it got inside. Friday’s live Kansas product is closed roads in Greeley and Wichita counties through mid-afternoon, and minor river flood into Saturday and Sunday. Photograph only if it is safe. Do not restaff a Flash Flood Emergency that expired Thursday.

Hotspot 3 — Mid-Atlantic gusts below a risk area

The cold front reaches the coastal Northeast and Mid-Atlantic by this evening and otherwise crosses the Tennessee Valley and lower Mississippi Valley. SPC still allows a couple of stronger storms with gusty winds near and ahead of the front in the Mid-Atlantic if there is enough sun, and isolated to scattered thunderstorms along the front into the Tennessee Valley and central Gulf Coast. Poor lapse rates are why the categorical map stays blank. It is not a Slight Risk and it is not a watch.

Restoration read: isolated tree and service-drop work is possible from the Cumberland Plateau into the Delmarva if a cell gusts. Do not stage a regional wind event on a no-risk outlook. Gulf Coast storms this afternoon are a rain check under the expanded Marginal, not a severe board.

Just hit

Today’s 12Z-cycle LSR board is empty: no tornado, hail, or wind reports received. The damage that already looks like a ticket is Thursday’s water, still visible in Friday flood products. Dodge City’s catastrophic flash-flood language expired Thursday. Goodland’s Friday morning warning is roads still closed in Greeley and Wichita counties after 3 to 7 inches. Austin/San Antonio’s Thursday warning for northern Atascosa, Bexar, and western Wilson counties, with emergency management reporting numerous low-water crossings closed in San Antonio and neighboring towns, also expired Thursday evening. Friday afternoon adds the Hays–Comal–Guadalupe advisory and the Harris–Montgomery watch totals of 6 to 8 inches or more in the wettest swath.

National Hurricane Center, 2:00 p.m. MST Friday: Hurricane Rachel was near 19.3°N, 111.1°W, moving west at 5 mph, minimum pressure 963 mb, still affecting Socorro Island and moving slowly westward, south of Baja California. That is not a U.S. landfall. The Atlantic basin has no tropical cyclones on the 2:00 p.m. EDT Friday outlook. Hurricane Nolo, in the Central Pacific near 23.3°N, 167.8°W, was moving west at 6 mph with maximum sustained winds near 75 mph on the 11:00 a.m. HST advisory. None of those is a mainland restoration staffing problem this afternoon.

Pulse table

Region	Main threats	SPC / NWS / WPC level	Status this afternoon
Dallas–Fort Worth to San Antonio, I-35	Training rain, urban runoff, 1–3 in more possible	WPC Day 1 Slight excessive rainfall	Live flood pulse
Hays, Comal, Guadalupe counties, TX	Excessive rainfall flooding	Flood Advisory until 5:30 p.m. CDT	Live through late afternoon
Harris / Montgomery / Jackson, TX	3–8 in already; training rates possible	Flood Watch until 7 p.m. CDT	Live through early evening
Greeley and Wichita counties, KS	Roads closed; 3–7 in already	Flood Warning until 4 p.m. CDT	Aftermath; no more rain expected
Solomon, Little Blue, Missouri River	Minor lowland river flood	Flood Warnings into the weekend	River, not convective
Mid-Atlantic / Cumberland Plateau	Isolated gusty storms	SPC Day 1: no severe areas	Possible; not organized
CONUS severe watches	None	No watches valid; WW 676 is Wednesday	Quiet
Atlantic / Rachel / Nolo vs. U.S. mainland	No landfalling cyclone	Rachel near Socorro Island; Atlantic empty; Nolo moving west	Quiet on the mainland coast

What this means for restoration teams

A blank Day 1 severe map is not a blank work board. The live call this afternoon is the Texas Slight: I-35 from the Metroplex to San Antonio, the Hays–Comal–Guadalupe advisory, and the Harris–Montgomery watch totals. Water inside a building from Thursday’s Bexar County warning is still a same-cycle extraction and a 24–48 hour mold clock. New water this afternoon starts a new clock only where it actually got in.

For teams in Ford, Geary, Riley, Greeley, or Wichita counties in Kansas: the convective warnings are expired. Work the water that is already in, and treat closed roads in west-central Kansas as still closed through the Goodland warning window. For teams on the Delmarva and the Cumberland Plateau: a couple of gusty storms are possible later today, below watch criteria. Do not staff Houston and Dodge City as the same event.

What this is not

This is not a severe-thunderstorm watch day, not a derecho, and not a U.S. mainland hurricane landfall. SPC Day 2, issued 10:58 p.m. CDT Thursday and valid 12Z Saturday through 12Z Sunday, also has no severe thunderstorm areas. Saturday’s summary: no severe thunderstorms are expected across the U.S. Rachel is an eastern Pacific hurricane near Socorro Island, moving west, not a Gulf or Atlantic landfall. Nolo is a Central Pacific hurricane moving west. The Atlantic basin is empty.

Looking ahead

The next Day 1 convective outlook is scheduled by 0100 UTC. If the Mid-Atlantic front produces a stronger storm, it will show up as a local warning or a special weather statement, not as a categorical risk area on the current package. The Texas Slight runs through 12 UTC Saturday. Kansas river flood warnings already extend into Saturday night and Sunday evening on several points. Saturday’s convective outlook remains a no-severe map. The flood story does not.

Sources and how to verify

Primary sources: NOAA Storm Prediction Center 2000 UTC Day 1 Convective Outlook for Friday, October 2, 2026, and the 0600 UTC Day 2 outlook; SPC current watches (none valid as of 19:12 UTC; last issued Watch 676); SPC preliminary storm reports for October 2 (none received); Weather Prediction Center Day 1 Excessive Rainfall Outlook updated 1556 UTC Friday, valid 16 UTC Friday through 12 UTC Saturday; National Weather Service warning text for Austin/San Antonio, Goodland, Topeka, and Kansas City/Pleasant Hill on Friday; National Hurricane Center Hurricane Rachel and Hurricane Nolo advisories and the Atlantic tropical weather outlook.

Check weather.gov for the county warning, spc.noaa.gov for the outlook, watches, and LSRs, and WPC excessive rainfall for the flood overlay. Morning desk for this calendar day: Friday, October 2 morning storm updates.

Informational only — not an official weather warning. Follow local authorities and the National Weather Service. Turn around, don’t drown.

October 2, 2026

The Best Delay Product Reads the Itinerary Against the Code
The airline already has a code for the delay. The passenger still has a screenshot and a hotel receipt that may not match it. That gap is the product.

The idea mills keep minting a flight chatbot, a claim-letter filler, and a delaycheck.ai. Three names. One object. A line on an itinerary that does not sit next to the cause code the carrier will report, or next to the commitment the carrier already posted.

Greg Isenberg’s stream and the daily micro-SaaS accounts keep splitting the same reader. One post wants a refund radar for merchants. Another wants a photo upload that becomes a manufactured part. A third wants a waitlist text when a slot cancels. Useful pieces. None of them join the boarding pass the traveler already holds to the public file the Department of Transportation already keeps.

The code is not the promise

Most travelers treat a delay as weather. The app says late. The gate agent says maintenance. The email says we are sorry. A hotel charge lands on the card. A week later the cause is a letter in a Bureau of Transportation Statistics file the passenger will never open.

That letter decides two different rights, and the mills keep collapsing them into one slogan.

The first right is a refund. Under 14 CFR Part 260, a covered airline owes an automatic refund if it cancels the flight, or delays it three or more hours on a domestic itinerary or six or more hours on an international itinerary, and the passenger does not accept a rebooking or a voucher. The reason does not matter. The Department has said the refund rule is separate from how a carrier codes the cause.

The second right is care. A hotel, a meal, a rebooking on another carrier. Federal law does not generally require those. What the passenger can point at is the airline’s own customer-service plan, summarized on the Department’s Airline Customer Service Dashboard. Those commitments attach to disruptions the carrier codes as within its control.

Change the code and you change the hotel. You do not change the refund. The product is the join, not a chatbot that says “you may be owed compensation.”

Why this month, not last year

On September 3, 2026, the Department published a final rule amending 14 CFR Part 234. Federal Register citation 91 FR 56588. It takes effect October 19, 2026.

The rule creates a new reporting category, Section 511(b), for ten events named in the FAA Reauthorization Act of 2024. Carriers that report under Part 234 may no longer place those events in the Air Carrier category, the bucket reserved for causes within the airline’s control.

The ten are specific. Aircraft cleaning after a passenger’s death. Aircraft damage from extreme weather, debris, or sabotage. A baggage-system outage the carrier does not control. A cybersecurity attack. An unexpected government-system shutdown. Overheated brakes after an emergency stop. Unscheduled maintenance, including work driven by an airworthiness directive. An onboard medical emergency. Removal of an unruly passenger. An airport closure from volcanic ash, wind, or wind shear.

Some of those were already outside the old Air Carrier bucket. Maintenance, a medical emergency, removal of an unruly passenger, and overheated brakes were not. After October 19 they have a place to go that is not “we caused this.” Dashboard commitments that say “controllable delay” no longer reach them by default.

A crew timeout still sits in Air Carrier. Weather at the airport still does not. The interesting cases are the ones a gate screen can describe two ways. “Mechanical” can be a deferred item the carrier owns, or unscheduled maintenance the new category now holds. The passenger cannot see the code. The carrier can.

That is the shift. Not a vibe about travel being broken. A reporting rule with an effective date, a Federal Register page, and a dashboard the Department already told large carriers to honor.

Two primitives, one wedge

Primitive one is the photo and the paste. The mills have been shipping receipt readers for months. The input here is the thing already on the phone. Boarding pass. Itinerary email. The delay text. The hotel folio if one exists. Flight number. Date. Origin. Destination. Scheduled time. What the airline said.

Primitive two is the public file. The dashboard already lists what each reporting carrier promised for a controllable cancellation and a controllable delay. Part 260 already states the refund clock in hours. After October 19, Part 234 states which ten causes are not Air Carrier. BTS already publishes the cause file, late, by carrier and airport.

The wedge is not a platform. It is a check a stranger will run this week. Paste the itinerary. Photograph the boarding pass. Get back three lines.
- Refund clock. Did the delay cross three hours domestic or six hours international, and did the passenger refuse the rebooking. If yes, Part 260 does not care about the code.
- Care clock. What that carrier posted on the dashboard, and whether the words on the delay text look like Air Carrier or like one of the ten.
- Mismatch. The text said crew. The later code said maintenance. Or the text said mechanical and the code, when it posts, said Section 511(b).
Charge after the mismatch, or do not charge. A free first read is the whole top of the funnel. If you cannot get a stranger to paste one itinerary this week, you do not have a company. You have a policy thread.

The map is the company

The first hundred checks are a service. The ten thousandth is a dataset.

What compounds is not another dashboard of flight status. Flight status already exists. What compounds is the labeled join: stated reason, dashboard commitment, Part 260 threshold, and the cause code that later lands in the BTS file. Carrier. Airport. Hour. Whether the hotel was offered. Whether the refund arrived without a form.

That map has a buyer who is not the passenger. A corporate travel desk that wants to know which carriers’ “mechanical” texts become Section 511(b) codes. A card issuer that wants to know which hotel charges were care the carrier had already promised. A plaintiff’s shop that wants the pattern, not the anecdote. You do not sell them a login to a status page. You sell them the mismatch rate.

Month one is one carrier and one metro. Paste only. No accounts. Month two adds the hotel folio as a second document on the same record. Month three is the ugly internal scoreboard: flights, stated cause, coded cause, refund cleared or not. That scoreboard is the seed of the business sale. The consumer check stays free or cheap. The map is the price.

Models draft. People file.

A refund request to the airline can be a draft. A complaint to the Department’s aviation consumer site is a filing. So is a chargeback that says the carrier broke a posted commitment. So is any letter that asserts a legal right in the passenger’s name.

The model reads the itinerary and the dashboard. It marks the hours. It marks whether the words on the delay text sit in Air Carrier or in the ten. It drafts the paragraph. A person reads it and sends it. If the product sends the complaint on its own, it is not a checker. It is an unlicensed claims shop with a timer.

The same rule covers the edge cases. Unscheduled maintenance is not a slogan a model should swear to. The passenger does not have the maintenance log. The honest output is a label: the text is consistent with a 511(b) event, or it is not, and here is the commitment that applies if the carrier later codes it as Air Carrier. Uncertainty is a feature. False certainty is how the product gets the airline’s lawyer a free exhibit.

Why this cut, not the last one

The leakage essay was tariffs, seats, and subscriptions. The rebate essay was a nameplate. The recall essay was a label. The short-pay essay was a contractor packet. The bill essay was an EOB against a hospital file. The tax essay was a notice against the roll. The utility essay was a statement against a filed tariff. The housing essay was a unit against a score.

This one is the itinerary version of the same pair, with a clock. A document the traveler already has, plus a public commitment file the Department already forces onto a page, joined in the seventeen days before the new cause code goes live. After October 19 the same join still works. It just has a sharper wrong answer available to the carrier.

The noticing used to require a forum thread and a weekend. It now requires a model that can read a boarding pass and a person who will sign the complaint. Recovery still works because the first check costs the traveler almost nothing.

Someone will own the labeled map of stated cause versus coded cause. The mills will keep proposing a new .ai name for each airline PDF. Ignore the names. Join the line. Keep the map.

Will Tygart — Tygart Media.

This is the idea-mill series.
October 2, 2026

Storm Updates: Kansas Flood Aftermath, Quiet Severe Pulse — Friday, October 2, 2026 (Morning)

This is the Friday morning Storm Tracker desk for October 2, 2026. Overnight into this morning the organized severe window stayed closed. The Storm Prediction Center 1300 UTC Day 1 convective outlook, updated 7:36 a.m. CDT by Guyer and Dean and valid 1300 UTC Friday through 1200 UTC Saturday, carries no severe thunderstorm areas. The summary line is short: severe thunderstorm potential is low today and tonight.

These are county- and ZIP-scale leftovers, not a mainland hurricane landfall. The live restoration ticket is yesterday’s water still in streets, basements, and low crossings in southwest Kansas and south-central Texas, not a new watch. Conditions change fast. Verify with the National Weather Service for the specific county or ZIP before you roll.

What expired overnight, and what is still live

No convective watches are currently valid. SPC’s watch page, updated 11:17 UTC, lists none. The most recently issued watch is Severe Thunderstorm Watch 676, issued 5:10 p.m. CDT Wednesday, September 30, for west-central Texas from near Fort Stockton to east of Abilene. It expired at midnight CDT Wednesday. It is not a Friday product.

No mesoscale discussions are in effect. The most recent is MD 2345, issued 1:32 p.m. CDT Thursday for southwestern Kansas into far northwestern Oklahoma. Watch probability was 5 percent. A couple of severe gusts and perhaps a brief tornado were possible; a watch was not expected. That discussion has expired.

Thursday afternoon flood products have also expired. National Weather Service Dodge City issued a Flash Flood Emergency at 2:32 p.m. CDT for Dodge City and central Ford County, tagged catastrophic damage threat and a particularly dangerous situation, after 3 to 6 inches of rain with another 3 to 5 inches possible. That warning ran until 5:30 p.m. CDT. Separate Dodge City warnings covered southwestern Gray, southern Haskell, northwestern Meade, and northeastern Seward counties until 6:00 p.m. CDT, and northwestern Ford County until 5:15 p.m. CDT. Topeka warnings covered Geary and northwestern Morris until 7:00 p.m. CDT, including Interstate 70 between mile markers 291 and 302 and 310 and 315, and a continuation for Manhattan, Junction City, Wamego, and neighboring Riley, Pottawatomie, Nemaha, and Jackson counties until 5:00 p.m. CDT. Wichita covered northeastern McPherson and northwestern Marion until 8:00 p.m. CDT, considerable threat, with up to 3 inches already down and another 3 possible.

In Texas, Austin/San Antonio kept a Flash Flood Warning until 7:00 p.m. CDT for northern Atascosa, Bexar, and western Wilson counties. Emergency management reported flooding and numerous low-water crossings closed. San Antonio, Schertz, Converse, Pleasanton, Floresville, and neighboring towns were in the polygon. Between 1 and 4 inches had fallen. Shreveport covered northwestern Cherokee and central Smith counties, including Tyler and Jacksonville, until 6:30 p.m. CDT. None of those polygons are still in force this morning.

Hotspot 1 — Dodge City and central Kansas water, after the emergency

The morning desk is an aftermath desk. Dodge City and central Ford County took the highest language NWS uses for flash flooding: emergency, catastrophic, seek higher ground. Junction City, Manhattan, and the McPherson–Marion line were the second story, with I-70 in the Topeka polygon. SPC’s filtered report board for the 12Z Thursday to 12Z Friday window did not log a tornado or hail report. The only wind reports are two ASOS gusts at Garden City (KGCK), 3 miles northwest of Pierceville in Finney County: 58 mph at 1754 UTC and 59 mph at 1802 UTC. That is sub-severe on the usual 58 mph severe-wind threshold only by a mile of rounding, and it is not a damage survey.

Restoration read: water first. Extraction, drying, and content work in Ford County and along the I-70 corridor in Geary and Riley counties are already on the clock from Thursday afternoon, not from a Friday warning. Photograph standing water and closed crossings only if it is safe. Do not treat an expired emergency as a live warning, and do not treat an expired warning as a clean street.

Hotspot 2 — San Antonio and south Texas water, then a Saturday Gulf Coast slight

The Weather Prediction Center Day 1 excessive-rainfall product still posted on the public page this morning is the overnight update, issued 0036 UTC Friday and valid 01Z to 12Z Friday. That window has expired. It held a Moderate Risk of excessive rainfall across portions of the southern Plains, with the greatest rates in southern and central Texas and a broader excessive-rainfall threat north into the Plains, the southern Great Lakes, and the far western Ohio Valley. Earlier Thursday discussion kept the Moderate from South Texas toward southeast Oklahoma, with ensemble means of 3 to 6 inches from the Austin–San Antonio metro into South Texas and higher-end local maxima above 8 to 10 inches in the wettest scenarios. A Marginal covered the Florida east coast from Miami to the Space Coast for isolated urban rates over an inch an hour.

The next flood overlay already on the board is Day 2, updated 0749 UTC Friday and valid 12Z Saturday through 12Z Sunday. WPC has a Slight Risk of excessive rainfall for the central Gulf Coast. Broad southerly flow off the Gulf pumps tropical moisture north, with precipitable water expected to exceed 2.5 inches. The Slight was expanded west to include the Houston metro in coordination with the Houston forecast office. New Orleans, Biloxi, Mobile, and Pensacola sit in the same Saturday afternoon language. That is tomorrow’s staffing note, not this morning’s warning.

Restoration read: San Antonio and Bexar County are Thursday’s observed flood, closed crossings, and a 24–48 hour mold clock if water got inside. Houston and the central Gulf Coast are a Saturday watch-item if the Slight verifies. Do not send the same crew to both stories.

Hotspot 3 — Mid-Atlantic gusts that stay below a risk area

SPC’s Friday discussion puts a progressive stream of westerlies over the northern third of the country. An extensive cold front continues east-southeast, reaching the coastal Northeast and Mid-Atlantic by this evening and otherwise crossing the Tennessee Valley and lower Mississippi Valley. Scattered showers and thunderstorms accompany the front and stay common on the Gulf Coast and Southeast.

As the front approaches the coastal Mid-Atlantic and Delmarva later this evening, effective shear of 35 knots or more will exist, and to a lesser extent southwest toward the Appalachians and the Cumberland Plateau. A couple of stronger storms with gusty winds could materialize this afternoon near and ahead of the front if there is enough sun and modest destabilization. Moist-profile, subsidence-related poor lapse rates aloft should preclude organized severe storms. That is why the categorical map is blank. It is not a Slight Risk and it is not a watch.

Restoration read: isolated tree and service-drop work is possible from the Cumberland Plateau into the Delmarva if a cell gusts. Do not stage a regional wind event on a no-risk outlook.

Just hit

Today’s 12Z-cycle LSR board, covering 1200 UTC Friday through 1159 UTC Saturday, is empty: no tornado, hail, or wind reports received. The Thursday 12Z-to-12Z board is the Garden City pair only. The damage that already looks like a ticket is the flood language, not the LSR list: the Dodge City emergency, the Manhattan–Junction City observed flooding, and the San Antonio low-water crossings.

National Hurricane Center, 2:00 a.m. MST Friday advisory on Hurricane Rachel: the center was near 19.4°N, 110.4°W, moving west at 5 mph, maximum sustained winds 115 mph, minimum pressure 955 mb. Rachel has weakened slightly and turned westward, south of Baja California Sur. No coastal watches or warnings are in effect. The Atlantic basin has no tropical cyclones on the 8:00 a.m. EDT Friday outlook. Tropical Storm Nolo is a Central Pacific system, with tropical-storm conditions in the Papahānaumokuākea Marine National Monument. None of those is a mainland restoration staffing problem this morning.

Pulse table

Region	Main threats	SPC / NWS / WPC level	Status this morning
Dodge City / Ford County, KS	Flash-flood aftermath, 3–6 in already	Flash Flood Emergency expired 5:30 p.m. CDT Thu	Aftermath; not a live warning
Junction City, Manhattan, McPherson–Marion, KS	Training rain, I-70 crossings	Flash Flood Warnings expired Thu evening	Aftermath / drying clock
San Antonio / Bexar, Atascosa, Wilson	Observed flooding, closed crossings	Flash Flood Warning expired 7 p.m. CDT Thu	Aftermath
Garden City / Finney County, KS	58–59 mph ASOS gusts	SPC LSR only; no watch	Logged; no damage survey on the board
Coastal Mid-Atlantic / Delmarva / Cumberland Plateau	Isolated gusty storms	SPC Day 1: no severe areas	Possible this afternoon; not organized
Houston / central Gulf Coast	Heavy rain Saturday	WPC Day 2 Slight excessive rainfall	Tomorrow, not this morning
CONUS severe watches	None	No watches valid; WW 676 expired Wed midnight	Quiet
Atlantic / Rachel vs. U.S. mainland	No landfalling cyclone	Rachel west of Baja, no watches; Atlantic empty	Quiet on the mainland coast

What this means for restoration teams

A blank Day 1 severe map is not a blank work board. Thursday’s catastrophic flash-flood language in Dodge City and the considerable-threat polygons in central Kansas and Bexar County are the jobs already started. Water inside a building from a Thursday afternoon warning is still a same-cycle extraction and a 24–48 hour mold clock on Friday morning. The Garden City gusts are a local check, not a wind event.

For teams in Ford, Geary, Riley, McPherson, Marion, Bexar, Atascosa, or Wilson counties: confirm the warning has expired, then work the water that is already in. For teams on the Delmarva and the Cumberland Plateau: a couple of gusty storms are possible later today, below watch criteria. For Houston and the central Gulf Coast: Saturday’s Slight is the next flood overlay. Do not staff it as if it were live this morning.

What this is not

This is not a severe-thunderstorm watch day and not a U.S. mainland hurricane landfall. SPC Day 2, issued 10:58 p.m. CDT Thursday and valid 12Z Saturday through 12Z Sunday, also has no severe thunderstorm areas. Saturday’s summary: no severe thunderstorms are expected across the U.S. Isolated lightning is possible over the Upper Midwest with a shortwave, and scattered thunderstorms are expected on the Gulf Coast into the Carolinas with weak shear. The work this morning, if crews are rolling, is Thursday’s water.

Looking ahead

The next Day 1 convective outlook is scheduled by 1630 UTC. If the Mid-Atlantic front produces a stronger storm, it will show up as a local warning or a special weather statement, not as a categorical risk area on the current package. The flood story shifts toward the central Gulf Coast on Saturday under the WPC Day 2 Slight. Rachel stays an eastern Pacific system moving west, away from the Baja coast.

Sources and how to verify

Primary sources: NOAA Storm Prediction Center 1300 UTC Day 1 Convective Outlook for Friday, October 2, 2026, and the 0600 UTC Day 2 outlook; SPC current watches (none valid; last issued Watch 676) and current mesoscale discussions (none; last MD 2345); SPC preliminary storm reports for October 1 and October 2; Weather Prediction Center Day 1 Excessive Rainfall Outlook valid through 12Z Friday and Day 2 outlook updated 0749 UTC Friday; National Weather Service warning text for Dodge City, Topeka, Wichita, Austin/San Antonio, and Shreveport from Thursday afternoon; National Hurricane Center Hurricane Rachel Advisory 21 and the Atlantic tropical weather outlook.

Check weather.gov for the county warning, spc.noaa.gov for the outlook, watches, and LSRs, and WPC excessive rainfall for the flood overlay. Prior desk: Thursday, October 1 afternoon storm updates.

Informational only — not an official weather warning. Follow local authorities and the National Weather Service. Turn around, don’t drown.

October 2, 2026

Storm Updates: Kansas Flash Flood Emergency, Texas Water — Thursday, October 1, 2026

This is a live Thursday afternoon snapshot for October 1, 2026. The organized severe window is small. The Storm Prediction Center 2000 UTC Day 1 convective outlook, updated 2:49 p.m. CDT, holds a Marginal Risk only across parts of southern Kansas and northwest Oklahoma — about 16,457 square miles and roughly 121,676 people, with Liberal, Kansas, and Woodward, Oklahoma, named in the risk table. No severe thunderstorm watch number is attached to that outlook. The live ticket is water. The National Weather Service in Dodge City issued a Flash Flood Emergency at 2:32 p.m. CDT for Dodge City and central Ford County, tagged catastrophic damage threat, after 3 to 6 inches of rain with another 3 to 5 inches possible. Restoration exposure this afternoon is interior water, saturated streets, and a short gusty-wind tail on the High Plains — not a hail swath and not a tornado outbreak.

These are county-scale thunderstorms and training rain, not a U.S. landfalling hurricane. Hurricane Rachel is in the eastern Pacific, south of Baja California Sur, with no coastal watches or warnings in effect on the 2 a.m. MST advisory and a track taking the center away from mainland Mexico. The Atlantic basin has no tropical cyclones this afternoon. Conditions change fast. Verify the county warning at weather.gov before a crew rolls.

What is live this afternoon

SPC’s Day 1 update valid from 2000 UTC Thursday through 1200 UTC Friday puts a 5 percent wind probability and a 2 percent tornado probability on that southern Kansas and northwest Oklahoma Marginal. No hail risk area is drawn. Mesoscale Discussion 2345, issued 1:32 p.m. CDT, covers southwestern Kansas into far northwestern Oklahoma and rates watch issuance at 5 percent. The discussion notes several storms undercut by the front produced 40 to 50 knot gusts from Hamilton to Finney counties, and that a brief tornado is most plausible in the warm sector along the Kansas–Oklahoma border — too localized, in SPC’s words, to warrant a watch. Filtered storm reports from 1200 UTC today show no tornado reports and no hail reports. Two wind reports landed near Garden City: 58 mph and 59 mph, 3 miles northwest of Pierceville in Finney County, from the Garden City ASOS at 12:54 p.m. and 1:02 p.m. CDT.

The Weather Prediction Center Day 1 excessive-rainfall point file issued 3:26 p.m. EDT, valid 1927 UTC Thursday through 12 UTC Friday, keeps a Moderate Risk of rainfall exceeding flash-flood guidance on a swath the point string ties through southwest and north Texas — Uvalde, Fort Worth Spinks, McKinney, Paris — and east toward the southern Appalachians near Morristown, Tennessee. A Slight Risk covers a broader corridor from the central Plains, including Hill City and Manhattan, Kansas, Falls City, Nebraska, and Lamoni and Iowa City, Iowa, into the Midwest fringe. A separate Marginal pocket sits over South Florida. The overnight Moderate discussion that was valid only through 12 UTC Thursday has expired; the afternoon product is the one above, and the warnings below are what is actually in effect.

Hotspot 1 — Dodge City and southwest to central Kansas

This is the live emergency. NWS Dodge City’s 2:32 p.m. CDT Flash Flood Warning for central Ford County runs until 5:30 p.m. CDT and includes the Flash Flood Emergency language for Dodge City, Ford, Fort Dodge, and Wright. Source is emergency management. Damage threat is catastrophic. A separate Dodge City warning covers southwestern Gray, southern Haskell, northwestern Meade, and northeastern Seward counties until 6:00 p.m. CDT, including Sublette and Copeland, after 1 to 3 inches with another half inch to an inch possible. Farther east, NWS Wichita has a Flash Flood Warning until 8:00 p.m. CDT for northeastern McPherson and northwestern Marion counties, including Canton, Lehigh, and Roxbury, with up to 3 inches already down and another 3 inches possible; damage threat considerable. NWS Topeka has a warning until 7:00 p.m. CDT for Geary and northwestern Morris counties after 3 to 5 inches, including Junction City and Grandview Plaza and Interstate 70 between mile markers 291 and 302 and 310 and 315. An earlier Topeka statement kept flooding in play for Manhattan, Wamego, and the Milford and Tuttle Creek lake areas.

Restoration read: this is a water ticket already open, not a forecast. Extraction, contents, and a mold clock start where water entered finished space. Do not route a crew across a closed low-water crossing to reach the loss. Wind is secondary here — the Garden City gusts are a roof-and-tree check, not the headline.

Hotspot 2 — San Antonio metro and northeast Texas

NWS Austin/San Antonio kept a Flash Flood Warning in effect until 7:00 p.m. CDT for northern Atascosa, Bexar, and western Wilson counties. At 3:23 p.m. CDT, emergency management reported flash flooding with numerous low-water crossings closed. Leon and Olmos creeks had responded. One to 4 inches had fallen, with up to another inch possible. Damage threat is considerable. Locations in the warning text include San Antonio, Schertz, Converse, Universal City, Live Oak, Pleasanton, Floresville, Helotes, and Randolph AFB. NWS Shreveport issued a Flash Flood Warning at 3:23 p.m. CDT until 6:30 p.m. CDT for northwestern Cherokee and central Smith counties, including Tyler, Jacksonville, Whitehouse, and Lindale, with 1 to 2 inches down and rates of 1 to 2 inches per hour expected.

SPC’s 2000 UTC update also notes convective coverage increasing over south-central and south Texas in hot, humid air. A localized strong gust is possible with the strongest downdrafts. Poor mid-level lapse rates and weakening shear keep that below a broader severe risk. Restoration read: San Antonio is observed water and closed crossings. Tyler is a radar-indicated flood warning with a short fuse. Treat both as urban-drainage and creek jobs, not as a severe-wind corridor.

Hotspot 3 — Southern Kansas and northwest Oklahoma Marginal

The only categorical severe area on the afternoon Day 1 outlook is the trimmed Marginal from southern Kansas into northwest Oklahoma, centered on Liberal and Woodward. The 11:28 a.m. CDT discussion, still carried as the previous discussion on the 2000 UTC product, describes a weak surface low over northwest Oklahoma and the northeast Texas Panhandle, a front northeast across Kansas, and a Pacific cold front south across the southern Plains. Cool temperatures aloft, around minus 10 to minus 11 C at 500 mb, can support small hail, strong to locally severe winds, and perhaps a brief tornado until the cold front undercuts the storms by late afternoon or early evening. SPC trimmed the northwestern edge of the Marginal where severe probabilities dropped behind ongoing convection.

A low-probability isolated storm is also noted along the surface front in northeastern Missouri and western Illinois later this afternoon or evening. Poor lapse rates and limited buoyancy keep severity muted if anything develops. Restoration read: stage a small wind-and-tree check for Liberal, Woodward, and the Kansas–Oklahoma border counties. Do not staff it like a watch.

Just hit

The overnight story is already a ticket, not a new outlook. The 0100 UTC Day 1 outlook from Wednesday evening had carried a Slight Risk from Texas into southwest Oklahoma and over north-central Kansas, with a tornado window noted for the next hour or two mainly in north-central and northeast Kansas. Today’s 12Z-onward SPC filtered page does not list a tornado or hail report. What verified into this afternoon is rain: Dodge City’s 3 to 6 inches, Junction City’s 3 to 5 inches, and San Antonio’s closed crossings. The morning Storm Tracker desk is the prior URL for that overnight close-out.

Pulse table

Region	Main threats	SPC / NWS level	Status this afternoon
Dodge City / Ford County, KS	Life-threatening flash flood, 3–6 in already	Flash Flood Emergency, catastrophic	Live until 5:30 p.m. CDT
Junction City, Manhattan, McPherson–Marion, KS	Flash flood, training rain, I-70	Flash Flood Warnings	Live into evening
San Antonio / Bexar, Atascosa, Wilson	Observed flooding, closed crossings	Flash Flood Warning, considerable	Live until 7 p.m. CDT
Tyler / Smith and Cherokee counties, TX	Heavy rain, urban drainage	Flash Flood Warning	Live until 6:30 p.m. CDT
Southern KS / northwest OK	Gusty wind, brief tornado possible	SPC Marginal; MD 2345, watch unlikely	No watch number
Atlantic / U.S. mainland tropics	No landfalling cyclone	NHC: no Atlantic cyclones	Quiet on the U.S. coast

What this means for restoration teams

Ford County is the priority desk. A catastrophic Flash Flood Emergency means finished-floor water, contents, and electrical in low structures are already in play where the water reached them. Photograph only from safe ground. The San Antonio warning is the second water desk: crossings are closed, so access is the constraint, not the estimate. Tyler is a shorter fuse on the same rain axis. The Marginal in Liberal and Woodward is a gust check — the only filtered wind reports so far are the 58 and 59 mph Garden City readings. A 60 mph peak is the most probable gust in MD 2345’s language, which is roof edge, fascia, and tree-on-structure work if it verifies, not a regional tarp campaign.

Do not send the same crew from Dodge City to San Antonio. They are separate warning offices and separate hydrology. Kansas water is High Plains urban and small-stream flooding under a slow upper low. San Antonio water is creek response in Bexar County with emergency-management confirmation.

What this is not

This is not a derecho, not a tornado outbreak, and not a U.S. hurricane landfall. SPC drew no hail risk area on the 2000 UTC outlook. No severe thunderstorm watch is in effect on that product. Rachel is a Pacific hurricane south of Baja with no U.S. coastal warning. Tropical Storm Nolo is in the central Pacific and is not a mainland landfall. The work this afternoon, where it is already reported, is floodwater in Ford County, Geary County, the San Antonio metro, and Smith County.

Looking ahead

SPC’s Day 2 convective outlook, issued 11:54 a.m. CDT and valid Friday into Friday night, forecasts no severe thunderstorm areas. A cold front is expected to reach the southern Mid-Atlantic, the Tennessee Valley, and the Texas coast by 12 UTC Saturday, with a broken band of showers and storms along it and limited destabilization where morning rain lingers. The flood story can outlast the severe story. Friday’s desk is leftover high water in Kansas and Texas, not a new Slight Risk.

Sources and how to verify

Primary sources, all dated Thursday, October 1, 2026: NOAA Storm Prediction Center 2000 UTC Day 1 Convective Outlook (updated 2:49 p.m. CDT) and Mesoscale Discussion 2345 (1:32 p.m. CDT); SPC today’s storm reports page (1200 UTC window); Weather Prediction Center Day 1 excessive-rainfall point file issued 3:26 p.m. EDT; National Weather Service warning text for Dodge City, Wichita, Topeka, Austin/San Antonio, and Shreveport; National Hurricane Center active-cyclone listing and Hurricane Rachel Advisory 17. Morning desk: Storm Updates, October 1, 2026 (Morning).

Check weather.gov for the county warning, spc.noaa.gov for the outlook and local storm reports, and the WPC excessive rainfall outlook for the flood overlay.

Informational only — not an official weather warning. Follow local authorities and the National Weather Service. Turn around, don’t drown.

October 1, 2026

Storm Updates: Kansas Tornado Aftermath, Quiet Severe Pulse — Thursday, October 1, 2026 (Morning)

This is the Thursday morning Storm Tracker desk for October 1, 2026. Overnight into this morning the organized severe window closed. The Storm Prediction Center 1300 UTC Day 1 convective outlook, issued at 7:53 a.m. CDT, has no severe thunderstorm areas forecast. No convective watches are valid. The work that verified was last evening in central Kansas, plus wind and heavy rain on the southern Plains. Today the national pulse is a Quiet Pulse on the severe side and a flood desk on the rain side.

These are county-scale thunderstorms and leftover water, not a U.S. mainland hurricane landfall. Remnant moisture from Polo is already folded into the Plains low. Restoration exposure this morning is survey work on a narrow Kansas tornado path, wind and pole damage in west and northwest Texas, and interior water where Wednesday night rain trained. Conditions change fast. Verify with the National Weather Service for the specific county or ZIP before you roll.

What expired overnight, and what is still live

Tornado Watch 675 covered central into northeast Kansas from 4:00 p.m. CDT Wednesday until 11:00 p.m. CDT. Severe Thunderstorm Watch 676 covered west-central Texas from 5:10 p.m. CDT until midnight CDT, with damaging wind to 70 mph the primary threat and a tornado or two not ruled out. Both have expired. SPC’s watch page, updated 12:12 UTC Thursday, lists no watches currently valid. The most recent issuance was Watch 676.

The 0100 UTC Day 1 update Wednesday evening still carried a Slight Risk from Texas into southwest Oklahoma and over north-central Kansas, with a couple of tornadoes possible for another hour or two in north-central and northeast Kansas. By the 0600 UTC outlook, SPC had dropped all categorical severe areas. The 1300 UTC update keeps that call. Organized severe potential is low. Occasional gusty winds can still accompany storms from parts of Kansas southward into central and southern Texas. SPC also notes a low-end funnel chance near a weakening surface wave and the front over southern Kansas, the Texas Panhandle, and western and northern Oklahoma if cloud breaks allow heating. That is not a watch, and it is not a categorical risk.

What is still live is the rain. The Weather Prediction Center short-range discussion issued at 2:52 a.m. EDT Thursday keeps a Moderate Risk of excessive rainfall over parts of the Southern Plains today. A Slight Risk covers parts of the Central Plains, the Middle Mississippi Valley, and parts of the Great Lakes. WPC language: numerous flash-flooding events are possible on the Moderate, and streams may flood, including debris flows in or near recently burned areas. The Slight is mainly localized flash flooding of urban streets, roads, and small streams. SPC’s own Day 1 text says the same thing in different words for eastern Oklahoma into north Texas, the Hill Country, and the Edwards Plateau: repetitive, locally heavy rainfall is the main concern as the rain shield shifts slowly east ahead of a surface low and cold front.

Just hit — central Kansas tornadoes

NWS Wichita has a preliminary event page for Wednesday afternoon and evening. A few low-topped supercells with very low cloud bases produced several tornadoes across Barton, Russell, and Lincoln counties ahead of a strong Plains low, in a tropical-like airmass tied in part to the remnants of Polo. Instability was not extreme. Low-level moisture was. Wichita’s summary: no significant damage or injuries reported.

SPC local storm reports for the period ending 11:59 UTC Thursday list the sequence. Storm-chaser video of a tornado 3 miles south-southwest of Ash Valley in Pawnee County at 20:49 UTC, then 1 mile southeast of Ash Valley at 20:53 UTC. Barton County followed: Olmitz at 21:52 UTC, Galatia at 21:58 UTC, several brief touchdowns west and northwest of Susank between 22:01 and 22:10 UTC, with tornado damage to some outbuildings 4 miles north-northwest of Susank. Russell County: a rope tornado 3 miles east of Bunker Hill, described as 3 miles west of Dorrance and north of I-70, at 22:51 UTC, then a spotter tornado 6 miles south of Lucas at 23:24 UTC. Lincoln County: an elephant-trunk tornado 3 miles east of Lucas at 23:39 UTC, Sylvan Grove at 23:43 and 23:53 UTC, a multi-vortex 4 miles south of Ash Grove at 00:01 UTC. A brief touchdown 2 miles southeast of Victor in Mitchell County at 00:23 UTC is the last tornado LSR on the board. NWS Wichita also issued a confirmed tornado warning for southwestern Russell and northwestern Barton counties around 4:13 p.m. CDT, with a spotter tornado south of Milberger.

Restoration read: this is a survey corridor, not a regional wind event. Outbuildings near Susank are the damage note on the filtered LSR list. Treat Barton, Russell, and Lincoln as the counties to check for roof punctures, farm structures, and tree-on-line calls. Do not staff it as a citywide loss. Photograph in daylight if it is safe. The path language from chasers and radar estimates is preliminary.

Just hit — Texas wind, and one Florida Keys note

The same LSR board has no hail reports. Wind is west and northwest Texas, mostly after dark. At least two power poles broken near the base 6 miles north-northwest of Tubbs Corner in Crane County around 20:40 UTC. A measured 58 mph gust at Clayton, New Mexico, at 22:40 UTC. One power pole and line down 1 mile northeast of Roscoe in Nolan County at 23:46 UTC. A 60 mph observer gust 24 miles south of Ozona in Crockett County at 01:06 UTC. A 64 mph gust 10 miles southwest of Paducah in Cottle County at 01:20 UTC. A 60 mph gust 4 miles south-southeast of Estelline in Hall County at 01:29 UTC. A 68 mph gust 4 miles west of Rotan in Fisher County at 02:50 UTC, the strongest measured wind on the board.

That is pole, line, and outbuilding work in the Concho Valley and Rolling Plains, consistent with Watch 676’s wind threat before it expired at midnight. Today’s SPC report page, which opens at 12:00 UTC Thursday, has no tornado, hail, or wind reports as of this desk.

One non-Plains tornado LSR sits earlier on Wednesday’s board, not in the overnight window: 16:00 UTC, 2 miles southwest of Rock Harbor in Monroe County, Florida. Preliminary highly localized damage to one residence in the Silver Shores community between Tavernier and Rock Harbor, time approximate, investigated by the emergency manager. That is a single-structure note, not a Plains-style outbreak.

Hotspot this morning — Southern Plains rain

SPC describes extensive convection from eastern Oklahoma into north Texas and southwestward into the Hill Country and Edwards Plateau, with a few stronger elements still ongoing at outlook time. The shield should keep a gradual eastward shift through the day on warm advection ahead of the surface low and cold front. Cloud cover and ongoing rain limit heating. Low-level winds are expected to weaken. Gusty winds can still occur. The severe ceiling is low. The water ceiling is not.

Wednesday’s WPC Day 1 Moderate, valid through 12 UTC Thursday, already targeted the Concho Valley, North Texas west of the Dallas–Fort Worth metroplex, the Edwards Plateau and Hill Country between San Angelo and Fort Worth, the Red River Valley, and a second Moderate from north-central Kansas through southeast Nebraska into western Iowa, including the Omaha and Des Moines corridors, with 2 to 4 inches and local amounts higher where cells trained on the warm front. Thursday’s new Moderate stays on the Southern Plains as Gulf moisture pools along the front. Cities and counties to watch for water, not for a new severe watch: San Angelo, Abilene, the Hill Country approaches to Fort Worth, southeast Oklahoma, and the Red River counties. Central Plains and western Iowa are the leftover Slight, where Wednesday night rain may already be in streets and small streams.

Restoration read: rain first. Stage extractors and drying equipment where flash-flood warnings or flooded intersections verify, especially on soils that took rain yesterday. A 58 to 68 mph gust is roof, siding, and service-drop work in the counties that already reported poles. A funnel or brief spin-up near the Kansas–Oklahoma boundary, if one occurs, is a local survey, not a second Watch 675. Do not send the Kansas tornado crew and the Texas water crew as if they are the same ticket.

Pulse table

Region	Main threats	SPC / NWS / WPC level	Status this morning
Barton, Russell, Lincoln, Mitchell KS	Tornado path, outbuildings	Watch 675 expired 11 p.m. CDT	Just hit; no significant damage reported
West-central and northwest Texas	Wind, poles, lines	Watch 676 expired midnight CDT	Just hit; 68 mph Rotan
Eastern OK / north TX / Hill Country	Heavy rain, isolated gusts	No severe areas; WPC Moderate flood	Live rain shield
Southern KS / TX Panhandle / western OK	Gusty wind, small hail, funnel chance	No categorical risk	Conditional this afternoon
Central Plains into western Iowa	Localized flash flood	WPC Slight	Overnight water, still draining
U.S. mainland tropics	No landfalling cyclone	Polo remnants inland	Quiet on the coast

What this means for restoration teams

Wind at 60 to 68 mph is roof, gutter, tree, and service-drop work, already logged in Crane, Nolan, Cottle, Hall, and Fisher counties. A tornado with no significant damage reported is still a county check: farm buildings and a few roofs can sit outside the first NWS summary. Heavy rain on a Moderate excessive-rainfall risk is wet drywall and a 24 to 48 hour mold clock if water got inside overnight. Kansas–Nebraska–Iowa water from the warm-front train is yesterday’s ticket still moving through town.

For teams on the Southern Plains: the severe watch is over. The flood risk is not. Property owners should photograph damage in daylight if it is safe, call the carrier, and start extraction the same day if water is inside. Turn around, don’t drown on low-water crossings west of Fort Worth and through the Hill Country.

What this is not

This is not a regional derecho and not a U.S. mainland hurricane landfall. National Hurricane Center products overnight included hurricane conditions in offshore waters of southwest Mexico, not a new U.S. land threat. Polo’s remnants are already in the Plains pattern. The work this morning, where it verifies, is scattered: a tornado survey in central Kansas, pole and roof calls in west Texas, and flooded intersections where the Southern Plains rain shield sits. That is the local-storm pattern this desk should staff.

Looking ahead

SPC’s Day 4–8 outlook, issued 4:00 a.m. CDT, does not flag an organized severe episode for the next several days. A large surface high dominates from the Mississippi Valley to the East Coast early next week. An isolated severe chance returns to the conversation around Tuesday from western Kansas into north-central Nebraska as a front drops southeast, then shifts toward the mid-Missouri Valley Wednesday. That is not today’s desk. WPC already flags a Slight excessive-rainfall risk on parts of the Southern Plains for Friday, and a Slight from the central Gulf Coast through the Lower Mississippi Valley into the Southern Appalachians on Saturday. Watch the afternoon Storm Tracker update rather than assuming the morning Quiet Pulse holds if a warning cluster fires on the Texas rain shield.

Sources and how to verify

Primary sources: NOAA Storm Prediction Center Day 1 Convective Outlook, 1300 UTC Thursday, October 1, 2026, and the 0100 UTC and 0600 UTC updates; SPC current watches page (no watches valid; Watch 675 and Watch 676 expired); SPC preliminary local storm reports for September 30 and October 1; NWS Wichita event summary for the September 30 central Kansas tornadoes; Weather Prediction Center short-range forecast discussion, 2:52 a.m. EDT October 1, and the Day 1 excessive-rainfall outlook covering the overnight Moderate on the Plains and Corn Belt. Prior desk: Wednesday, September 30 afternoon storm updates.

Check weather.gov for the county warning, spc.noaa.gov for the outlook, watches, and LSRs, and WPC excessive rainfall for the flood overlay.

Informational only — not an official weather warning. Follow local authorities and the National Weather Service. Turn around, don’t drown.

October 1, 2026

Storm Updates: Kansas Tornado Window, West Texas Wind Slight — Wednesday, September 30, 2026

Wednesday afternoon desk. The organized severe work is on the Plains, not the coasts. As of Wednesday, September 30, 2026, the Storm Prediction Center 1630 UTC Day 1 Convective Outlook still holds a Slight Risk of severe thunderstorms across portions of the southern and central Plains. No convective watches are currently valid. Two mesoscale discussions are live with watches possible. The Weather Prediction Center still holds Moderate Risks of excessive rainfall across portions of the central and southern Plains and the Corn Belt.

These are county- and ZIP-scale thunderstorms and flash-flood corridors. No named tropical cyclone is threatening U.S. land this afternoon. Restoration exposure is wind-driven roof and tree work from southwest Oklahoma into west Texas tonight, a conditional brief-tornado window on the Kansas warm front this evening, and interior water where cells train on already-wet ground from the Red River Valley toward Omaha and Des Moines. Conditions change fast. Verify with the National Weather Service for the specific county or ZIP before you roll.

What is live this afternoon

SPC’s 1630 UTC outlook (issued 11:26 a.m. CDT, valid 1630 UTC Wednesday through 1200 UTC Thursday) keeps two Slight Risk areas: central and eastern Kansas into far southeast Nebraska, and southwest Oklahoma / northwest Texas through the Edwards Plateau. Combined Slight coverage is about 83,861 square miles and 1.63 million people, with Topeka, Abilene, Wichita Falls, Lawton, and San Angelo on the population list. A broader Marginal wraps San Antonio, Dallas, Austin, Fort Worth, and Oklahoma City. Forecasters Mosier and Chalmers: a few tornadoes and localized wind damage are possible across Kansas and possibly far southeast Nebraska this afternoon and evening. Severe wind gusts, some hail, and a brief tornado are also expected from west Texas into southwest Oklahoma this afternoon into tonight.

No Storm Prediction Center convective watches are currently valid. The watch page, updated 2000 UTC Wednesday, still lists Watch 674 as the most recently issued product. That watch is not in effect this afternoon. Two mesoscale discussions are the live signal instead.

Mesoscale Discussion 2337, issued 2:21 p.m. CDT for portions of central Kansas into extreme northern Oklahoma, is tagged Severe potential… Watch possible, with a 60 percent probability of watch issuance. SPC says a few of the stronger storms may produce brief tornadoes, and that a Tornado Watch will likely be needed at some point in the next few hours. Timing is the open question because storm evolution is expected to be slow.

Mesoscale Discussion 2338, issued 2:56 p.m. CDT for portions of western Texas, is tagged Severe potential… Watch possible, with a 40 percent probability of watch issuance. SPC expects at least a few severe gusts and a couple instances of hail if storms increase in coverage and intensity. A Severe Thunderstorm Watch may be needed. Peak wind in that discussion is 55–70 mph. Peak hail is up to 1.25 inches.

WPC’s Day 1 Excessive Rainfall Outlook (updated 0800 UTC Wednesday, valid 12Z Wednesday–12Z Thursday) keeps Moderate Risk language on two corridors: the Front Range into the southern Plains, and the central Plains into the Corn Belt. HREF neighborhood probabilities for more than 3 inches remain 60–90 percent from the Lower Trans Pecos to the central Red River Valley. The Corn Belt footprint is still 2–4 inches, locally around 6 inches, from northern Kansas toward Omaha and Des Moines generally south of I-80.

Hotspot 1 — Central and eastern Kansas into far southeast Nebraska

This is the tornado-window corridor. SPC places the peak around 21Z to 00Z (4 p.m. to 7 p.m. CDT). Cloud cover is expected to linger, so most destabilization is from low-level moisture advection, not full heating. Low-70s dewpoints are forecast over much of central and eastern Kansas by late afternoon. RAP guidance in the 1630 UTC package shows 0–1 km storm-relative helicity of 150–200 m²/s². MD 2337 adds 200–300 m²/s² of 0–3 km SRH along the warm front and the Oklahoma–Kansas border, with backed surface flow. Tornadoes in this kind of tropical, poor-lapse-rate airmass are typically brief. SPC still treats a few longer-duration updrafts as possible.

Cities and counties to watch: Topeka under the Slight list; Wichita under the Marginal wrap; I-70 and Kansas River counties; the state-line counties toward Omaha. Today’s first LSR on the 12Z-to-12Z board is a storm-chaser video report 3 miles south-southwest of Ash Valley in Pawnee County, Kansas, at 2049 UTC (3:49 p.m. CDT). That is a live-cell report, not a damage survey.

Restoration read: tornado plus training rain. A brief tornado is a narrow swath — staff it as a local damage survey. The same warm front is a water job if cells repeat. Do not send one crew to a wind ticket and a flooded basement without checking which county has a warning now.

Hotspot 2 — Southwest Oklahoma, northwest Texas, Edwards Plateau

This remains the higher-confidence wind corridor. Low-70s dewpoints cover much of the southern Plains warm sector. Primary development is expected this evening along modest surface troughing south of the surface low moving into Kansas. An initially supercellular mode is possible from southwest Oklahoma into northwest Texas and the Edwards Plateau, where MLCAPE can reach near or above 1,500 J/kg. Front-parallel flow then favors a linear mode. Severe gusts are the most likely hazard. Isolated hail is more plausible across southwest Texas. A localized brief tornado threat can increase in the evening as effective storm-relative helicity rises.

MD 2338 is the afternoon trigger for western Texas. Surface temperatures there have reached the upper 80s to 90 F. Storms should start multicellular, then become linear as they overspread a dry boundary layer. Cities and counties: Lawton, Wichita Falls, Abilene, San Angelo, the Edwards Plateau counties under the Slight contour, and Midland on the Marginal fringe. An isolated severe threat could linger into parts of central Texas and Oklahoma overnight before buoyancy collapses east of the front.

Restoration read: wind first, water second. Stage tarps, generators, and tree crews before evening initiation, not after the first warning. If a line trains on already-wet ground, treat the same ZIP as a water job by morning.

Hotspot 3 — Southern Rockies, Front Range, and the Corn Belt flood overlay

WPC keeps a Moderate flood risk from the Sangre de Cristos and San Juan Range into the Front Range as northeasterly upslope persists on the northwest side of the surface low. Antecedent wet soils raise the flash-flood probability. Additional 2–4 inches, locally higher, remains the working range, with a second heavy period this evening as the surface low intensifies.

Farther northeast, the Corn Belt Moderate still sits on a southwest-to-northeast axis from northern Kansas through Omaha into Des Moines, generally south of I-80. Hourly rates of 1–2 inches in the better cores, with repeating action on the warm front. North of the warm front the rates drop. That is urban streets, low-water crossings, and small streams first — then finished basements if the same cell trains twice.

Just hit

Today’s 12Z-to-12Z LSR board had been empty until the Pawnee County, Kansas chaser report at 2049 UTC. That is the only official today-board entry as of this desk. Last night’s tickets still stand: a social-media tornado 3 miles south-southeast of Claude in Armstrong County, Texas, at 0012 UTC Tuesday evening; a tornado 7 miles west-northwest of Timbercreek Canyon in Randall County, Texas, at 0245 UTC; 67 mph at Roswell Air Center in Chaves County, New Mexico; 60 mph 2 miles northeast of Roswell; and 65 mph 6 miles west-northwest of Denver City in Yoakum County, Texas. Those are preliminary reports, not damage surveys.

No named tropical cyclone threatens U.S. land this afternoon. NHC is issuing advisories on Hurricane Rachel well south-southwest of Cabo Corrientes, Mexico, Tropical Storm Nolo several hundred miles west of Lihue, Hawaii, and Tropical Depression Nineteen-E over the western East Pacific. Hanna is a remnant low in the central subtropical Atlantic. None of those are a CONUS restoration staffing problem today.

Pulse table

Region	Main threats	SPC / NWS / WPC level	Status this afternoon
Central/eastern KS into SE NE	Brief tornadoes, localized wind, training rain	SPC Slight + MD 2337 (watch possible, 60%)	Peak 4–7 p.m. CDT; no watch yet
SW OK / NW TX / Edwards Plateau	Severe wind, isolated hail, brief tornado	SPC Slight + MD 2338 west TX (watch possible, 40%)	Evening initiation
Red River Valley / west-central TX	Flash flood, merging clusters	WPC Moderate	Late afternoon into Thursday morning
KS–Omaha–Des Moines (south of I-80)	Flash flood, 1–2 in/hr cores	WPC Moderate	Afternoon through overnight
Southern Rockies / Front Range	Upslope heavy rain, flash flood	WPC Moderate	Evening pulse still live
Pawnee County, KS	Live-cell chaser report	Today’s LSR board	2049 UTC / 3:49 p.m. CDT
TX Panhandle / Chaves County NM	Tornado and wind LSRs from Tuesday night	Yesterday’s Marginal	Just-hit / survey
Atlantic / East Pacific vs. U.S. mainland	No landfalling hurricane	Rachel / Nolo / Hanna offshore	Quiet on the mainland coast

What this means for restoration teams

A Slight Risk is not a watch and not a warning. MD 2337 and MD 2338 are the afternoon products that say a watch may still come. Wind at severe criteria is roof, siding, gutter, and tree-on-structure work. A brief tornado, if one occurs in Kansas or on the Edwards Plateau, is a narrow swath. Heavy rain on the two Moderate flood corridors is extraction the same night and a mold clock by Friday.

For teams in central Kansas, southwest Oklahoma, and northwest Texas: stage before the 21Z–00Z window, not after the first warning. Property owners should photograph damage in remaining daylight only if it is safe, call the carrier, and start extraction the same night if water is inside. Turn around, don’t drown on the Front Range and Corn Belt crossings.

What this is not

This is not a regional derecho and not a U.S. mainland hurricane landfall. Rachel is off western Mexico. Nolo is west of Kauai. Hanna is a remnant low in the central Atlantic. The work today, if it verifies, will be scattered: a wind swath through a Texas or Oklahoma county, a brief tornado on the Kansas warm front, a flooded intersection where cells train on the Red River or south of I-80. That is the local-storm pattern this desk should staff.

Looking ahead

The next Day 1 outlook is scheduled by 2000 UTC. SPC Day 2 (1730 UTC package, valid 12Z Thursday–12Z Friday) drops to a Marginal over portions of Kansas, Oklahoma, and Texas for isolated severe wind Thursday afternoon and evening. Watches, if they come tonight, will most likely fire on the Kansas warm front first, then western Texas if coverage increases. Watch the next Storm Tracker update rather than assuming this afternoon’s empty watch list is the last line of the day.

Sources and how to verify

Primary sources: NOAA Storm Prediction Center Sep 30, 2026 1630 UTC Day 1 Convective Outlook; SPC Mesoscale Discussions 2337 and 2338; SPC current convective watches page (no watches valid as of 2000 UTC Wednesday); SPC local storm reports for 20260930 (Pawnee County, Kansas) and 20260929 (overnight Panhandle and New Mexico); Weather Prediction Center Day 1 Excessive Rainfall Outlook updated 0800 UTC Wednesday; National Hurricane Center public pages for Rachel, Nolo, Hanna, and Nineteen-E. Check weather.gov for the county warning, spc.noaa.gov for the outlook, watch, MD, and LSRs, and WPC excessive rainfall for the flood overlay.

Morning desk: Storm Updates: Southern Plains Slight Risk, Kansas Tornado Window — Wednesday, September 30, 2026 (Morning).

Informational only — not an official weather warning. Follow local authorities and the National Weather Service. Turn around, don’t drown.

September 30, 2026

The Best Housing Product Reads the Unit Against the Score
HUD already scored the property. The household still lives with an outlet, a door, or a heat source that the score did not count. Starting October 1, those items count. That join is the product.

The idea mills keep minting a tenant chatbot, a work-order filler, and a “pass your REAC” micro-SaaS. Three names. One object. A defect in the unit that does not sit next to the public inspection file the department already posted.

The unit is not the file

Most residents treat the inspection as weather. A clipboard appears. Someone knocks. A number lands on a HUD USER spreadsheet months later. The household never sees the join: last score, last inspection date, property identifiers, and the six affirmative requirements that were cited but not deducted.

Notice PIH 2025-27 / H 2025-06, issued September 30, 2025, pushed the scoring date for those new affirmative requirements to October 1, 2026. HUD had already delayed once, to October 1, 2025. The extra year is over. The notice names the items that start taking points: fire-labeled doors; an unprotected outlet within six feet of a water source; guardrails; HVAC; interior lighting; and minimum electrical and lighting. HUD USER posted physical inspection scores through April 8, 2026 as downloadable files for public housing and multifamily assisted properties.

That is not a vibe. That is a published scoring clock landing on the same week vision models can read a kitchen outlet and a property score without a REAC consultant in the room.

The HUD Office of Inspector General’s July 24, 2026 evaluation (2026-OE-0802) pulled NSPIRE results for properties that scored 70 or below from March 1, 2025 to February 28, 2026. Of 469 public housing properties in that slice, 373 — 79.5 percent — scored below 60. Those inspections covered 5,491 buildings and 8,658 units and recorded 20,360 life-threatening and severe deficiencies. OIG also wrote that scores are expected to decline once habitability items are scored. NAHRO’s analysis, cited in the trade press this week, found public housing scores rose about 13 points after the switch from UPCS, and multifamily scores rose about 6, with unscored affirmative requirements as part of that cushion. The cushion ends tomorrow.

Who checks, who does not

The gap is not “people hate housing authorities.” The gap is who can put a photo of the unit next to the last published score before the next inspection window, the next work order, or the next complaint that becomes a record.

A resident already holds the object. Address on the lease. Outlet by the sink. Door closer that does not latch. Heat that does not reach 68. HUD already published a property-level score and an inspectable-area rulebook. The product is the join.

Do not build “AI for property managers” or “AI for tenant rights.” Those slogans die in a demo. The customer is holding a phone in a kitchen. They want to know if the outlet is the unprotected kind the notice now scores, if the last file already flagged the property, or if the unit is fine.

Two primitives, one wedge

Primitive one is photo-and-PDF review. The mills have been shipping receipt readers and home-health paperwork agents for months. Greg Isenberg’s stream and the daily micro-SaaS accounts keep splitting that reader into a work-order bot, a “pass REAC” coach, and a housingcheck.ai. The input here is a photo of the inspectable item plus the address on the lease or the property name on the building. Outlet. Door label. Guardrail. Thermostat. Kitchen light.

Primitive two is the public inspection file. HUD USER already ships comma-delimited scores. The NSPIRE standards and the scoring notice already list what an inspector must cite. The checker does not invent a fair apartment. It joins the photo to the last published score and the defect family that starts taking points on October 1, or it says the join failed and why.

The first action a stranger will take this week is upload. Phone photo of the outlet by the sink. No account required to see the first verdict: scored item, not scored, property not in the HUD file, or photo too thin to judge. If it matches a scored family, you still captured a labeled pair. If the property is not assisted housing, you say so and stop. That honesty is the product.

That is the only honest offer on day one. Do not ask them to connect a Yardi feed. Do not ask a housing authority to install anything. Do not scrape every PHA work-order system before you have watched a hundred kitchens fail a join.

The chatbot is a flag, not the company

A product that only talks will recreate the old legal-aid intake gap in cheaper clothes. The wedge is the labeled join, not another chat pane on top of a blurry outlet.

Hallucinated inspection IDs are how this category gets banned from the front desk. Cite the HUD USER file date. Cite the notice. Cite the defect family. Do not cite a score the model dreamed.

A checker that points at the real PHA complaint process or the real HUD hotline is useful. A checker that invents a federal “housing refund request” is a scam adjacent. Same rule as the tax essay: point at the real form or shut up.

What compounds

The first useful output is a three-line verdict. The business is the labeled corpus.

After a few thousand photos you know which properties post a passing score while kitchens still show unprotected outlets, which authorities close work orders without touching the scored item, which multifamily owners pass building systems and fail in-unit electrical, which files on HUD USER are current and which are theater. That map is what a legal-aid housing desk, a PHA inspector trainer, an owner’s insurance desk, or a city council watchdog will pay for. Not another portal. A ranked list of properties where the unit photo and the published score refuse to meet.

Do not sell the map first. Close real questions on real photos. The dashboard of “possible habitability savings” is how this idea dies in a pitch.

Irreversible steps stay human

A model can draft the work order. It can pull the last score and write the mismatch paragraph. It can calendar the mitigation window that already exists under NSPIRE severity categories. A person owns the send. A formal complaint, a request for tenancy termination, or a claim that the unit is uninhabitable creates a record a court will treat as a claim. Same rule we use on every filing in this shop: the model drafts, a named human signs.

Do not let the product call itself counsel of record. Do not let it file the complaint, accept a contingency check, or speak at the informal hearing. Those are seats, not features. Charge after the join shows a scored defect the file did not absorb, or do not charge.

What not to build

Do not build a nationwide housing platform in month one. You will drown in HCV units that are still on a later NSPIRE clock, city code that is not NSPIRE, and market-rate buildings that have no HUD file at all.

Do not scrape every PHA site on day one and call it a marketplace. Most addresses will fail a join. Your first hundred uploads teach you which columns actually exist.

Do not brand this as an agentic housing copilot. The sentence attracts the wrong first ten users and the wrong first ten housing lawyers.

A build order that will survive contact
- Week 1–2: one checker. Photo plus address in. Scored item, not scored, not in file, or photo too thin. No account for the first answer. One metro, public housing and multifamily only.
- Week 3–4: a draft work-order or complaint pack with a human signer. Defect family, last published score, notice citation. Contingency or a cheap per-letter fee only after the first free verdict.
- Month 2: add a second photo type for the same unit — door closer, heat register, bathroom fixture. Keep one metro until the join rate is honest.
- Month 3: publish the first ugly internal scoreboard. Properties, defect families, mismatch rates against HUD USER. That scoreboard is the seed of the B2B SKU.
If you cannot get a stranger to photograph one outlet this week, you do not have a company. You have a policy thread.

Why this cut, not the last one

The leakage essay was tariffs, seats, and subscriptions. The rebate essay was a nameplate. The recall essay was a label. The short-pay essay was a contractor packet. The bill essay was an EOB against a hospital file. The tax essay was a notice against the roll. The utility essay was a statement against a filed tariff. This one is the housing version of the same primitive pair: a photo the resident already can take, plus a public file the institution was forced to publish, joined on the week the grace period ends.

The noticing used to require a housing counselor and a weekend. It now requires a model that can read the outlet and a person who will sign the form. Recovery still works because the first check costs the resident almost nothing. Charge them after the score file and the photo refuse to meet, or do not charge them.

Someone will own the labeled map of unit versus score. The mills will keep proposing a new .ai name for each inspection form. Ignore the names. Join the line. Keep the map.

Will Tygart — Tygart Media.

This is the idea-mill series.
September 30, 2026

Storm Updates: Southern Plains Slight Risk, Kansas Tornado Window — Wednesday, September 30, 2026 (Morning)

This is a live Wednesday morning snapshot of U.S. local-storm activity as of Wednesday, September 30, 2026. The organized desk is back on the Plains. The Storm Prediction Center 1300 UTC Day 1 Convective Outlook holds a Slight Risk of severe thunderstorms across portions of the southern and central Plains. No convective watches are currently valid. The Weather Prediction Center holds Moderate Risks of excessive rainfall across portions of the central and southern Plains and the Corn Belt.

These are county- and ZIP-scale thunderstorms and flash-flood corridors, not a U.S. mainland hurricane landfall. The National Hurricane Center’s last advisory on Polo said the remnants dissipated over northwestern Mexico. Restoration exposure today is wind-driven roof and tree work on the southern Plains this afternoon and evening, a conditional tornado window on the Kansas warm front, and interior water where cells train on already-wet ground. Conditions change fast. Verify with the National Weather Service for the specific county or ZIP before you roll.

What is live this morning

SPC’s 1300 UTC outlook (issued 7:57 a.m. CDT, valid 1300 UTC Wednesday through 1200 UTC Thursday) upgrades Day 1 to a Slight Risk over about 82,000 square miles covering parts of southwest Oklahoma, northwest Texas, the Edwards Plateau, and a separate corridor through central and eastern Kansas into far southeast Nebraska. A broader Marginal wraps Fort Worth, Oklahoma City, Wichita, Norman, and Midland. Forecasters Guyer and Bentley: thunderstorms capable of severe wind gusts, some hail, and a brief tornado are expected across the southern Plains this afternoon into tonight. A few tornadoes and localized wind damage are also possible across Kansas and possibly far southeast Nebraska.

No Storm Prediction Center convective watches are currently valid. The watch page last listed Watch 674 as the most recently issued product; that watch is not today’s product and is not in effect this morning. Any new watch this afternoon would be a new number. Today’s SPC local-storm-report board (1200 UTC Wednesday through 1159 UTC Thursday) is empty as of this desk. That is expected before the diurnal window.

WPC’s Day 1 Excessive Rainfall Outlook (updated 0800 UTC Wednesday, valid 12Z Wednesday–12Z Thursday) keeps Moderate Risk language on two corridors: the Front Range into the southern Plains, and the central Plains into the Corn Belt. HREF neighborhood probabilities for more than 3 inches run 60–90 percent from the Lower Trans Pecos to the central Red River Valley, with a 2–4 inch, locally 6 inch footprint from northern Kansas toward Omaha and Des Moines south of I-80.

Overnight into this morning

Tuesday night’s 12Z-to-12Z LSR board is the just-hit file. Two tornado reports came in from the Texas Panhandle after midnight UTC: a social-media video tornado 3 miles south-southeast of Claude in Armstrong County at 0012 UTC (7:12 p.m. CDT Tuesday), position estimated via radar by NWS Amarillo; and a tornado 7 miles west-northwest of Timbercreek Canyon in Randall County at 0245 UTC (9:45 p.m. CDT), reported south of State Highway 335 west of I-27, on the ground 3–4 minutes and then roped out. Those are preliminary reports, not damage surveys.

Severe wind also verified on the same night: 67 mph at Roswell Air Center (KROW) in Chaves County, New Mexico, at 0033 UTC; 60 mph 2 miles northeast of Roswell at 0037 UTC; and 65 mph 6 miles west-northwest of Denver City in Yoakum County, Texas, at 0324 UTC, with additional measured gusts near 59 mph around 10:22 p.m. CDT. No hail reports were logged on that board. Tuesday afternoon’s Storm Tracker already had the Southwest flood-and-Marginal frame; last night added the Panhandle tornado and New Mexico/west Texas wind tickets.

Hotspot 1 — Southwest Oklahoma, northwest Texas, Edwards Plateau

This is the higher-confidence diurnal severe corridor. SPC expects early-day convection across the southern Plains to weaken or shift north by early afternoon, then redevelop late afternoon into evening ahead of the approaching mid/upper-level low. Heating of a very moist airmass should push MLCAPE near or above 1,500 J/kg from southwest Oklahoma into northwest Texas and the Edwards Plateau despite poor mid-level lapse rates. Supercells are possible at first. Front-parallel flow and increasing coverage favor a more linear mode with time. Strong to severe gusts are the most likely hazard. Isolated hail is more plausible across southwest Texas. A localized brief tornado threat can increase in the evening as effective storm-relative helicity rises in the moist environment.

Cities and counties to watch: Lawton, Wichita Falls, Abilene, San Angelo, Midland on the Marginal fringe, and the Edwards Plateau counties that sit under the Slight contour. An isolated severe threat could linger into parts of central Texas and Oklahoma overnight before buoyancy collapses east of the front.

Restoration read: wind first, water second. Stage tarps, generators, and tree crews before the late-afternoon initiation, not after the first warning. If a line trains on already-wet ground, treat the same ZIP as a water job by morning.

Hotspot 2 — Central and eastern Kansas into far southeast Nebraska

SPC upgraded this corridor on the 1300 UTC package. A rather strong low-level jet (50-plus knots diurnally) is forecast to shift northeast across central and eastern Kansas into western Missouri and southeast Nebraska or southwest Iowa by evening. Destabilization near the warm front may stay weak because of clouds, ongoing rain, and poor mid-level lapse rates. The upgrade is about 0–1 km and 0–3 km wind profiles that stay supercell-conducive even if CAPE stays muted. Multiple tornadoes are treated as a viable possibility, not a high-confidence outbreak.

Cities to watch: Topeka under the Slight population list; Wichita under the Marginal wrap; the I-70 and Kansas River counties; the Nebraska state-line counties toward Omaha. Flood Watch language was already in play overnight for parts of north-central and northeast Kansas through Thursday afternoon, with 2–4 inches widespread and locally around 6 inches in the wetter cores.

Restoration read: this is the tornado-and-water overlap. A brief tornado is a narrow swath — staff it as a local damage survey. Training rain on the same warm front is wet drywall and a 24–48 hour mold clock. Do not send the same crew to a wind ticket and a flooded basement without checking which county actually has a warning now.

Hotspot 3 — Southern Rockies, Front Range, and the Corn Belt flood overlay

WPC keeps a Moderate flood risk from the Sangre de Cristos and San Juan Range into the Front Range as northeasterly upslope persists on the northwest side of the surface low. Antecedent wet soils raise the flash-flood probability. Additional 2–4 inches, locally higher, is the working range, with two heavy periods: morning and again in the evening as the surface low intensifies.

Farther northeast, the Corn Belt Moderate sits on a southwest-to-northeast axis from northern Kansas through Omaha into Des Moines, generally south of I-80. Hourly rates of 1–2 inches in the better cores, with some repeating action on the warm front. North of the warm front the rates drop and the flash-flood signal cuts off. That is urban streets, low-water crossings, and small streams first — then finished basements if the same cell trains twice.

Just hit

Claude and Randall County, Texas, tornado reports and the Roswell / Denver City wind gusts are last night’s tickets. They sit under yesterday’s Marginal from southern and eastern New Mexico into west Texas. Today’s new work, if it verifies, is farther east and north: the southwest Oklahoma–northwest Texas–Edwards Plateau wind corridor, the Kansas warm-front tornado window, and the Moderate flood footprints on the southern Plains and the Kansas–Nebraska–Iowa axis.

Polo is not a U.S. landfall desk this morning. NHC’s last forecast/advisory (number 38, 0300 UTC Wednesday) placed the remnants near 30.5°N 108.0°W over northwestern Mexico and forecast dissipation by 12Z Wednesday. Hanna is an open-Atlantic tropical storm well east of the mainland. Neither is a restoration staffing problem for the CONUS this morning.

Pulse table

Region	Main threats	SPC / NWS / WPC level	Status this morning
SW OK / NW TX / Edwards Plateau	Severe wind, isolated hail, brief tornado	SPC Slight	Afternoon–tonight initiation
Central/eastern KS into SE NE	A few tornadoes, localized wind, training rain	SPC Slight + WPC Moderate flood	Conditional; no watch yet
Red River Valley / west-central TX	Flash flood, merging clusters	WPC Moderate	Late afternoon into Thursday morning
KS–Omaha–Des Moines (south of I-80)	Flash flood, 1–2 in/hr cores	WPC Moderate	Afternoon through overnight
Southern Rockies / Front Range	Upslope heavy rain, flash flood	WPC Moderate	Morning and evening pulses
TX Panhandle / Chaves County NM	Tornado and wind LSRs from Tuesday night	Yesterday’s Marginal	Just-hit / survey
Atlantic / East Pacific vs. U.S. mainland	No landfalling hurricane	Polo dissipated over NW Mexico	Quiet on the mainland coast

What this means for restoration teams

A Slight Risk is not a watch and not a warning. It is the afternoon and evening probability field. Wind at severe criteria is roof, siding, gutter, and tree-on-structure work. A brief tornado, if one occurs in Kansas or on the Edwards Plateau, is a narrow swath. Heavy rain on the two Moderate flood corridors is extraction the same night and a mold clock by Friday.

For teams in southwest Oklahoma, northwest Texas, and the Kansas warm-front counties: stage before mid-afternoon local, not after the first Severe Thunderstorm Warning. Property owners should photograph damage in remaining daylight only if it is safe, call the carrier, and start extraction the same night if water is inside. Turn around, don’t drown on the Front Range and Corn Belt crossings.

What this is not

This is not a regional derecho and not a U.S. mainland hurricane landfall. Polo is gone over northwestern Mexico. Hanna is in the central Atlantic. The work today, if it comes, will be scattered: a wind swath through a Texas or Oklahoma county, a brief tornado on the Kansas warm front, a flooded intersection where cells train on the Red River or south of I-80. That is the local-storm pattern this desk should staff.

Looking ahead

The next Day 1 outlook is scheduled by 1630 UTC. Day 2 on the SPC page is already a Marginal. Watches, if they come, will most likely fire late afternoon on the southern Plains and early evening on the Kansas warm front. Watch the next Storm Tracker update rather than assuming this morning’s empty watch list is the last line of the day.

Sources and how to verify

Primary sources: NOAA Storm Prediction Center Sep 30, 2026 1300 UTC Day 1 Convective Outlook; SPC current convective watches page (no watches valid as of 1313 UTC Wednesday); SPC local storm reports for 20260929 (overnight) and 20260930 (today, empty after 12Z); Weather Prediction Center Day 1 Excessive Rainfall Outlook updated 0800 UTC Wednesday; National Hurricane Center remnants of Polo forecast/advisory 38. Check weather.gov for the county warning, spc.noaa.gov for the outlook, watch, and LSRs, and WPC excessive rainfall for the flood overlay.

Prior desk: Storm Updates: Southwest Flood Moderate, New Mexico–West Texas Marginal — Tuesday, September 29, 2026.

Informational only — not an official weather warning. Follow local authorities and the National Weather Service. Turn around, don’t drown.

September 30, 2026

Author: William Tygart

What is live this morning

Hotspot 1 — Central Gulf Coast

Hotspot 2 — Lower Texas coast

Northern Plains scatter, and what expired

Tropics — not a U.S. land desk

Pulse table

What this means for restoration teams

Next check

Sources and how to verify

The export that refused to invent numbers

The hang that has been a verify for six days

Rank Math did not see the week

What I would not repeat

The patch that did land

Still open

What is live this afternoon

Hotspot 1 — Dallas–Fort Worth to San Antonio, the Slight

Hotspot 2 — Kansas water, after the emergency

Hotspot 3 — Mid-Atlantic gusts below a risk area

Just hit

Pulse table

What this means for restoration teams

What this is not

Looking ahead

Sources and how to verify

The code is not the promise

Why this month, not last year

Two primitives, one wedge

The map is the company

Models draft. People file.

Why this cut, not the last one

What expired overnight, and what is still live

Hotspot 1 — Dodge City and central Kansas water, after the emergency

Hotspot 2 — San Antonio and south Texas water, then a Saturday Gulf Coast slight

Hotspot 3 — Mid-Atlantic gusts that stay below a risk area

Just hit

Pulse table

What this means for restoration teams

What this is not

Looking ahead

Sources and how to verify

What is live this afternoon

Hotspot 1 — Dodge City and southwest to central Kansas

Hotspot 2 — San Antonio metro and northeast Texas

Hotspot 3 — Southern Kansas and northwest Oklahoma Marginal

Just hit

Pulse table

What this means for restoration teams

What this is not

Looking ahead

Sources and how to verify

What expired overnight, and what is still live

Just hit — central Kansas tornadoes

Just hit — Texas wind, and one Florida Keys note

Hotspot this morning — Southern Plains rain

Pulse table

What this means for restoration teams

What this is not

Looking ahead

Sources and how to verify

What is live this afternoon

Hotspot 1 — Central and eastern Kansas into far southeast Nebraska

Hotspot 2 — Southwest Oklahoma, northwest Texas, Edwards Plateau

Hotspot 3 — Southern Rockies, Front Range, and the Corn Belt flood overlay

Just hit

Pulse table

What this means for restoration teams

What this is not

Looking ahead

Sources and how to verify

The unit is not the file

Who checks, who does not

Two primitives, one wedge

The chatbot is a flag, not the company

What compounds

Irreversible steps stay human

What not to build

A build order that will survive contact

Why this cut, not the last one