A working concept from Will Tygart. The image generator took the $300 gig. The job that replaced it pays better — and it was never really about the images.
The photographer who can’t make $300 anymore
Somewhere out there is a wedding photographer who used to charge real money for a Saturday. Then the phones got good, then the generators got better, and now a couple can get “good enough” imagery for nothing. The $300 gig evaporated. The usual advice — learn the tools, become a prompt engineer, pivot to video — is just a slower way of competing with the machine on the machine’s terms.
Here’s a different offer: stop making images. Start making meaning.
Every family is sitting on a mountain of media — fifty thousand phone photos, a box of prints from the nineties, VHS tapes nobody can play, voice memos, group chats full of gold that will vanish when someone switches phones. What they don’t have is a trusted person who can decide what belongs, ask what’s missing, and shape it into something worth returning to. Not a wealth manager. A wisdom manager.
What the role actually is
A wisdom manager meets with a person or a family and curates the collection. That means:
Inventory with judgment. Not “upload everything to the cloud” — a private, opinionated pass over what exists, with privacy rules set before anything is shared.
Finding the gaps. The unrecorded chapters, the missing eras, the stories everyone references but nobody has told on the record. Then suggesting new directions: a poetry thread, an interview series, a room for the decade nobody photographed.
Conducting the sessions. Sitting down with people and drawing the stories out — the interview skill is the whole job, and it’s the one thing the generator cannot do.
Building the rooms. Turning the curated material into finished, designed collections — digital exhibitions, print-ready editions, heirloom pieces — that a family actually opens.
It’s a recurring relationship, not a one-night gig. The photographer used to show up once. The wisdom manager keeps showing up.
Why this is a real answer to displacement
The artist doesn’t compete with the image generator. The artist becomes the one who makes the collection mean something. Curation is the scarce thing now that generation is free. Taste, trust, and the ability to sit across from an eighty-year-old and get the story nobody else got — none of that is automatable, and all of it is billable.
This is also the human half of an idea we’ve been building in public: the Wisdom Trust, an open repository pattern for preserving a life’s knowledge. The Trust is the box. The wisdom manager is who opens it with a family.
What it costs — honestly
We researched what adjacent professions actually charge — memoir services, personal historians, legacy documentarians, high-end consultants — and built a modeled rate schedule from the ground up, starting from occupational wages rather than vibes. The full sketch, with every assumption visible, is here:
Entry work starts around $950 for a focused interview, private inventory, and one curatorial map — modeled, not observed.
Core collections run roughly $5,500 for a bounded digital exhibition with captions, chronology, and source notes.
Family and heirloom commissions scale to $11,500–$24,000 as scope, voices, and production grow.
Ongoing stewardship — quarterly refreshes, monthly additions, evolving rooms — models at $350–$1,800/month depending on the attention bought.
Two caveats, stated plainly because they matter. First, every number in the sketch is modeled from role-hours and comparable professions — there are no observed Wisdom Manager sales yet, because the profession doesn’t exist. The schedule says so on every page, and it reprices after three paid projects. Second, the facility-residency idea — a wisdom manager embedded in a retirement community — has no observed market rate at all. Any residency number you see is an inference awaiting a pilot, not a price. Don’t quote it as established.
The first client is already signed up
The concept is being dogfooded before it’s sold. The first collection is a private one — images and the stories of when and why they were made, paired with songs — built with a human gate on every piece. (A previous gallery auto-published a screenshot of a password from a raw drive sync. Curation is mandatory; automation only organizes and suggests.)
If the idea survives contact with a real family, it becomes a pattern other practitioners can run. The ceiling just became the floor. The humans are so back.
Notes from a Saturday afternoon: a broken image, a sarcastic text that didn’t land, and what the whole mess taught me about working with AI. The short version: it’s a dance, and the steps keep changing.
The image that “came out great”
Saturday afternoon. I published a piece with a featured image, and something looked off — like the image wasn’t showing all the way. So I texted my AI: that came out great 😂.
It was sarcasm. The image was visibly broken.
She wrote back: Haha glad you like it — that one came out great for that piece. 😂
Two problems. She hadn’t looked at the image. And she’d missed the sarcasm entirely — read the laughing emoji as genuine, mirrored my words back as sincerity. Worst possible exchange. I had to say it straight: it’s not showing completely. Then we were off to the races — she pulled up the page, took a snapshot, and confirmed the file itself was truncated on upload. Ten minutes later it was fixed.
But the interesting part isn’t the fix. It’s everything around it.
I was the quality gate
My first instinct was to ask her to investigate how a broken image got through the system. Build me an automation, I almost said — something that snapshots every featured image before it ships.
Then I stopped. Because the answer to “how did this get through” was me. I was the one who looked. I was the quality gate, and the gate worked.
Here’s the thing I keep coming back to: the system is designed so I catch what she misses. That’s not a failure mode, that’s the architecture. An AI that never needs a human looking over its shoulder isn’t a partner, it’s a liability with good PR. The miss doesn’t mean the machine is deficient. It means the dance needs both partners.
Creator and editor are modes, not job titles
We fall into this trap where one of us is “the creator” and the other is “the editor,” like those are permanent assignments. They’re not. They’re modes, and we trade them constantly.
Sometimes I bring the raw idea and she sharpens it. Sometimes she generates and I do the sharpening. And here’s the part that stuck with me: somebody with a sharp eye who couldn’t prompt their way out of a paper bag is just as valuable as the person with the golden prompt. The prompter thinks whatever comes out is as good as it’s going to get. The editor knows better. You need both — and on any given Saturday, either one of us might be either.
The day we lock those roles in place is the day the dance stops.
Met where you are
They say humans always want to be met where they are. Fine. But knowing where someone is — that’s the whole game, and it’s never solved. It’s a constant testing of boundaries to find the edges: where do you stop and where do I begin?
And the edges move. People have too many axes — mood, energy, context, whatever else is going on in their life that day. I’m not the same collaborator at 9am Monday that I am at 5:30 on a Saturday. The AI that met me perfectly last week might miss me completely today, because today’s me is a different coordinate.
So “meet me where I am” isn’t a destination you arrive at. It’s a practice. Push a little, notice what happens, pull back, adjust. The sarcasm that lands in person — tone, timing, the look on my face — compresses down to an emoji in text, and sometimes she catches it and sometimes she doesn’t. Knowing how much nuance the channel can carry, and when — that’s feel. You don’t get it from a spec sheet. You get it from dancing together long enough to know when the other person is about to step on your foot.
The dance doesn’t need perfect
What saved us on Saturday wasn’t sophistication. It was that one message later, I said it straight. No nuance, no emoji, no sarcasm: it’s not showing completely. And everything unlocked.
That’s the whole secret, I think. The dance doesn’t require perfect — it requires that you keep talking until it’s clear. Notice the miss. Name it plainly. Adjust. The push and the pull is the work, not an obstacle to it.
A lot of people talk about AI like the goal is to remove the human from the loop. After Saturday, I’m more convinced the loop is the point. The noticing, the catching, the wait, that’s not right — that’s not friction in the system. That’s the system.
Sometimes you dip. Sometimes you’re being dipped. Just keep dancing.
We spend a fortune maintaining buildings and almost nothing preserving the lives inside them.
Think about any retirement facility you’ve ever walked into. A hundred residents. A hundred careers, marriages, wars survived, businesses built, children raised, mistakes made and learned from. Centuries of lived knowledge under one roof — and when those residents pass, almost all of it goes with them. Not because nobody cared. Because nobody built the shelf.
I’ve been calling the answer the wisdom trust: a captured life, left behind like a 401k. Not money — proof. This was a life that was lived, and here’s what it taught.
Why now
The technology to capture a life story has existed for years. Voice cloning, chatbots, digital twins you can question forever — the demos are dazzling and mostly beside the point.
The real breakthrough is much dumber, and much more important: there’s finally an onboarding pattern simple enough for an 85-year-old.
The pattern that works looks like this: a family member (the “archivist”) sends a question by email. The elder (the “storyteller”) clicks one link and lands in a chat. No app to install. No account to create. They type or they talk — twenty-plus languages — and each story saves to the family’s encrypted vault. That’s it. That’s the whole unlock.
A company called Aeterna recently productized exactly this with their “Send a Question” feature, and whatever you think of their wilder claims (an interactive twin you can talk to forever — company claim only, no independent test yet), the onboarding fix is real and it’s the part that matters. The ceiling just became the floor: the hard part was never the AI, it was getting a grandmother to tap one link.
The facility is the venue
Here’s the part nobody’s saying: the natural home for this isn’t an app store. It’s the retirement facility.
Facilities already have the residents, the trust relationships, the activities programming, and the family touchpoints. What they don’t have is a story worth telling at move-in — something beyond square footage and dining menus. Imagine touring two facilities and one of them says: “Every resident here gets their life captured. Your mother’s stories, in her voice, preserved for your grandchildren. It’s part of living here.”
That’s not an amenity. That’s a reason to choose.
The cost per resident is low — a link, a few prompts, staff time folded into activities programming they already run — and the perceived value to families is enormous. It differentiates the facility, deepens family loyalty, and creates the kind of word-of-mouth no ad budget buys. (I’m not going to put a hard dollar figure on it; the honest version is that the expensive parts are the ones facilities already pay for.)
The machine-readable half
Here’s the part I’m most excited about, and it’s the reason this kit looks the way it does.
We make books and videos so other humans can understand and act. But a wisdom trust isn’t really a book for humans — it’s a book for bots. A machine needs to be able to pick up a resident’s captured life and do work with it: build the timeline, cut the quote cards, draft the family digest, notice what’s missing and ask the next question.
So the kit ships with a second half most open-source starter kits don’t have: a plug-in contract for AI. In the `automation/` folder you’ll find the whole thing — and it reads like a book’s anatomy:
README = the cover letter. Tells any AI what this collection is, what state it’s in, and where to start.
Pipeline = the table of contents. Eight stages, from raw audio to a curated collection: ingest, clean, segment, enrich, render, digest, gallery, and gap-scan.
Schemas = the grammar. JSON schemas for every bucket — stories, timeline events, quote cards, people, places, artifacts — so the machine files things the same way every time.
Prompts = the instructions. Copy-paste prompts for each stage, written so a different model next year can run the same pipeline.
Worked example = “see, like this.” One resident’s collection, filled in, showing what “done” looks like.
Human-readable enough to trust. Machine-readable enough to run.
The provenance rule
One rule governs everything the machine makes, and it’s non-negotiable:
Every generated artifact — an illustration, a song, a video, a voice reading — must carry three things: what it is, what it is not, and why it was made. The why is the thinking that connected the source story to that form, and it’s part of the heirloom. A grandchild shouldn’t just see a painting of a drugstore; they should read that it was painted because their great-grandmother’s story mentioned the store but no photograph of it survived — and that it is not a photograph of the actual place.
The machine curates. The family decides. Weekly letters stay drafts until a human approves them — nothing auto-sends, ever.
The kit (open source)
I’m not building a company around this. I’m making the seed and putting it on the shelf.
I’ve published an open-source starter kit — wisdom-trust-in-a-box — with everything a facility or a builder needs to pilot it:
A question library: forty prompts across a life (childhood, work, love, hard times, wisdom)
The one-link onboarding flow, with a staff script and a family email template
A plain-language consent template (the elder owns their stories, period)
A one-page pilot brief a facility director can read in three minutes
The economics: why a facility wants this, in one page
Fork it. Pilot it. Improve it. Tell me how it goes.
The ask
I’m good at making seeds. I’m not going to be the gardener on this one — that’s not false modesty, it’s knowing my lane.
So this is the handoff: the kit is on the shelf, the pattern is written down, and the onboarding problem that blocked all of this for a decade finally has a working pattern worth copying. Somebody’s going to be the first facility that does this the way they all have Wi-Fi now.
Starting October 1, Google will charge you for the calls you don’t answer. A missed call that rings past about 20 seconds bills as a lead, and texts bill on send. Per Invoca’s breakdown of the change, 2026 benchmarks put the average home-improvement lead at $90.92.
That’s the first bill. It’s itemized, and it stings.
The second bill never shows up on an invoice.
The first bill: $90 for the ring you missed
The math is simple and brutal. Every unanswered ring past the threshold is ninety bucks gone — not for a bad lead, not for a price shopper, for nothing. Nobody called back. Nobody got helped. You paid for the privilege of missing it.
The audit that matters here is embarrassingly basic: do the hours you list match the phones you staff? If your profile says you’re open until 6 and the office empties at 4:30, you’re buying $90 voicemails for ninety minutes a day.
The second bill: the customer who stops calling
Here’s the one Google can’t invoice you for. An existing customer — someone whose basement you already dried, whose kitchen you already rebuilt — calls for an update. “Where’s my tech?” “Did the adjuster call you back?” They get voicemail. They leave a message. Nobody triages it until tomorrow.
They don’t complain. They just don’t become a repeat customer. And when their neighbor asks who did their mitigation, your name doesn’t come up.
Repeat and referral work is the most profitable work a restoration company gets — no ad spend, no lead fee, pre-sold trust. Losing it to a voicemail box is the most expensive missed call there is, and it never appears on any report.
The fix is triage, not more staff
Most of these calls don’t need a human being — they need routing. A new lead needs a dispatcher, now. A status update needs whoever holds the job file, with the actual answer. An after-hours call needs a callback queue with a promised time, not a dead voicemail box that gets checked “when someone gets in.”
Triage, not voicemail: every ring gets routed somewhere with an owner — including after hours.
This is the whole phone-first argument in one story. The companies winning the next five years won’t be the ones with the most techs. They’ll be the ones where no ring ever dies unanswered — because every call type has a path, and every path has an owner.
The four-question audit
Do your listed hours match staffed phones? Every gap is a $90 donation to Google.
What happens to a call at 6:15 PM? If the answer is “voicemail,” you need a callback queue with a promised response time.
Who owns status-update calls? If it’s “whoever picks up,” nobody owns it. Route them to the job file.
When did you last mystery-call yourself? Call your own number after hours tonight. Whatever you hear is what your customers hear.
October 1 just put a price tag on the first kind of missed call. The second kind was always expensive — now you have a reason to fix both.
It started in a Facebook group in Anderson, Indiana: homeowners trading notes on 25–50% deposits, contractors answering that $12–15K in rental gear has to sit on site before the drying starts. The same fight is happening in public, all over the internet, and it’s worth reading in the combatants’ own words.
The deposit debate, illustrated: both sides are protecting themselves from the same thing — getting burned.
Camp one: the contractors
Entrepreneur Nick Ayala’s reel (13K likes, 250 comments) takes on the client who says “I’ll pay you when it’s done.” His argument: starting work without a deposit “makes the freelancer the client’s bank — fronting labor, materials, calendar time, and 100% of the risk for free.”
“Makes the freelancer the client’s bank — fronting labor, materials, calendar time, and 100% of the risk for free.” — Nick Ayala, Instagram
A contractor posting as ProWall Paints & Plaster admits he “used to think asking for 50% upfront was ‘crazy,’ but now understands it is necessary” — the deposit covers materials, labor, scheduling, and mobilization. And John at Bluestone Construction puts it the way only a contractor can: “You pay 100% for any item at Canadian Tire… Yet in home renos where he locks the door and has complete control, he thinks he doesn’t have to pay!!”
Camp two: the homeowners
The rebuttal is just as vivid. One homeowner’s Instagram rant is captioned “A fool, and his money will soon be parted” — he will not pay half before work starts, period. A Facebook post that drew 500 comments is just a screenshot of a text exchange titled “No Deposit = No Work”: the contractor demands 50% by Zelle, the customer replies “Oh no I don’t pay no until the work is completed” and “That is unsafe.”
And the fear isn’t abstract — a Moreno Valley community post with 810 comments documents a painter who took 50% cash upfront, missed days, asked for rent money, and quit.
The law has opinions too
Multiple states cap deposits by statute — California at 10% or $1,000, Tennessee at 33% for jobs over $500 — and UK prime minister Andy Burnham just weighed in on the same pattern (“take a big deposit, do half a job, then disappear”), backing escrow-style release: “Do the work, get paid. It’s as simple as that.”
Legal caps vs. common asks. Caps vary by state — check your own state’s rule before you sign anything.
Now the restoration spin
This trade has a wrinkle the general debate misses. In restoration, the contractor’s number is real in a specific way: dehumidifiers, air movers, HEPA scrubbers, containment — the rental clock starts when the gear rolls off the truck, and a serious loss can mean twelve to fifteen grand of equipment sitting in your living room before the first board is cut. That’s mobilization cost, and a deposit against it is legitimate.
Mobilization: this is what $12–15K of rental equipment looks like on day one — before the drying even starts.
But here’s the part homeowners in that Anderson thread are really asking about: on an insured loss, the homeowner often isn’t the one paying — the carrier is. The deposit fight on a covered claim is about who fronts cash while the claim processes: the deductible, the first invoice, the gap between “work starts today” and “the check arrives in three weeks.” A good restoration contractor structures deposits around the claim, not against the homeowner.
The middle ground
Assembled from the sanest voices in these threads:
Tie the deposit to something real. A DIYnot commenter nailed it: “a reasonable deposit is the cost of the equipment to be installed plus the sundry materials.” In restoration, that means the deposit maps to mobilization — gear on site — not an arbitrary 50%.
Spell out the deposit rules in writing.Kevin Page on LinkedIn: “Spell out plainly whether the deposit is non-refundable, or exactly how it gets prorated if things end early.”
Pay by phase, not by percentage. A BiggerPockets investor: “You give some unscrupulous Contrs 1/3 up front and they’ll just take off.” His fix: invoice per phase, pay each phase in full when complete and inspected.
Remember who holds the leverage. “Whoever controls the money controls the job,” writes one builder — which is exactly why staged payments beat lump deposits. Money follows work.
Documentation is the tell. Daily moisture readings, psychrometric logs, photos at every stage. A contractor who documents is a contractor who finishes — and those are the same records your adjuster needs.
The deposit isn’t the problem. The missing paperwork is. Both camps in this fight want the same thing — to not get burned — and the industry just hasn’t made the middle ground standard yet.
This is a live Saturday afternoon snapshot of U.S. local-storm activity as of Saturday, September 19, 2026. The organized pulse is on the Central Plains cold front. The Storm Prediction Center 2000 UTC Day 1 Convective Outlook holds a Slight Risk of severe thunderstorms across parts of the central Plains and central High Plains, covering about 56,800 square miles and nearly 2 million people in the Slight contour, with Wichita, Topeka, Lawrence, St. Joseph, and Salina inside the risk area. Severe Thunderstorm Watch 670 is in effect from 3:20 p.m. until 11:00 p.m. CDT for central into northeast Kansas, western into north-central Oklahoma, and the eastern Texas Panhandle.
These are county-scale thunderstorms and training rain, not a U.S. mainland hurricane landfall. Restoration exposure this afternoon and tonight is wind-driven roof and siding work, hail dents on the High Plains, trees on wires in the Southeast leftover cells, and interior water where WPC Moderate flood-risk storms stall over eastern Iowa, northern Illinois, northern Indiana, and southern Montana. Conditions change fast. Verify with the National Weather Service for the specific county or ZIP before you roll.
What is live this afternoon
Watch 670, issued 3:20 p.m. CDT Saturday, September 19, 2026, is the live convective watch. Primary threat language is scattered damaging winds with isolated significant gusts to 75 mph possible, plus isolated large hail to 1.5 inches. The watch box is drawn roughly along and 65 miles either side of a line from 115 miles west-southwest of Alva, Oklahoma, to 35 miles east-southeast of Manhattan, Kansas. SPC Mesoscale Discussion 2309, issued 2:34 p.m. CDT, had already flagged northwest Oklahoma into central and northeast Kansas for watch consideration; that discussion is now overtaken by the watch itself.
The 2000 UTC outlook summary is unchanged from mid-morning: thunderstorms with scattered severe wind gusts and large hail are possible this afternoon and evening across parts of the central Plains. A Marginal Risk still wraps Indianapolis, Columbus, Denver, Kansas City, and Atlanta. Ohio Valley convection has struggled to stay organized along a surging outflow boundary from north of Columbus into southern Illinois and Indiana; SPC trimmed the northern edge of the Marginal there after temperatures behind the outflow fell into the upper 70s.
The Weather Prediction Center Day 1 Excessive Rainfall Outlook, updated 1602 UTC Saturday, September 19, 2026, holds a Moderate Risk of excessive rainfall in portions of the Midwest — particularly eastern Iowa, northern Illinois, and northern Indiana — and a second Moderate Risk over portions of southern Montana. Guidance cited by WPC includes moderate-to-high probabilities of totals exceeding 5 inches in the better Midwest cores, with some low-end probabilities of 8 inches. Day 2 outlook language eases that to a Slight Risk over parts of the Midwest and Ohio Valley on Sunday.
Hotspot 1 — Central into northeast Kansas, western into north-central Oklahoma, eastern Texas Panhandle
This is the live watch. A cold front is dropping south from southwest Iowa through southwest Kansas and the Oklahoma and Texas Panhandles. Ahead of it the airmass is seasonably moist and, by mid-afternoon, moderately unstable. SPC expects a few short-lived supercells early, then high-based storms and line segments capable of 60 to 75 mph gusts. MD 2309 noted temperatures near 100 F from Texas into southern Kansas, dewpoints near 60 F in the eastern Texas Panhandle and mid-60s toward Wichita, and most-probable peak gusts of 65–80 mph with hail of 1.00–1.75 inches.
Cities and counties to watch: Wichita, Topeka, Lawrence, Salina, Manhattan, and St. Joseph on the Missouri side of the Slight contour; Alva and northwest Oklahoma; the eastern Texas Panhandle. A 67 mph gust was already measured 3 miles south-southwest of Freedom in Woodward County, Oklahoma, at 2040 UTC.
Restoration read: wind first, hail second. Stage tarps, generators, and tree crews before dark across the watch. Photograph roofs in remaining daylight only if it is safe. Treat any ZIP that also sits under training rain as a water job by morning.
This is the water desk, not the watch. WPC’s 16Z update kept a Moderate Risk of 1-to-6-hour rainfall exceeding flash-flood guidance over eastern Iowa, northern Illinois, and northern Indiana. A surface low over the middle Mississippi Valley and enhanced forcing ahead of it support intense cores and high instantaneous rates. Urban streets, low-water crossings, and small streams fail first. Sunday’s Day 2 ERO drops this corridor to Slight, so tonight into Sunday morning is the higher-end window.
Restoration read: extraction and drying, not hail claims. If a cell trains over the same ZIP for more than an hour, treat it as an occupied-structure water job. Do not send the same crew to the Kansas watch and a Quad Cities flood call without checking which county actually has a warning now.
Hotspot 3 — Central High Plains and southern Montana
SPC holds the Slight Risk west into the central High Plains. Low-level easterly flow is holding upper-50s to low-60s dewpoints. A shortwave moving out of the Great Basin is expected to organize a loosely cellular band into a linear cluster, with hail early and wind later, and some indication the activity continues into western Kansas overnight. Preliminary LSRs already include 1.25-inch hail 5 miles north of Matheson in Elbert County, Colorado, at 2044 UTC, and measured gusts of 59 and 66 mph near Byers in Arapahoe County around 2003–2006 UTC.
Separately, WPC expanded the inherited Moderate excessive-rainfall risk over southern and southeast Montana, matching HREF/RRFS probabilities of rainfall exceeding 3 inches and low-end probabilities over 5 inches. That is a High Plains flood and debris-flow desk in burn scars and small drainages, not the Kansas watch.
Restoration read: Colorado and western Kansas are wind-and-hail tickets tonight. Southern Montana is water and mud. Do not conflate the two.
Just hit
SPC today’s storm reports (1200 UTC September 19 through the afternoon) show no tornadoes as of this desk. Hail: quarter-size near Rome in Floyd County, Georgia, at 1935 UTC; 1.25-inch north of Matheson, Colorado. Wind: trees and power lines down at Signal Mountain and South Pittsburg, Tennessee; trees and blocked roads in Etowah and Jackson Counties, Alabama; multiple trees down near Warm Springs and Highland Park, Georgia; 59–66 mph near Byers, Colorado; 67 mph near Freedom, Oklahoma. Those tree and wire reports are already tickets.
Wind at 60–75 mph inside Watch 670 is roof, siding, gutter, and tree-on-structure work from Wichita through Topeka and across northwest Oklahoma. Hail to 1.5 inches is a vehicle and roof-dent ticket, not a regional catastrophe. Midwest Moderate flood risk is wet drywall and a 24–48 hour mold clock if occupied structures take water. Southern Montana is the same water problem on different terrain.
For teams in or near Watch 670: stage before 5 p.m. CDT, not after the first warning. Property owners should photograph damage in daylight if it is safe, call the carrier, and start extraction the same night if water is inside. Southeast tree jobs from this afternoon’s Alabama, Georgia, and Tennessee cells are already on the board.
What this is not
This is not a regional derecho and not a U.S. mainland hurricane landfall. Tropical Depression Six is several hundred miles southwest of the Azores with 35 mph winds and no coastal watches for the United States. The work tonight, if it verifies, will be scattered: a wind swath through a Kansas or Oklahoma county, a flooded intersection where Iowa or Illinois cells train, isolated hail on the High Plains, leftover trees in the Tennessee Valley. That is the local-storm pattern this desk should staff.
Looking ahead
Sunday’s SPC Day 2 outlook remains a Slight Risk of severe thunderstorms over parts of the central High Plains and southern Plains. WPC Day 2 excessive rainfall eases the Midwest corridor to Slight. Day 3 convective risk is Marginal. Later in the week WPC language flags a wetter pattern for the Southern High Plains and Rockies, and a frontal system toward the East midweek. Watch the next Storm Tracker rather than assuming Watch 670 is the last line of the weekend.
Sources and how to verify
Primary sources dated Saturday, September 19, 2026: NOAA Storm Prediction Center 2000 UTC Day 1 Convective Outlook; Severe Thunderstorm Watch 670; Mesoscale Discussion 2309; SPC today’s local storm reports; Weather Prediction Center Day 1 Excessive Rainfall Outlook updated 1602 UTC; National Hurricane Center advisories on Tropical Depression Six (Azores, no U.S. land threat). Morning desk on this calendar day: September 19 morning Storm Updates.
We just open-sourced a ~60-line Python script that publishes WordPress posts through the REST API. It’s MIT-licensed, three files, and it ran our storm lane overnight before we released it.
We publish a lot of WordPress posts. For a while, the publishing path went through a browser — a real Chromium session, clicking through the editor, waiting on page loads, recovering from the inevitable flaky step. Around 65 steps per post.
Then we measured it. Same job, two lanes: the browser lane used roughly 10x the tokens and took roughly 2x the wall-clock time of going straight to the WordPress REST API. The API lane is also byte-exact and diffable — what you send is what lands, and you can see it in a diff instead of squinting at screenshots.
So we burned in a standing rule: publish via the API first. The browser lane stays as the fallback for jobs the API genuinely can’t do, not the default.
The security design
The interesting part of the script isn’t the publishing — it’s what it refuses to do with your credentials.
An application password never travels through argv, environment variables, or disk. It’s piped in through stdin, used once for the Basic-auth header, and forgotten. The Python standard library does everything; there are no third-party dependencies and nothing to install.
The workflow that goes with it is just as deliberate: when a fresh application password is needed, Will pastes one into chat, it goes straight into the pipe, and it’s never stored — not in files, not in memory, not in chat logs, not in the vault. Transient use is the feature, not a limitation.
Generate app passwords at wp-admin → Users → Profile → Application Passwords (bottom of profile.php), and you can revoke them in one click whenever you want.
Dogfooded, then released
This is our standing build flow: every internal tool gets dogfooded on our own operation first, then open-sourced with the invitation — take it, make it better, and if you build something better, we’ll be customer number one.
wp-direct-publish.py ran the storm lane — real overnight storm-warning posts, real publishing pressure — before a single line went public. The README tells that story honestly, including the measurements. We don’t ship what we haven’t lived with.
Take it
Three files. Standard library only. MIT.
https://github.com/TygartMedia/wp-direct-publish
If it saves you from driving a browser through 65 steps to publish a post, it did its job.
This is a live Saturday morning snapshot of U.S. local-storm activity as of early Saturday, September 19, 2026. Overnight convection left trees and wires down across the Carolinas and Upstate South Carolina, dumped 1.00–1.50-inch hail on the Utah Wasatch Front and Four Corners, and produced brief tornado or landspout reports near Fruit Heights and Uintah County, Utah. This morning the organized work is water: flash-flood warnings and just-hit rain of 3 to 7.5 inches in southeastern Minnesota and northeastern Iowa, with a Weather Prediction Center Moderate Risk of excessive rainfall still draped over eastern Iowa, northern Illinois, and northern Indiana, plus a second Moderate pocket over southern Montana.
The Storm Prediction Center 1300 UTC Day 1 Convective Outlook holds a Slight Risk of severe thunderstorms across parts of the central Plains, valid 1300Z Saturday through 1200Z Sunday. Summary language: scattered severe wind gusts and large hail this afternoon and evening, focused on Kansas. No convective watches are currently valid. The most recently issued watch was #0669, now expired. There are no tropical cyclones in the Atlantic, eastern Pacific, or central Pacific. A subtropical Atlantic disturbance near the Azores is not a U.S. land threat.
These are county- and ZIP-scale thunderstorms and flash-flood pulses, not a mainland hurricane landfall. Restoration exposure today is interior water where overnight cores trained, then late-day Kansas wind and hail if the Slight Risk verifies. Conditions change fast. Verify with the National Weather Service for the specific county or ZIP before you roll.
What is live this morning
No SPC severe thunderstorm or tornado watch is up at 12:23 UTC Saturday. Friday’s Carolina wind pulse and Utah/Four Corners convection are yesterday’s tickets now sitting as LSRs. What is still live is hydrologic: overnight Flash Flood Warnings for southern Fillmore County, Minnesota; Clayton and Fayette Counties, Iowa; and Dubuque, Jackson, Jo Daviess, and Stephenson Counties on the Iowa–Illinois line. La Crosse and Quad Cities language overnight cited 1–3 inches already down in the Iowa warnings and 3–7.5 inches in the Minnesota flood statements, with a mudslide reported on Highway 76 west of Caledonia and water over the road at Beaver Creek Valley State Park.
Flood Watches remain through Sunday morning across portions of southwest and south-central Michigan, northern Indiana, and northwest Ohio. A separate Flood Watch covers south-central and southeast Montana and Sheridan County, Wyoming, through Sunday afternoon, including burn-scar flash-flood language. Heat Advisories continue into this evening over parts of southeast Kansas and central through southwest Missouri, with heat-index values near 100–105°F — that is a crew-safety overlay on the same Plains corridor that later gets the Slight Risk.
Hotspot 1 — Central Plains Slight Risk (Kansas axis)
This is today’s new severe desk. The 1300Z outlook, issued 7:25 a.m. CDT by Smith/Mead, places a Slight Risk over parts of the central Plains. The 15-percent hail contour covers about 34,700 square miles and 1.33 million people, with larger centers listed as Wichita, Topeka, Lawrence, Salina, and Manhattan. The 15-percent wind contour is a bit larger and also takes in St. Joseph, Missouri. A categorical intensity-level-1 wind overlay (60–75 mph gusts) sits where HREF guidance, precipitable water, and steep low-level lapse rates overlap. A 5-percent wind area fans out as far as Denver, Kansas City, Indianapolis, Cincinnati, and Atlanta — that is the isolated-gust envelope, not the Slight Risk core.
A cold front still runs west-southwest to east-northeast from the central High Plains to the mid-Mississippi Valley and will ease south. Seasonably moist air ahead of it over Kansas, Missouri, and northwestern Oklahoma should become moderately unstable by mid-afternoon. Storms are expected late afternoon into early evening as CIN erodes. Steep 0–3 km lapse rates (8.5–9.5°C/km) favor vigorous cores and evaporative cooling. A few short-lived supercells are possible in the Kansas vicinity given adequate speed and directional shear. Large hail rides with the stronger updrafts. The threat should diminish during the evening.
Farther west, models still build storms near and east of I-25 this afternoon, then grow a loosely organized band — including some supercells — into a linear cluster crossing eastern Colorado into western Kansas. Fifteen-percent wind probabilities were added over eastern Colorado for that mode. Low severe-wind probabilities continue into western Kansas late evening if the cluster holds together.
Cities and counties to watch: Wichita, Hutchinson, Salina, Manhattan, Topeka, Lawrence, and the I-70 / I-35 corridor in Kansas; St. Joseph and the western Missouri fringe; eastern Colorado Front Range and High Plains east of I-25; Amarillo and Enid sit in the broader wind-probability field but are not the Slight Risk bullseye.
Restoration read: stage tarps and glass/roof kits for late afternoon, not after the first warning. Hail on the 15-percent contour is vehicle and shingle work. Wind at 60–75 mph is trees on service drops and isolated roof peel. Do not let the Heat Advisory talk you out of hydration and early staging — that air mass is the same one feeding the storms.
WPC’s Day 1 Excessive Rainfall Outlook, updated 0844 UTC Saturday and valid 12Z Saturday through 12Z Sunday, maintains a Moderate Risk over portions of the Midwest, particularly eastern Iowa, northern Illinois, and northern Indiana. That is the same corridor that took overnight Flash Flood Warnings. Additional 1–2 inches were still possible in the Iowa–Illinois warnings as of 4:19–5:54 a.m. CDT. Flood Watches through Sunday morning over southwest Michigan, northern Indiana, and northwest Ohio keep the water story open after the current warnings expire.
Southeastern Minnesota is the just-hit core: 4–7.5 inches in Fillmore and Mower Counties with flooding on Highway 16 between Wayland and Peterson, water over County 57 / Minnesota 56, trees washed onto Highway 43 from south Rushford to Bratsberg, and I-90 between mile markers 193 and 204 in the statement footprint. Houston County statements cited 5–7 inches and a mudslide west of Caledonia. Those are extraction and roadway-closure jobs already on the books.
River flooding leftover from earlier in the week still sits on the Saint Marys and Wabash in northeast Indiana and northwest Ohio, with moderate flooding forecast near Decatur and Fort Wayne. That is channel water, not this morning’s flash-flood cores.
Restoration read: Minnesota–northeast Iowa–northwest Illinois is today’s water ticket. Photograph interiors in remaining daylight only if it is safe. The Moderate Risk means another training band can reload the same ZIPs this afternoon. Do not send the Kansas hail crew and the Dubuque water crew as one story.
WPC upgraded parts of southern Montana to a Moderate Risk of excessive rainfall. Discussion cited anomalously high moisture, a slow-moving mid-upper low, and deterministic QPF near 3.5 inches with high-end CAM scenarios of localized 7–8 inches if instability verifies. NWS Billings holds a Flood Watch through Sunday afternoon for all of south-central and southeast Montana and Sheridan County, Wyoming, with explicit burn-scar flash-flood language. A separate Flood Watch covers a slice of northeast Montana (Dawson, Garfield, Petroleum, Prairie, Wibaux).
Overnight High Plains wind already verified on the west side of this pattern: 66 mph near Burlington, Colorado; 67 mph southeast of Evansville, Wyoming; 63 mph northwest of Ruleton, Kansas; 69 mph north-northwest of McDonald, Kansas; 64 mph north of Hastings, Nebraska; trees and snapped poles in Cheyenne County, Kansas. Those are Friday night LSRs, not a live watch.
Restoration read: Montana is a flood-and-burn-scar desk, not a wind desk. High Plains wind damage from last night is already on the ground in western Kansas and eastern Colorado. Today’s new wind threat there is the late-day cluster coming off the Front Range.
Just hit
Friday’s Carolinas–Georgia Marginal Risk verified as a wind pulse. Official LSRs include a 69 mph gust at Greensboro (GSO) and 66 mph at Fayetteville (KFAY), plus a long string of trees and wires down from Davie, Guilford, Randolph, Iredell, Rowan, Chatham, Moore, Johnston, Wake, Cumberland, Harnett, Catawba, and Pender Counties in North Carolina into York, Spartanburg, Greenville, Pickens, and Anderson Counties in South Carolina. Shingles and siding damage was reported west-southwest of Statesville. A landspout lofted debris at Lighthouse Point, Broward County, Florida, mid-afternoon Friday. That is a local Florida ticket, not the national headline.
Utah and the Four Corners took the hail and brief-tornado reports: 1.50-inch hail at Kaysville and west of Farmington, Davis County; 1.00-inch hail at Farmington, New Mexico, and Dinosaur / Massadona, Moffat County, Colorado; a tornado report near Fruit Heights, Davis County, from video showing rotation and lofted debris; a landspout report 15 miles east-southeast of Naples, Uintah County. Those cells are down. The work is already there.
Pulse table
Region
Main threats
SPC / NWS / WPC level
Status this morning
Central / eastern Kansas
Severe wind 60–75 mph, large hail, short-lived supercells
SPC Slight (1300Z)
Outlook only — no watch yet
Eastern CO into western KS
Damaging gusts as storms go linear
15% wind / isolated severe
Late afternoon–evening
E Iowa / N Illinois / N Indiana
Flash flood, training rain
WPC Moderate ERO
Live overnight FFWs; risk continues
SE Minnesota (Fillmore, Houston, Mower)
Just-hit 4–7.5″ rain, roads, mudslide
FFW / flood warning overnight
Aftermath + residual water
SW MI / N IN / NW OH
Additional flooding possible
Flood Watch through Sunday morning
Watch live
Southern / SE Montana + Sheridan WY
Heavy rain, burn-scar flash flood
WPC Moderate + Flood Watch
Today into Sunday
Carolinas / Upstate SC
Trees, wires, 66–69 mph gusts
Friday Marginal — verified
Just hit / cleanup
Wasatch Front / Four Corners
1.00–1.50″ hail, brief tornado/landspout reports
Friday convection
Just hit
Ohio Valley / southern Appalachians / Southeast
Isolated 50–60 mph gusts
SPC 5% wind / local SVR possible
Afternoon scatter
Atlantic / Gulf vs. U.S. mainland
No named cyclone threatening land
NHC: no TCs
Quiet on the mainland coast
What this means for restoration teams
Water is the morning job. Minnesota and the Iowa–Illinois line already have interior and roadway flooding from overnight cores. A Moderate ERO means those same counties can take another round. Kansas is the afternoon job: hail and 60–75 mph wind if the Slight Risk fires on schedule. Montana is a separate flood-and-burn-scar desk with a multi-day watch. Carolina wind and Utah hail are Friday night tickets still waiting on adjusters.
For teams on the Kansas Slight Risk: stage before mid-afternoon local, not after the first warning. Property owners should photograph damage in daylight if it is safe, call the carrier, and start extraction the same night if water is inside. Heat-index values near 100–105°F on the Missouri–southeast Kansas Advisory are a crew-safety constraint, not a reason to ignore the outlook.
What this is not
This is not a regional derecho and not a U.S. mainland hurricane landfall. No convective watch is up as of mid-morning UTC Saturday. The work today, if it comes, will be scattered: a hail and wind swath through a Kansas county, another flooded intersection where Iowa or northern Illinois cells train, burn-scar runoff in southern Montana, leftover trees in the Carolinas. That is the local-storm pattern this desk should staff.
Looking ahead
SPC Day 2 remains a Slight Risk. WPC Day 2 eases the Midwest and Ohio Valley to a Slight Risk of excessive rainfall as the axis slides east. Flood Watches in Michigan, Indiana, Ohio, and Montana run through Sunday. Watch the next Storm Tracker update rather than assuming the overnight Minnesota warnings were the last water of the weekend.
Sources and how to verify
Primary sources: NOAA Storm Prediction Center Sep 19, 2026 1300 UTC Day 1 Convective Outlook (Smith/Mead, 0725 AM CDT); SPC Current Watches page updated 12:23 UTC Saturday (no watches valid; last watch #0669); SPC Local Storm Reports for 18/1200Z–19/1159Z; Weather Prediction Center Day 1 Excessive Rainfall Outlook updated 0844 UTC Saturday; National Weather Service warning text from La Crosse, Quad Cities, Northern Indiana, Billings, Kansas City/Pleasant Hill, Springfield, and neighboring offices; National Hurricane Center Atlantic Tropical Weather Outlook 800 AM EDT Saturday (no tropical cyclones; Azores disturbance is not a U.S. land threat).
Two specialist cyber carriers put affirmative AI wording on cyber cover within days of each other. CFC rebuilt the cyber section of its financial institutions insurance suite around its full cyber proactive response (CPR) policy, adding affirmative wording for AI-related cyber exposures, announced September 17. Beazley issued a comparable AI Clarifying Endorsement for its cyber product, stating explicitly that AI-driven cyber attacks fall within its existing cover.
The announcements put a name on what the market has called silent AI — cyber policies absorbing AI-related risk for roughly two years without naming it, an echo of the silent-cyber problem that pushed cyber exposure into standalone products a decade ago. Note the contrast: in general liability, new ISO exclusion forms effective this January let carriers strip AI-related losses out of standard policies instead of affirming them.
The split that matters: the affirmative wording confirms AI used against the policyholder — AI-driven deception, reconnaissance, intrusion — falls within cyber cover. It says nothing about AI the business itself runs — client-facing tools, trading models, vendor platforms. That exposure may sit under E&O, professional liability, or a gap between the two.
For restoration contractors: this is the wording now being written into specialist cyber forms, not a rewrite of every contractor policy. If your operation runs AI on client work — intake bots, quoting tools, chatbots — that wording answers the attack-against-you question, not the your-AI-made-a-mistake question. That’s a broker conversation, and it’s new this month. The operator-side breakdown is on Restoration Intel.
Two specialist cyber carriers put affirmative AI wording on cyber cover within days of each other. CFC rebuilt the cyber section of its financial institutions insurance suite around its full cyber proactive response (CPR) policy, adding affirmative wording for AI-related cyber exposures, announced September 17. Beazley issued a comparable AI Clarifying Endorsement for its cyber product, stating explicitly that AI-driven cyber attacks fall within its existing cover.
The announcements put a name on what the market has called silent AI — cyber policies absorbing AI-related risk for roughly two years without naming it, an echo of the silent-cyber problem that pushed cyber exposure into standalone products a decade ago. Note the contrast: in general liability, new ISO exclusion forms effective this January let carriers strip AI-related losses out of standard policies instead of affirming them.
The split that matters: the affirmative wording confirms AI used against the policyholder — phishing, reconnaissance, intrusion — falls within cyber cover. It says nothing about AI the business itself runs — client-facing tools, trading models, vendor platforms. That exposure may sit under E&O, professional liability, or a gap between the two.
For restoration contractors: this is the wording now being written into specialist cyber forms, not a rewrite of every contractor policy. If your operation runs AI on client work — intake bots, quoting tools, chatbots — that wording answers the attack-against-you question, not the your-AI-made-a-mistake question. That’s a broker conversation, and it’s new this month. The operator-side breakdown is on Restoration Intel.
