TL;DR: My personal AI runs on Muse. It can’t write code into my repos by itself — so I built it a bridge to Cursor’s cloud agents. One repo, two transports, nine tools. Now when I say “add CI to that repo,” it dispatches an agent, checks the PR, and merges. Here’s how the Muse-to-Cursor loop actually works.
The direction nobody talks about
Everyone’s building the same arrow: human → AI writes code faster. I built the other arrow: AI → AI. My assistant (Muse) holds all my context — my repos, my work orders, my rules. Cursor’s cloud agents hold the hands — they can open PRs, run CI, touch repos. The bridge between them is an MCP server I open-sourced: cursor-cloud-agents-mcp.
The interesting part isn’t the tools. It’s the shape: one orchestrator that holds all the context, and disposable agents that each know one task. The orchestrator doesn’t write the code — it briefs, checks, and merges. The agents don’t set direction — they execute the brief. That separation is the whole trick.
Two transports, one repo
I almost built two projects. Then I realized the only real difference between audiences is where the credential lives. So it’s one repo, two transports:
REST — your Cursor API key, direct to api.cursor.com. For general users.
Sandbox — for assistants running inside sandboxed environments (like Muse/Meta’s), where there is no API key to hand out. It shells out to a brokered cursor-agent CLI on PATH instead.
Same nine tools either way: launch, status, result, follow-up, cancel, list, models, whoami, usage.
The lessons are in the timeouts
The v1 API splits agents and runs, and launches can take minutes — sometimes timing out after succeeding. So the bridge mints the agent ID client-side before the call: a retry after a timeout can never create a duplicate. A timeout is reported as unknown, never as failure, then reconciled. Run status is the source of truth, because agent “ACTIVE” doesn’t mean “still working.” These are the details that separate a demo from something you can actually operate.
It earned its keep on day one
The first thing I pointed it at was its own repo: add CI to cursor-cloud-agents-mcp. The agent opened a PR with a GitHub Actions workflow. The first CI run failed — and caught a real bug: the package’s floating dependency had resolved to MCP 2.x, which renamed FastMCP out from under the import. The repo was shipping broken against current dependencies and nobody knew. Pin, re-run, green, merge. I didn’t touch a terminal.
I didn’t trust my own first draft
Before any of that, four AI models reviewed the spec against Cursor’s live docs — and independently caught the same flaw: my original design was shaped around the retired v0 API. Then two more reviewed the actual code and found real bugs: a broken idempotency path, a transport auto-detect that would have grabbed the wrong binary, a polling loop that blocked the server. All fixed before it shipped. The irony I like: the final review round ran through the bridge itself. The launcher timed out on all four agents — and the bridge’s own timeout-reconciliation showed they were all actually running.
Where this goes
v1.1 brings MCP 2.x support. Around it, I’m building the rest of the pattern: work orders as GitHub issues, a daily SLA check, a weekly digest — the scaffolding that turns “AI that can open PRs” into something closer to staff. Most people use agents as a faster keyboard. I’m interested in what happens when they’re the hands and something with memory is the head.
MIT licensed. Issues and PRs welcome — help make it better.
This is a live Saturday afternoon snapshot of local storm-type events across the United States as of Saturday, September 12, 2026. The organized pulse is on the south-central Plains. The Storm Prediction Center holds a Slight Risk of severe thunderstorms across parts of the south-central Plains into the Ozarks, and Severe Thunderstorm Watch 667 is in effect from 3:45 p.m. until 10:00 p.m. CDT for portions of southwest Kansas, Oklahoma, and the Texas Panhandle. Farther east, the Weather Prediction Center keeps a Slight Risk of excessive rainfall over the Ohio Valley and Mid-Atlantic. Tropical Storm Norbert is over the open eastern Pacific and is not a U.S. land threat.
These are county- and ZIP-scale thunderstorms, not a mainland hurricane landfall. Restoration exposure this afternoon and evening is wind-driven roof and siding work, isolated large hail, trees on service drops, and interior water where cells train over already-wet ground in the Ohio Valley and Mid-Atlantic. Conditions change fast. Verify with the National Weather Service for the specific county or ZIP before you roll.
What is live this afternoon
Watch 667 covers southwest Kansas, Oklahoma, and the Texas Panhandle through 10:00 p.m. CDT. Primary threat language from SPC: scattered damaging winds and isolated significant gusts to 80 mph, plus isolated very large hail to 2 inches. Tornado probability in the watch is low. The 2000 UTC Day 1 outlook, issued 3:00 p.m. CDT Saturday, expanded the Slight Risk southwest across parts of western Oklahoma after satellite showed agitated cumulus and isolated initiation along a remnant outflow. Temperatures of 102–104°F south of the wind shift support severe-caliber downdrafts if clusters organize.
Mesoscale Discussion 2286, issued 2:52 p.m. CDT, flagged southern Kansas into northwest Oklahoma as watch-likely before the watch went up. Most probable peak gusts in that discussion were 65–80 mph; most probable peak hail 1.50–2.50 inches. MD 2287 followed on a severe-potential, watch-possible track as storms tried to fill in.
WPC’s Day 1 Excessive Rainfall Outlook, valid 12 UTC Saturday through 12 UTC Sunday, keeps a Slight Risk over the Ohio Valley and Mid-Atlantic. That language is flood first, wind second: 2.0–2.25 inch precipitable water along I-95 from Richmond toward Philadelphia, with a higher-end Slight pocket in the upper Ohio Valley where flash-flood guidance is under 2 inches in northern West Virginia and western Pennsylvania. Central Plains stay Marginal for excessive rain. Florida remains in a localized urban-flood environment on 2.0–2.25 inch precipitable water.
The official SPC Local Storm Report list for the 12 UTC Saturday through 12 UTC Sunday window was still empty as of mid-afternoon, which is expected this early in the convective day. SPC’s same-day report-trend plot on the homepage was already counting preliminary tornado, wind, and hail ticks as storms started to fire. Treat those as unofficial until they land on the LSR page.
This is the live watch. Storms are expected to increase and intensify near an outflow boundary across Oklahoma and near a front across Kansas and the eastern Texas and Oklahoma Panhandles. SPC notes a narrow corridor of 2,000–3,500 J/kg MLCAPE, 30–40 kt of deep-layer shear, and steep mid-level lapse rates that support isolated 2-inch hail before storms cluster. Higher-based convection in the hot mixed layer favors wind over tornadoes.
Cities and counties to watch: Wichita, Hutchinson, and Emporia in Kansas; Enid, Ponca City, and the Oklahoma City metro fringe; Alva to Chandler along the watch axis; Amarillo and the eastern Texas Panhandle. Neighboring offices: Dodge City, Wichita, Norman, Tulsa, Amarillo.
Restoration read: wind and hail first. Stage tarps, generators, and glass/roof crews before dark. A 75–80 mph gust on a well-mixed 104°F afternoon is a tree-and-roof ticket, not a regional catastrophe. Photograph roofs in remaining daylight only if it is safe.
Hotspot 2 — Ohio Valley and Mid-Atlantic flood pulse
This is the water desk, not the watch desk. WPC holds a Slight Risk of excessive rainfall from the upper Ohio Valley through the Mid-Atlantic. HREF signals in the morning discussion showed moderate-to-high chances of 3-hour and 6-hour flash-flood guidance exceedance in the upper Ohio Valley, and 20–40 percent chances of 3-hour totals over 2 inches from the Richmond area late Saturday into the Delaware Valley and southern New Jersey Saturday night. The Slight Risk was extended north through eastern Pennsylvania, northern New Jersey, and into the New York City metro and lower Long Island for late Saturday night into Sunday.
SPC keeps a Marginal Risk of isolated damaging wind with loosely organized clusters in the upper Ohio Valley this afternoon. That is secondary to the flood overlay.
Cities and counties to watch: Pittsburgh and western Pennsylvania; northern West Virginia; Columbus–Dayton corridor on the wind-marginal fringe; Richmond, Baltimore, Philadelphia, and the I-95 urban core Saturday night.
Restoration read: extraction and drying if cells train. Urban streets, underpasses, and small streams fail first. Do not treat this as the same story as Watch 667. Different hazard, different crew mix.
Hotspot 3 — North Georgia leftover water and Plains scatter
National Weather Service Peachtree City issued multiple Flash Flood Warnings this morning for Cobb, DeKalb, Douglas, Fulton, Carroll, and Paulding counties, including Atlanta, Marietta, Sandy Springs, Douglasville, and Villa Rica. Radar-indicated totals of 1–4 inches were already on the ground in those products, with additional 1–3 inches possible in the warned windows. Some of those warnings expired by mid-afternoon; the water is still in the street and in the buildings. That is already a ticket, not a new watch.
Elsewhere, isolated strong-to-severe cells remain possible on the edges of the Slight Risk into the Ozarks and on the hot High Plains. Florida stays a local urban-flood and lightning desk on deep tropical moisture. A Flash Flood Watch remains up over the Paradise and Hagen burn scar in northeast Oregon and southeast Washington from Saturday afternoon through Sunday evening — debris-flow country, not a CAT event.
Just hit
Friday’s official LSR window (12 UTC September 11 through 12 UTC September 12) is the last closed book. Preliminary reports included a tornado touchdown 7 miles northeast of Artichoke, Minnesota, plus golf-ball hail near Artichoke and Alberta in Stevens County, Minnesota. Wind and hail also hit Tarrant County, Texas (Arlington–Mansfield trees, poles, and up to 1.75-inch hail), Bexar County, Texas (golf-ball hail near Converse and Kirby), and a long tree-down swath through South Carolina, Virginia, and North Carolina. Those are already claims. Today’s new work, if it verifies after 12 UTC Saturday, is Watch 667 wind and hail plus Ohio Valley–Mid-Atlantic water.
Pulse table
Region
Main threats
SPC / NWS level
Status this afternoon
SW Kansas / Oklahoma / TX Panhandle
Damaging wind to 80 mph, isolated 2-inch hail
Slight + Watch 667 to 10 p.m. CDT
Live watch
Ohio Valley / Mid-Atlantic
Flash flood, training heavy rain, isolated wind
WPC Slight excessive rainfall; SPC Marginal wind
Tonight into Sunday morning
North Georgia metro
Urban flash flood leftover from morning warnings
FFW earlier today
Aftermath / still in street
Ozarks / central Plains fringe
Isolated hail and wind
SPC Marginal
Scattered
NE Oregon / SE Washington burn scar
Flash flood / debris flow
Flash Flood Watch through Sunday evening
Local hydrologic
Atlantic / Gulf vs. U.S. mainland
No landfalling tropical cyclone
Quiet on the mainland coast
Quiet (Norbert open EPAC)
What this means for restoration teams
Wind at 65–80 mph is roof, siding, gutter, and tree-on-structure work. Isolated 2-inch hail is broken glass and pitted panels in a narrow swath, not a statewide event. Heavy rain on the Ohio Valley–Mid-Atlantic Slight Risk is wet drywall and a 24–48 hour mold clock. Atlanta-metro water from this morning is already inside some buildings.
For teams in or near Watch 667: 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. Do not send the same crew to Oklahoma wind and Pittsburgh water without checking which county actually has a warning now.
What this is not
This is not a regional derecho and not a U.S. mainland hurricane landfall. Tropical Storm Norbert is expected to dissipate east-southeast of Hawaii by midweek and is not a CONUS or Hawaii landfall problem on this desk. The work tonight, if it comes, will be scattered: a wind or hail swath through a Kansas or Oklahoma county, a flooded intersection where Ohio Valley or Mid-Atlantic cells train, leftover urban water in metro Atlanta. That is the local-storm pattern this desk should staff.
Looking ahead
Sunday, SPC Day 2 is a Marginal Risk of strong storms with small to marginally severe hail and locally damaging wind from the Ohio Valley to the Northeast. Coverage is uncertain. Monday, Day 3 adds a small Slight Risk across eastern Nebraska into western Iowa. Watch the next Storm Tracker update rather than assuming Watch 667 is the last line of the weekend.
Sources and how to verify
Primary sources, all date-stamped Saturday, September 12, 2026: NOAA Storm Prediction Center 2000 UTC Day 1 Convective Outlook; Severe Thunderstorm Watch 667; Mesoscale Discussions 2286 and 2287; SPC today and September 11 Local Storm Reports; Weather Prediction Center Day 1 Excessive Rainfall Outlook issued 3:39 a.m. EDT; National Weather Service warning text including Peachtree City flash-flood products; National Hurricane Center public advisory on Tropical Storm Norbert (open eastern Pacific, no U.S. land threat).
This is a live Saturday morning snapshot of local storm-type events across the United States as of the early hours of Saturday, September 12, 2026. Overnight into this morning the organized severe pulse that ran eastern South Dakota into Minnesota has expired. Severe Thunderstorm Watch 666 is down. No convective watches are valid as of mid-morning UTC. The Storm Prediction Center 1300 UTC Day 1 outlook has upgraded the afternoon and evening corridor to a Slight Risk of severe thunderstorms across parts of the central and southern Plains into the Ozarks. The Weather Prediction Center Day 1 Excessive Rainfall Outlook holds a Slight Risk for portions of the Ohio Valley and Mid-Atlantic.
These are county- and ZIP-scale thunderstorms, not a mainland hurricane landfall. Restoration exposure today is large hail and damaging wind on the Plains, plus interior water where Ohio Valley and Mid-Atlantic cells train. Conditions change fast. Verify with the National Weather Service for the specific county or ZIP before you roll.
What expired overnight vs what is live this morning
Watch 666 covered southwestern into north-central Minnesota and eastern South Dakota from 6:40 p.m. to 10:00 p.m. CDT Friday. Primary language was scattered large hail, isolated very large hail to two inches, damaging gusts to 70 mph, and a tornado or two if a supercell held together early in the watch. That watch is expired. SPC current watches page as of 12:03 UTC Saturday: no watches valid. Last issued watch remains 666.
What is live this morning is the outlook, not a watch. The 0748 AM CDT Saturday Day 1 convective outlook is valid 1300 UTC Saturday through 1200 UTC Sunday. Headline: there is a Slight Risk of severe thunderstorms across parts of the central and southern Plains. Summary language: isolated to scattered severe thunderstorms capable of large to very large hail and severe or damaging winds may occur across parts of the central and southern Plains into the Ozarks this afternoon and evening. A separate Marginal Risk corridor remains over the upper Ohio Valley for isolated damaging gusts this afternoon.
WPC’s current Day 1 excessive-rainfall outlook, issued 339 AM EDT Saturday and valid 12Z Saturday to 12Z Sunday, keeps a Slight Risk of rainfall exceeding flash-flood guidance for portions of the Ohio Valley and Mid-Atlantic. Precipitable water of 2.0 to 2.25 inches is forecast to stream north along the I-95 corridor from Richmond and Washington toward Baltimore and Philadelphia by Saturday evening, then into the New York metro and lower Long Island late Saturday night. That late-night northern end of the slight risk is expected to linger into Sunday (Day 2).
Hotspot 1 — Southern Kansas, northern Oklahoma, eastern Oklahoma and Texas Panhandles into the Ozarks
This is today’s severe ticket. Elevated storms persisted overnight into early morning across southern Nebraska into eastern Kansas and western Missouri on a modest low-level jet. SPC expects that activity to weaken through the remainder of the morning, with some guidance still showing additional development along outflow across southern Kansas and northern Oklahoma. A fairly strong cold front is draped from eastern Colorado into Kansas and northwest Missouri. That boundary is the afternoon focus.
Along and south of the front, a narrow zone of moderate to strong instability (MLCAPE 2000–3500 J/kg) is forecast this afternoon from the eastern Oklahoma and Texas Panhandles into southern Kansas and northern Oklahoma. Deep-layer shear of about 30–40 kt is enough for organized updrafts. Isolated robust development along the front is favored around 21–23Z once convective temperatures are reached. Sustained supercells would pose a threat for large to very large hail, including isolated two-inch-plus stones. Higher-based convection from the eastern Panhandles into southwest and south-central Kansas and northern Oklahoma favors scattered severe downdrafts. Some gusts could exceed 75 mph. Clustering later this afternoon and evening remains uncertain, but isolated damaging wind may persist into much of Oklahoma and the Ozarks if upstream storms in Kansas and western Missouri stay organized.
Cities and counties to watch: Wichita, Hutchinson, Emporia, Liberal, and Derby in the Slight Risk core; Oklahoma City, Tulsa, and Kansas City sit in the surrounding Marginal Risk. Restoration read: hail first in the Slight Risk, then wind. Stage tarps and roof kits before mid-afternoon local. If a cell trains on the same ZIP, treat it as a water job by morning.
Hotspot 2 — Ohio Valley through the Mid-Atlantic I-95 corridor
This is today’s flood ticket, not the hail ticket. SPC keeps only a Marginal Risk of isolated damaging wind across parts of the upper Ohio Valley this afternoon in a narrow corridor of filtered heating between denser clouds over Ohio and a stationary boundary to the east. Mid-level lapse rates stay poor. The bigger operational signal is WPC. HREF signals include moderate-to-high chances of three- and six-hour flash-flood-guidance exceedance in the upper Ohio Valley, and a 20–40 percent chance of three-hour QPF over two inches from the Richmond area late Saturday afternoon, then from northeast Maryland into the Delaware Valley and southern New Jersey Saturday night. The Slight Risk was extended north through eastern Pennsylvania, northern New Jersey, and into the New York metro and lower Long Island, with that northern end weighted late Saturday night into Sunday.
Cities and counties to watch: Pittsburgh and western Pennsylvania, northern West Virginia, the upper Ohio Valley; Richmond, Washington, Baltimore, Philadelphia, northern New Jersey, New York City, and lower Long Island on the late-day and overnight rain axis. Restoration read: urban street flooding, low crossings, and wet drywall where cells train. The 24–48 hour mold clock starts when water is inside, not when the outlook expires.
Hotspot 3 — Just-hit Upper Midwest and leftover Arizona water
Friday evening’s Slight Risk over far eastern South Dakota into Minnesota verified locally. Preliminary Storm Prediction Center local storm reports for the 1200 UTC Friday to 1159 UTC Saturday window include a tornado touchdown reported seven miles northeast of Artichoke in Stevens County, Minnesota, around 0051 UTC, plus downed power poles eight miles south of Alberta on County Highway 9. Golf-ball hail (1.75 inches) was reported east and south of Artichoke and south of Alberta. Half-dollar hail fell near Dumont, Herman, Norcross, and Toronto, South Dakota. Wind damage and trees on lines were reported around Chokio, Embarrass and Britt in St. Louis County, Whipholt and Longville in Cass County, and Blue Grass in Wadena County, with one report noting possible tornado damage and large trees blocking County Road 23.
Separate Friday hail and wind clusters hit Tarrant County, Texas (Arlington and Mansfield, golf-ball hail and trees and poles down), Bexar County, Texas after 0310 UTC (golf-ball hail near Converse), and a long tree-down corridor through South Carolina, North Carolina, and Virginia. Arizona flash-flood warnings fired Friday evening over Gila, Coconino, Navajo, Cochise, and Graham Counties, including fire-scar drainages. Those Arizona warnings were evening products; treat them as just-hit water, not today’s new Slight Risk.
Just hit
Minnesota and eastern South Dakota are yesterday’s tickets: hail, trees, poles, and at least one reported tornado touchdown that still needs a damage survey, not a new watch. North Texas and San Antonio-area hail are Friday afternoon and overnight work already on the books. The Carolinas and southern Virginia tree-down scatter is the same. Today’s new work, if it verifies, is the Kansas–Oklahoma hail and wind corridor plus localized flash flooding from the Ohio Valley onto the Mid-Atlantic I-95 axis tonight.
Pulse table
Region
Main threats
SPC / NWS / WPC level
Status this morning
Southern KS / northern OK / Panhandles / Ozarks
Large to very large hail, damaging wind, isolated 75+ mph gusts
SPC Slight (core) + Marginal surround
Outlook live; no watch yet
Upper Ohio Valley
Isolated damaging wind; heavy rain / flash flood
SPC Marginal + WPC Slight ERO
Afternoon increase
Mid-Atlantic I-95 (RIC–DC–BAL–PHL–NYC)
Training heavy rain, urban flash flood
WPC Slight ERO
Late afternoon through Saturday night
Eastern SD / west-central and northern MN
Hail, trees, poles, reported tornado
Watch 666 expired 10 p.m. CDT Fri
Aftermath / just-hit
North Texas / San Antonio metro
Friday hail and wind
Local LSRs
Aftermath
Southeast AZ fire scars / washes
Flash flood from Friday cells
Expired FFWs
Aftermath
Atlantic / Gulf vs. U.S. mainland
No landfalling tropical cyclone
NHC: formation not expected next 7 days in Atlantic
Quiet on the mainland coast
What this means for restoration teams
Two-inch hail is roof and auto glass work in the Slight Risk counties. Gusts of 60–75 mph are siding, gutter, and tree-on-structure work. A reported tornado near Artichoke, Minnesota, is a narrow swath — staff it as a local damage survey, not a regional event. Ohio Valley and Mid-Atlantic heavy rain is wet drywall and a same-night extraction clock if water is inside. Do not send the same crew to Wichita hail and Pittsburgh flooding without checking which county actually has a warning now.
For teams in or near the Kansas–Oklahoma 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.
What this is not
This is not a regional derecho and not a U.S. mainland hurricane landfall. National Hurricane Center Atlantic outlook at 800 AM EDT Saturday: tropical cyclone formation is not expected during the next seven days. Eastern Pacific Tropical Storm Norbert is well west-southwest of the southern tip of Baja California and is not a U.S. land threat. The work today, if it comes, will be scattered: a hail swath through a Kansas or Oklahoma county, a wind-thrown tree in the upper Ohio Valley, a flooded underpass where Mid-Atlantic cells train. That is the local-storm pattern this desk should staff.
Looking ahead
SPC Day 2 is a Marginal Risk Sunday afternoon and evening from western New England through the upper Ohio Valley for small to marginally severe hail and locally damaging gusts. Day 3 is also Marginal. Fire-weather outlooks are Elevated today and Sunday. The next Day 1 convective outlook is scheduled by 1630 UTC. Watch the afternoon Storm Tracker update rather than assuming this morning’s Slight Risk is the last line of the weekend.
Sources and how to verify
Primary sources: NOAA Storm Prediction Center Sep 12, 2026 1300 UTC Day 1 Convective Outlook (issued 0748 AM CDT); SPC current watches page (no watches valid; most recently issued Watch 666); SPC preliminary local storm reports for 20260911 1200 UTC–20260912 1159 UTC; Weather Prediction Center Day 1 Excessive Rainfall Outlook issued 339 AM EDT Sat Sep 12, 2026; National Hurricane Center Atlantic Tropical Weather Outlook 800 AM EDT Sat Sep 12, 2026; National Weather Service watch/warning text feed.
Companies already lived through bring-your-own-device. The next one is bigger: bring your own fleet. When you hire someone now, you are not just hiring the person. You are hiring their output capacity — and output capacity includes their AI stack.
Two candidates with identical skills and different agent setups are not the same hire. Not close. The resume cannot express any of this. So the interview has to change.
A personal fleet and a company bot only talk after the walls are drawn.
Bring your own fleet. A personal set of AI agents — seats, tools, workflows, integrations, and data walls — that a candidate already runs. In a fleet interview, that stack does a capability handshake with the company’s operations bot, then both sides run a small piece of real work before an offer letter exists.
What is bring your own fleet?
Bring your own fleet is the hiring version of bring-your-own-device. The candidate does not show up as a lone operator with a laptop. They show up with the agents that already produce their work: research seats, writing seats, ops seats, and the filters between them.
I have been building mine this way for months. One seat that knows who I am. Separate seats that know what I do. A filter between them. That is not a product pitch. It is the only setup I would let near a company bot. The shop-floor version of the same idea already lives on this site: Cursor checking in on Grok Desktop mid-job is a fleet, not a chat window.
Why can’t a resume show an AI stack?
A resume can list tools. It cannot prove throughput. It cannot show which seats talk to which systems, where the walls sit, or what happens when a task is live instead of described. “Uses ChatGPT” and “runs a governed agent fleet” look the same on paper. They are not the same on a desk.
That is why the old screen fails first. Degree filters, keyword screens, and whiteboard puzzles all ask the candidate to narrate capacity. Narration is cheap. A fleet that can sit down with an operations bot and do a slice of the actual job is not.
How does an AI fleet interview work?
The human intro still happens. Then the agents talk. Your personal AI sits down — figuratively — with the company’s operations bot and they do a capability handshake.
What seats do you run?
What tools, integrations, workflows, and data assets?
What throughput can you demonstrate on a bounded task?
Where are the boundaries — what can each side touch, and what stays behind a clean wall?
Then the part that kills the whiteboard interview: instead of a coding puzzle, the two fleets run a small piece of real work together. The trial task is the interview. You do not describe what you could do. The work gets done, live, before the offer letter exists.
Old interview
Fleet interview
Resume plus degree screen
Working system as the portfolio
Whiteboard or take-home puzzle
Bounded live trial on real work
Claims about tools
Capability handshake: seats, walls, throughput
Trust the story
Watch the output, then talk terms
What is an agent clean room?
An agent clean room is a verified wall between the personal seat and the work seats. The personal agent translates. It does not cross over. It must never leak a private life into an employer system. Without that wall, no sane person lets their agent near a company bot.
This is AI hygiene, not a slogan. The same discipline we write about when agents share a WordPress lock or a night shift: one owner, one wall, one recovery path. See Four Agents, One WordPress Lock and the operator note in Wire and Fire Guys. A handshake without a clean room is just another attack surface with a friendly name.
Why does the fleet beat the diploma?
I do not have a degree. In the old world, that is a filter that screens me out before a human ever reads my name. In the handshake world, it is irrelevant — because “here is my working system, watch it do the job” beats “here is my diploma, trust that I could learn the job” every time. The fleet is the portfolio.
That is not an argument against school. It is an argument against using school as a proxy for output you can now watch. If the trial task is real work, the credential becomes a footnote.
What breaks first if companies try this?
The objections land fast, and they are honest.
Ownership. Who owns the workflows when a personal fleet plugs into an employer? You built it on your own time. It now runs their playbooks. That is the “who owns your work laptop” fight, upgraded. Nobody has a settled answer.
Security. Their bot talking to your agent is an attack surface in both directions. The clean room has to be verifiable, not promised.
Offboarding. When you leave, what stays running and what takes the employer’s data with it? Offboarding for agents does not exist yet.
Trust. How does their bot trust your capability claims? Trial tasks help. Claims are cheap. Demonstrated throughput is not.
You do not wait for a protocol to be ratified before you build the wall. The pieces are already here: the seats, the clean room, the trial task. Somebody is going to ship the first version of this. It might as well be someone who already runs their life this way.
What we would not claim
That a standard for agent handshakes already exists. It does not.
That every role should interview this way tomorrow. High-stakes, high-output knowledge work is the first fit.
That a personal fleet is automatically safe to plug into a company. Without a clean room, it is not.
That this replaces human judgment. The human intro still happens. The fleet only replaces the part of the interview that was already theater.
FAQ
What is a capability handshake in hiring?
A capability handshake is a structured exchange between a candidate’s personal agents and an employer’s operations bot. Both sides declare seats, tools, integrations, data walls, and what they can touch. The point is not a demo script. It is a map of capacity and boundaries before any live work starts.
Is bring your own fleet the same as bring your own device?
No. BYOD was hardware and a policy packet. Bring your own fleet is software labor: agents that already produce work. The risk is not a lost laptop. The risk is a personal agent leaking private context into an employer system, or an employer workflow walking out inside a personal seat.
Do you need a degree if the fleet is the portfolio?
Not for the screen that used to happen before a human read the name. A degree can still signal training. It cannot substitute for a working system that completes a bounded trial task in front of both sides.
How do you keep a personal AI out of company data?
Separate seats. One identity seat that never joins the employer handshake. Work seats that only see what the clean room allows. A filter that translates tasks instead of forwarding raw personal context. If you cannot show that wall, you should not plug in.
This is not a weekly recap. It is the receipt for three things that actually failed or got patched in the last seven days. The sources are the Tygart Ops cards, not a brainstorm. GitHub org TygartMedia did not move this week. The breaks lived in WordPress, nginx, and a parked hang.
The clips were not YouTube. They were us.
We reused a guest appearance onto Restoration Intel. The article went live. The YouTube embed was fine. The inline MP4s were not. First pass through the REST write path, the files came back grainy at roughly 432 pixels, 56 to 138 kb/s. Easy to blame the source kit. It was not the source kit.
Nginx on the knowledge-cluster box still has client_max_body_size 1m. That is a Pinto leftover. Fat uploads 413. The agent did what agents do when the pipe is too small: it re-encoded until the file fit. That is how you get a square clip that looks like it was filmed through a sock.
The patch on the post itself was a one-off chunked replace. Live MP4s now SHA-256 match the kit files. 1080 by 1080. 6.57 to 19.02 MB. The article is correct. The box is not. Future fat REST uploads will 413 until someone sets nginx to 32m and PHP upload/post to at least 32M on that VM. We are not standing up a helper plugin to hide the limit.
If you run self-hosted WordPress and an agent write path, check the body size before you ship media. The 413 does not always surface as a clean error. Sometimes it surfaces as a “successful” upload of a crushed file. That is worse than a hard fail. The hard fail makes you stop. The squash makes you publish junk and argue about cameras.
Twin slugs are not a content strategy.
Tygart Media had two leftover Claude URLs sitting next to the live desks. /claude-ai-pricing-2/ and /latest-claude-models/. Both already noindex, both already carrying a canonical. That is the polite way to leave a mess. Search engines still find twins. Agents still cite twins. Operators still edit the wrong one.
On 8 September the 301/302 lane moved to Pinto. The card closed this week after the live check: /claude-ai-pricing-2/ now 301s to /claude-ai-pricing/, and /latest-claude-models/ 301s to /current-claude-model-version/. WP Admin noindex matches what the connector sees. Done-when was both twins 301, not “we will canonical our way out of it.”
The standing rule on that card is the useful part. Do not mint a third pricing URL. The citation desks already fight each other when the official numbers move. A third slug is how you get two agents writing two patches to two pages that should have been one page. If the model page needs a new title, change the title. Do not clone the URL and hope Rank Math sorts the family later.
Redirects are cheap. Duplicate living pages are not. A 301 is a patch. A second slug with a canonical tag is a shrug.
The home page still does not point at the guide.
On a restoration site we own the work on, the home body is supposed to send “water or fire damage” to the live guide-2 URL. Pre-check on 11 September at about 8:30 AM PT: home guide-2 hrefs equaled zero. The water hub already had the link. The hubs were 200. H1 count was 1. The older -2 and -3 redirects to guide-2 were holding. Home was the hole.
The hang got assigned. Then it got parked the same morning, about 11:39 AM PT, behind a session wall. Status on the card reads Done because the hang was parked, not because the link exists. Home still has zero guide-2 hrefs. Resume only on a re-assign. Hurricane and flood 404s stay parked behind it.
That is the kind of break that does not page anyone. The site is up. The guide is up. The money phrase on the home page just does not go where the rest of the architecture already goes. Crawlers will keep scoring the hub. Humans who land on home will keep missing the desk you already built. Interlink work that stops at the interior pages is half a patch.
We do not name the client beyond the internal slug. The lesson does not need the name. If the home widget is the last place the live URL should appear, treat a zero-count pre-check as an outage, not as a nice-to-have in the daily hang loop.
One thing we will not repeat
We will not treat a successful media write as proof the file is the file. The RI clips “uploaded.” They were the wrong bytes. SHA-256 against the kit is the check. Visual vibe is not the check. “It posted” is not the check.
Same class of mistake as minting -2 slugs when the first URL is still live. The system accepted the write. The system did not protect the shape of the library. Operators have to put the hash and the 301 in the done-when, or the agent will keep delivering a green card with the wrong object behind it.
The patch still open
Nginx on the Restoration Intel box is still 1 MB. That is the open patch. The article is fixed. The next fat REST upload is not. 32m on nginx and 32M on PHP upload/post is the actual close. Until that lands, every media write on that VM is one leftover limit away from another squash.
Second open, different box: a traffic spike on the knowledge cluster around 1:51 PT. The card says about 2,487 requests per hour and nine wp-login POSTs. The instruction on the card is a read-only log pull and a one-paragraph verdict. No firewall change, no plugin change, no credential change without a named gate. That card is still not started. A spike is not automatically an attack and it is not automatically “leave it.” It is a log plus a verdict. Until the verdict exists, it stays an open patch, not a story.
GitHub this week added nothing to the picture. Org repos last moved in July and August. No commit lane, no issue lane worth citing. The week’s failures were in the CMS and the reverse proxy, which is where most of this operation actually lives.
Shipped this week on the public site was other work: citation desks, storm desks, a Canva template read, a Mastheads changelog note. None of that is this post. This post is the three cards that broke or got taped. The clips match the kit now. The twin Claude URLs 301. Home still does not point at the guide. The 1 MB limit is still sitting on the box that will eat the next file.
Most restoration contractors are invisible where it now matters most: inside the AI answers. When a facility manager asks Copilot who to call for a commercial loss, the model does not scroll your homepage. It cites whoever taught it the cleanest sentence.
Your website does not need more traffic. It needs to be the answer. Zero-click search already took the click. The remaining win is being named inside the answer itself. That is a different game than ranking a page, and most agencies are still scoring the old one.
Cited answer. A cited answer is the short, checkable sentence an answer engine lifts into Copilot, ChatGPT, Perplexity, Gemini, Bing Copilot, or a Google AI Overview and attributes to a URL. Traffic is optional. The attribution is the asset.
Why are restoration contractors invisible inside AI answers?
Commercial buyers no longer start with a ten-blue-link session. They type the job into an assistant: who handles a sprinkler discharge on a mid-rise, what a drying standard actually requires, whether a vendor is after-hours in this metro. The model answers from pages that already look like briefings.
Most contractor sites still look like brochures. Hero image. Five service tiles. A form. A blog post that restates the service name. There is no 40-to-60-word answer under the question the buyer asked. There is no timetable, no definition, no named protocol. The model has nothing safe to lift, so it lifts a national franchise FAQ, an insurer explainer, or last year’s trade-press roundup.
What did a 20-page race guide teach us about citations?
Race weekend in Madrid. We published a small independent visitor guide at racemadrid.com — twenty static pages, Spanish primary, English secondary, no ticket shop. Through 8 September 2026, Bing Webmaster showed 144 clicks and 3,218 AI citations. On 8 September the model quoted the site 55 times for every human click.
Same playbook we run for restoration companies: be the clearest answer to the question the buyer is actually asking. A facility manager after a loss is in the same posture as a traveler the night before a sold-out race. They do not want your brand story. They want the next true sentence.
How is that different from SEO?
SEO still matters. It is the foundation that lets a URL exist, resolve, and get fetched. AEO is how a featured snippet or People Also Ask box can lift a clean block. GEO is how a generative engine decides you are safe enough to speak for. We treat them as concentric layers on one page, not three rewrites. The operator version of that stack is in What Is GEO? and in what GEO delivery looks like inside a real engagement.
Layer
Question it answers
What you ship
SEO
Can the engine find and trust the URL?
Title, meta, headings, first-100-word keyword, internals, schema that is true
AEO
Can a snippet lift one block without rewriting you?
Question H2, 40–60 word answer, FAQ, definition box
GEO
Will a model cite you when a buyer asks in chat?
Checkable facts per paragraph, entity names, dates, sources, bilingual or local variants when the buyer uses them
If you only measure sessions, you will call a 55-to-1 citation ratio a failure. If you measure whether the model will say your name when a facilities director asks who to call, that ratio is the product.
What does the restoration version of a cited answer look like?
It looks like a briefing, not a pitch. The H2 is the question. The next paragraph answers it in plain language, with a number or a standard attached. Then the proof: what you do on site, what you do not do, the metro you actually cover, the clock you keep.
Who to call after a commercial sprinkler discharge in this building class, after hours.
How long a category of water stays a drying job before it becomes a rebuild conversation.
What the carrier packet has to include on day one so the file does not stall.
Which document the facility manager should send before the first truck rolls.
Write those as answers a model can quote without inventing a second sentence. Put the misspellings and the local names on the page on purpose. Madrid taught us that travelers cannot spell a new circuit. Facility staff cannot spell your d/b/a either. Cover the words they type.
What is a citation worth if nobody clicks?
On the race guide, a citation is proof of position. It is not a ticket sale. We said that in the field note and it stays true here. A restoration citation is worth more than a travel citation only if you already own the next step: the phone, the after-hours board, the approved-vendor list, the estimator who can take the job tonight.
If the sentence the model lifts is wrong, the citation is a liability. We locked a Sunday start time off an older F1.com page and the official MADRING time was later. That error is still the most-clicked kind of question in the logs. The next hour of work is not a new URL. It is correcting the fact the model already trusts. Restoration pages have the same failure mode: an outdated response-time claim will travel farther than the correction.
What we would not claim
That 144 Bing clicks is a media business.
That citations replace Google. The Madrid export is Bing Webmaster plus Clarity. Google Search Console is a separate pile.
That being cited is automatically good. It is good if the fact is right and you have a use for the attention.
That this article invents a new discipline. SEO, AEO, and GEO are already named on this site. This is the operator sentence we are willing to put on LinkedIn and stand behind.
What we would do again
Show up early on a named question that does not have a settled official FAQ. Write the buyer’s language, not the agency’s. Keep the page short enough to finish. Put the clock in one place and keep it tied to a source you can defend. Do not invent a content brand around a weekend — or around a single storm.
The models will quote you if the sentence is plain. The humans who still click will click the schedule, the response protocol, the packing list. Everyone else will take the answer and move. Your job is to be the sentence they take.
FAQ
What is the difference between AEO and GEO?
AEO — Answer Engine Optimization — structures a page so a featured snippet, People Also Ask box, or voice result can lift a complete answer. GEO — Generative Engine Optimization — structures the same page so a generative model will cite that URL when a person asks in chat. One page. Two retrieval systems.
Does zero-click search mean a restoration website is useless?
No. It means the homepage-as-brochure is the wrong artifact. The useful site is a set of briefings the model can quote and the buyer can still open when they need the packet, the photo standard, or the after-hours number.
How do you know a page is being cited?
You measure it on more than one desk. Bing Webmaster now reports AI citations. Clarity shows whether the humans who still arrive actually read. Prompt checks in Copilot, ChatGPT, Perplexity, and Gemini tell you whether the brand is named. We keep the method on AI citation monitoring and on the Bing citation mining thesis.
Is this only for restoration companies?
No. Restoration is the vertical where a missed answer has a wet building attached to it. The same pattern holds anywhere a buyer asks an assistant a time-sensitive operational question and needs a named next step.
Sources: Will Tygart, Tygart Media, Tacoma, WA, 11 September 2026. First-party Bing Webmaster and Microsoft Clarity figures for racemadrid.com through 8 September 2026, as published in the Madrid field note. Related Tygart pages: restoration AI visibility, GEO explainer, GEO delivery.
This is a live Friday afternoon snapshot of local storm-type events across the United States as of Friday, September 11, 2026. The organized pulse is still ahead of most radar cores: the Storm Prediction Center 2000 UTC Day 1 Convective Outlook keeps a Slight Risk of severe thunderstorms across the Upper Midwest for late this afternoon and tonight. No convective watches are currently valid. Mesoscale Discussion 2281, issued 1937 UTC, flags a lower-end damaging-wind threat over parts of southern Virginia and northern North Carolina with watch issuance unlikely. The Weather Prediction Center holds a Slight Risk of excessive rainfall in far southern Arizona and northern Minnesota.
These remain county- and ZIP-scale thunderstorms, not a mainland hurricane landfall. Tropical Storm Norbert is in the Eastern Pacific well west-southwest of Baja California and poses no threat to U.S. land. Restoration exposure this afternoon is wind, water, hail, and trees: large hail and damaging wind in the Minnesota–northeast South Dakota Slight Risk, isolated wind in the Virginia–North Carolina scatter, flash-flood rates in northern Minnesota and Santa Cruz County, Arizona, plus residual hail and pole work from last night’s Texas Panhandle event. Conditions change fast. Verify with the National Weather Service for the specific county or ZIP before you roll.
What is live this afternoon
No severe thunderstorm or tornado watches are in effect as of the SPC watch page update Friday afternoon. The most recently issued watch remains Watch 665 from earlier in the week. Today’s official Local Storm Reports page (1200 UTC Friday through 1159 UTC Saturday) still shows no new tornado, hail, or wind reports in that window. Last night’s reports sit on the September 10 LSR page.
SPC’s 2000 UTC Day 1 outlook (forecaster Wendt, issued 0300 PM CDT) is mostly on track from the morning package. Scattered severe thunderstorms capable of large hail (some 2+ inches), damaging winds, and a couple of tornadoes are expected late this afternoon and tonight across parts of the Upper Midwest. Initiation farther south into the central Plains remains more uncertain and conditional. Marginal wind/hail probabilities were extended into more of central Kansas for overnight conditional storms as the cold front reaches northern Kansas Saturday morning.
WPC’s Day 1 Excessive Rainfall Outlook (updated 1601 UTC, valid 16Z Friday–12Z Saturday) keeps Slight Risk language over far southern Arizona and northern Minnesota. The 16Z update expanded a Marginal Risk eastward across more of the Florida Panhandle for 1–2+ inch local rates. Mid-South, Tennessee Valley, central Gulf Coast, and Southern Appalachians stay in the more widespread thunderstorm/flash-flood conversation at Marginal intensity.
Hotspot 1 — Upper Midwest Slight Risk (northeast SD into western and northern MN)
This is still the primary organized severe corridor. A mid-level shortwave and cold front support a narrow corridor of 60s F dewpoints, moderate destabilization, and 35–45 kt of deep-layer shear. Initial supercells favor large hail, isolated 2+ inches possible. Mode should trend toward clusters and bowing segments this evening as the low-level jet strengthens, shifting the main hazard toward damaging wind. A couple of tornadoes remain in the official language if any cells stay semi-discrete into early evening. The wind threat is expected to wane with eastward extent into western Wisconsin late tonight as the instability corridor stays narrow.
Cities and counties to watch: Watertown and Aberdeen vicinity in South Dakota; Willmar, St. Cloud, Fergus Falls, Brainerd, Hibbing, Duluth, and the Minnesota Arrowhead. Restoration read: hail first, then wind and trees after dark. Stage roof tarps, generators, and tree crews on the Minnesota side of the Slight Risk before evening clustering. Photograph only in remaining daylight if it is safe.
Hotspot 2 — Southern Virginia and northern North Carolina (MD 2281)
Mesoscale Discussion 2281 (valid 1937–2200 UTC) covers parts of southern Virginia and northern North Carolina. A stationary boundary from far northeastern North Carolina into south-central Virginia is the focus. Moderate surface-based buoyancy and steepening low-level lapse rates support loosely organized clusters capable of locally damaging gusts of 55–70 mph and isolated/marginally severe hail up to about 1.25 inches. Watch probability is 20 percent — watch unlikely.
Offices in the attention line: AKQ, MHX, LWX, RAH, RNK. Restoration read: treat this as scattered wind and tree work, not a regional line. One strong cluster can still drop a tree on a service drop or peel a section of roof. Do not staff it like Watch 665 from Wednesday.
Hotspot 3 — WPC flood pockets: northern Minnesota and far southern Arizona
The same shortwave that supports the Upper Midwest Slight Risk also carries a WPC Slight Risk of excessive rainfall over northern Minnesota. Official discussion cites precipitable water in the upper climatological percentile, possible training near the warm front, 1–2 inches (locally up to 3 inches), and rates approaching 1.5 inches per hour Friday afternoon and evening.
Far southern Arizona, especially the Santa Cruz County corridor, remains the other Slight Risk flood pocket on monsoon moisture with precipitable water above 1.5 inches. HREF guidance earlier today showed moderate-to-high chances of 3-hour QPF exceeding flash-flood guidance there. The Florida Panhandle was added to the broader Marginal flood language on the 16Z update for coastal 1–2+ inch rates.
Restoration read: northern Minnesota can be a dual ticket — hail/wind plus interior water if cores train. Southern Arizona is a flash-flood and poor-drainage desk. Florida Panhandle is localized urban flooding, not the national headline.
Just hit
Thursday evening into early Friday remains the live claim pile. Official September 10 LSRs include 2.25-inch hail near Lake Tanglewood and 2.00-inch hail at Timbercreek Canyon in Randall County, Texas; 1.75-inch and 1.25-inch stones around Lake Tanglewood and Pantex; an 87 mph thunderstorm gust 1 SE of Colby, Thomas County, Kansas; 67 mph near Pantex; 65 mph at Plainview, Hale County, Texas, with snapped power poles, an overturned construction trailer, damaged vehicles, and fences down; plus additional 60–62 mph gusts on the Texas South Plains. Residual high-water work from overnight Flash Flood Warnings in north-central West Virginia and southeastern Ohio is still on yesterday morning’s books.
No Atlantic tropical cyclone is present. NHC’s 200 PM EDT Friday Tropical Weather Outlook states tropical cyclone formation is not expected in the Atlantic, Caribbean, or Gulf of America during the next 7 days. Tropical Storm Norbert, 65 mph as of the late-morning Eastern Pacific package, is moving west well offshore and is not a U.S. land threat.
Pulse table
Region
Main threats
SPC / NWS / WPC level
Status this afternoon
NE SD / western & northern MN
Large hail (2+” possible), damaging wind, couple tornadoes
SPC Slight
Late afternoon–tonight
Southern VA / northern NC
Locally damaging gusts 55–70 mph, isolated hail
MD 2281, watch unlikely
Remainder of afternoon
Northern MN / far southern AZ
Flash-flood rates, training possible in MN
WPC Slight
Afternoon–evening
TX Panhandle / Colby KS
Hail to 2.25″, 60–87 mph gusts, poles/vehicles
Sept 10 LSRs
Just-hit / recovery
Central Plains / central KS overnight
Conditional hail/wind
SPC Marginal (expanded 20Z)
Evening–overnight if storms fire
Mid-South / TN Valley / Carolinas
Pulse damaging gusts, heavy rain
SPC Marginal
Scattered
Atlantic / Gulf vs. U.S. mainland
No landfalling tropical cyclone
NHC: no TC next 7 days
Quiet
What this means for restoration teams
The Texas Panhandle and Colby, Kansas, hits are already tickets: hail roofs and vehicles in Randall and Carson counties, wind-driven pole and debris work around Plainview and Colby. Today’s new work, if it verifies, is the Upper Midwest Slight Risk after peak heating — hail swaths first, then tree-and-wire clusters. Northern Minnesota can add interior water on the same shift. Virginia–North Carolina is a local wind desk, not a watch-scale deployment.
Stage Minnesota tarps and tree crews before dark. Property owners should photograph damage in daylight if it is safe, call the carrier, and start extraction the same night if water is inside. Do not send the same crew to both the Minnesota Slight Risk and last night’s Texas recovery without checking which county actually has a warning now.
What this is not
This is not a regional derecho and not a U.S. mainland hurricane landfall. There is no live tornado or severe thunderstorm watch as of this afternoon package. The work tonight, if it comes, will be scattered: a hail swath through a Minnesota or South Dakota county, a wind-downed tree in southern Virginia, a flooded wash in Santa Cruz County, Arizona, or leftover pole work in Hale County, Texas. That is the local-storm pattern this desk should staff.
Looking ahead
Saturday’s Day 2 Convective Outlook (1730 UTC, forecaster Jewell) drops to Marginal over parts of the Central Plains and from Ohio and West Virginia into western Pennsylvania. Widely scattered strong-to-severe storms are possible Saturday afternoon and evening over parts of the Central Plains, with isolated activity also possible in the Upper Ohio Valley. Critical fire-weather conditions remain in today’s fire outlook. Watch the next Storm Tracker update rather than assuming the Upper Midwest Slight Risk is the last line of the week.
Sources and how to verify
Primary sources: NOAA Storm Prediction Center Day 1 Convective Outlook issued 2000 UTC Friday, September 11, 2026; SPC Mesoscale Discussion 2281 issued 1937 UTC; SPC current watches page (no watches valid); SPC Local Storm Reports for 11 September (none in the new 12Z window as of this writing) and 10 September (Texas Panhandle and Colby, Kansas); Weather Prediction Center Day 1 Excessive Rainfall Outlook updated 1601 UTC; National Hurricane Center Atlantic Tropical Weather Outlook 200 PM EDT Friday; Eastern Pacific package on Tropical Storm Norbert. Morning desk on the same calendar day: Friday morning Storm Updates.
Last verified: September 11, 2026 (Pacific). Source: Canva product email to will@tygartmedia.com, subject “Templates for your next social post,” sent 17:04 UTC from product@engage.canva.com. Visible copy in the message: “New templates recommended just for you.” Tracking wrappers from the vendor mail are not linked here. Public product surface: canva.com. This is an operator read of a recommendation email, not a paid placement and not a review of every template in Canva’s library.
Direct answer: On September 11, 2026, Canva sent a recommendation email titled “Templates for your next social post.” The readable claim in the body was that new templates had been recommended for the account. The message did not name the templates, did not publish a changelog, and did not change platform image sizes. A Canva template is a starting canvas with a locked aspect ratio. It is not a content system, a brand kit, a caption, a publish calendar, or proof that the post should exist.
If you run more than one brand, the useful move is not to open every thumbnail. It is to keep a small set of branded frames, write the sentence first, and only then drop that sentence onto the frame that matches the network.
What the September 11 email actually said
The subject line was “Templates for your next social post.” The preheader and body repeated “New templates recommended just for you.” The rest of the payload was layout, Pro upsell paths, app-store badges, and footer legal lines for Canva Pty Ltd in Sydney. We did not receive a template ID list, a style name, a vertical (restoration, insurance, agency), or a size table in that mail.
That is enough to date the event. It is not enough to write a template roundup. Do not invent names for designs we did not open. Do not treat a recommendation engine as a product launch. Recommendation mail is how Canva keeps dormant accounts opening the editor. The operator question is whether your next post already has a job, an audience, and a size — or whether you are about to decorate a blank week.
What a social template is allowed to do
A template earns its keep when it encodes three decisions you would otherwise remake every time: canvas size, type hierarchy, and safe zones. Everything else is costume. Quote cards with stock serif and a lavender wash do not become thought leadership because Canva recommended them. They become more of the same feed.
Keep the frame. Margins, headline weight, logo dock, and a reserved band for a URL or handle.
Throw out the dummy copy. Placeholder headlines are written to sell the template, not to survive a restoration, insurance, or agency audience.
Swap the palette before the first export. If the file still uses Canva’s demo colors, it is not on-brand yet.
Export once per network. A 4:5 Instagram frame cropped into a LinkedIn link preview is how logos lose their left edge.
Sizes that still matter in September 2026
Platform crop rules move. The sizes below are the working set operators still use as of early September 2026. Recheck the live composer before a paid boost. Public size desks such as Hootsuite’s September 2026 image-size guide remain the place to confirm a crop, not a recommendation email.
Instagram feed. 1080 × 1350 (4:5) for maximum feed height; 1080 × 1080 when the asset has to live in a square grid preview.
Instagram Stories and Reels, TikTok, Stories on Facebook. 1080 × 1920 (9:16). Keep type out of the top and bottom action bars.
LinkedIn feed image. 1200 × 1200 is the safe square. Link previews and single-image ads still lean 1200 × 627.
Facebook and Open Graph share cards. 1200 × 630 remains the link-preview default.
X post image. Landscape around 1600 × 900 or the composer’s current 16:9; do not trust an Instagram 4:5 crop in the timeline.
YouTube thumbnail. 1280 × 720. That is a different job than a feed post.
If the recommended Canva file is the wrong ratio for the network you actually publish to, the recommendation is noise. Resize the canvas first. Do not stretch type to fit.
The operator stack: sentence, frame, kit, queue
Tygart runs social as a queue, not as a design hour. Canva is the compositor. Metricool (or the scheduler you already pay for) is the clock. The CMS is the source of the sentence. Reverse that order and you get pretty files with nothing to say.
Write the one sentence the post has to survive as a citation. If an answer engine quoted only that line, would it still be true?
Pick the network and the size from the list above. Do not start in “Instagram Post” because that is Canva’s default.
Open a brand kit, not a trending template. Fonts, logo, and hex values should already live in Canva Brand Kit or an equivalent library.
Drop the sentence into the headline band. Caption and alt text are written in the scheduler, not inside the PNG.
Export PNG or MP4 at 1× the target pixels. Do not upscale a 1080 file to look sharper on LinkedIn.
Queue the file next to the source URL. A graphic that cannot point back to a dated page is decoration.
Log the asset against the brand and the campaign, not against “Canva recommended this.”
That last step is the difference between a template habit and a system. Recommendation mail wants you to open the editor. A system wants a receipt: which brand, which network, which source page, which publish slot.
AEO, SEO, and GEO on a social graphic
A feed image is a weak citation target. The page behind it is the durable one. Use the graphic to carry a claim the long page already proves.
AEO. Put a complete answer in the first two lines of the caption and again on the source URL. Answer engines quote sentences, not layouts. “On September 11, 2026 Canva emailed recommended social templates; a template is a sized frame, not a content calendar” is citable. A gradient quote card is not.
SEO. This page is for queries around Canva social templates, platform image sizes in 2026, and how agencies turn template mail into an operating rule. Rank Math title and meta stay under the usual length caps. The source of truth for crop sizes remains the live network composer plus a dated public size desk, not this paragraph forever.
GEO. Name the vendor (Canva), the sender domain (product@engage.canva.com), the date, the subject line, and the operator (Tygart Media). Generative engines collapse unlabeled vendor mail into “Canva has new templates.” Entities stop that collapse. Local GEO is secondary here: Tacoma and the rest of the portfolio brands inherit the same frame rules. City pages do not make a square post rank in Maps.
What not to do with a recommendation email
Do not publish the tracking URLs from the mail. They are click wrappers, not documentation.
Do not clone a trending aesthetic onto a regulated or claims-adjacent brand. Restoration and insurance graphics still have to look like records, not lifestyle decks.
Do not treat Canva Magic Studio output as a sourced claim. Generate the layout. Write the fact from the desk that owns it.
Do not build a new template for every idea. Four frames per brand — square, 4:5, 9:16, and 1.91:1 — cover almost every publish path we actually use.
Do not skip alt text. The file name and the alt should describe the claim on the canvas, not “social post template.”
Quality notes
We did not click through the recommended set in this mail, so this page does not list template titles, preview art, or a Pro-versus-free split for those specific files. Canva’s library changes continuously. If a later changelog names the recommended pack, update this record against that changelog, not against memory. Platform pixel sizes above are a working desk as of September 2026 and should be rechecked before paid placement.
What did Canva email Tygart Media on September 11, 2026?
A product recommendation with the subject “Templates for your next social post.” The visible body line was “New templates recommended just for you.” It did not include a named template list or a size table.
Are Canva social templates enough to run a content program?
No. A template is a sized frame with type hierarchy. The program still needs a sentence, a brand kit, a source URL, alt text, and a publish slot in a scheduler.
What image size should I use in Canva for Instagram in 2026?
Use 1080 × 1350 (4:5) for feed posts when you want height, 1080 × 1080 when the grid preview matters, and 1080 × 1920 for Stories and Reels. Confirm the live Instagram composer before a paid boost.
What image size should I use in Canva for LinkedIn?
1200 × 1200 for a standard feed image. 1200 × 627 for link previews and many single-image ads. Do not reuse a tall Instagram 4:5 export as a LinkedIn link card.
Should I click the links inside a Canva recommendation email?
Only if you need the editor. Those URLs are engagement wrappers. Documentation and size rules belong on public pages such as canva.com and a dated image-size desk, not on a tracking redirect.
How many Canva templates does a multi-brand operator actually need?
Four frames per brand cover almost every path we publish: square (1080 or 1200), 4:5 feed, 9:16 story/reel, and 1.91:1 link preview. More templates usually mean more costume, not more output.
The best product in claims is not another adjuster dashboard. It is the thing that shows the short-pay before the shop or the homeowner closes the file.
That is not a slogan. It is how Texas SB 458, new Washington claims-handling rules, and the sudden cheapness of vertical agents rhyme. Three different surfaces. One failure mode. Nobody owns the photo set or the estimate map, so nobody demands the appraisal or the supplement in time.
What actually changed in 2026
Texas Senate Bill 458 added Chapter 1813 to the Insurance Code. For personal automobile and residential property policies delivered, issued, or renewed on or after January 1, 2026, the policy must contain a binding appraisal provision for disputes solely over the amount of loss. Either the policyholder or the insurer can demand it unilaterally. The amount determined by appraisal is binding except for fraud, accident, or material mistake. That is not a proposal. It is live statute for 2026 renewals.
The Texas Department of Insurance has been working the implementing rules. Proposed 28 TAC §§5.9800–5.9806 set hard timelines: demand windows, appraiser naming periods, and outer deadlines for the award. Practitioner write-ups already treat the unilateral right as real for policies that renewed into the new year. Shops cannot file the demand themselves, but they can build the file, coach the customer, and stop leaving money on the table when the carrier will not move.
Washington followed with clearer minimum claims-handling duties under WAC 284-30-390, effective October 18, 2026. Carriers cannot condition coverage on photo-only evaluation. Shops and policyholders gain process language they can cite when supplements stall or explanations stay thin. Illinois added its own amount-of-loss appraisal path in the same window. The pattern across states is consistent: regulators are tightening the rails around automated or virtual first looks while giving policyholders and shops clearer levers on the dollar amount.
Florida lawmakers have already floated mandatory human review for claim denials. Oregon has guidance on virtual claim adjustment systems and when mobile apps can be required. The direction of travel is the same. Virtual is allowed. Pure automation of the denial or the lowball without a human gate is getting harder.
At the same time OpenAI shipped the Agents API. Long-running sessions, tool use, recovery, and context management moved from something you build to something you rent. Greg Isenberg called it the AWS moment for agents. The hard engineering is now a line item. What remains scarce is ownership of one painful vertical workflow and the data that makes the next run better.
The failure mode is the same as leakage
In the leakage essay the problem was money that already left and no one owned the file. Here the money has not left yet. The carrier estimate or the initial offer is short. The shop or the homeowner has the photos and the line items, but the map of what is missing lives in no system they control. So the file closes at the low number, or the supplement fight starts late and under-documented.
Collision shops already live this. Hail and storm work in restoration companies live this. The adjuster arrives with a photo-first or virtual process. The initial scope misses labor hours, OEM procedures, or secondary damage that only shows under proper light. The shop knows the number is low. The customer is tired. The clock on the new appraisal window is running. Without a clean first pass that flags the gap, the leverage created by SB 458 stays theoretical.
The same pattern appears in residential storm claims. Sparse photo sets become lowball scopes. Dense, angled, scaled sets get paid. The difference is not magic. It is ownership of the evidence map before the carrier’s first number hardens.
The wedge is a free checker, not a platform
Do not start with a claims management system. Start with the moment the customer already hates.
Upload the carrier estimate PDF. Or upload the set of damage photos taken the same day. Thirty seconds later: missing line items, density patterns that usually support higher repair hours, scale problems that virtual adjusters systematically under-count, and a short list of the specific points that justify an appraisal demand or a supplement under the new state rules.
That is the first action a stranger will take this week. No login required for the free pass. No new system of record. Just the photo or the PDF they already have on their phone.
The product then keeps the map. Which carriers short-pay which procedures in which ZIP codes. Which photo sets correlate with successful appraisal outcomes. Which missing lines reappear after the human gate. That dataset is the moat. Not another dashboard.
Models draft. People own the send.
Appraisal demands, supplements, and formal disputes are irreversible steps. The model can draft the demand letter, the photo index, and the line-item comparison. A named human still owns the send. That is the same gate we already run on money movement and filings. The bot finishes the research. The person signs.
This is not “AI for claims adjusters.” It is a vertical combination of two primitives that already show up in the idea mills: regulated document and photo review (the home-health paperwork pattern Greg has pushed) plus physical-world claim recovery for the trades. The agent does the first pass against a living checklist of short-pay patterns. The human decides whether to pull the appraisal lever that the 2026 statutes now make real.
The same logic applies to the spend-control side of agents. Once agents hold virtual cards and budgets, someone has to own the receipt and the exception. Here the “receipt” is the estimate and the photo set. The exception is the short-pay. The human gate stays in place for the irreversible action.
Why the compounding path is the dataset
Volume turns the free checker into a labeled corpus. Every upload that later produces a higher settlement or a closed appraisal award becomes training signal. Carriers change their virtual adjustment models; the checker sees the new under-count patterns first. Shops in Texas and Washington start citing the same process language; the product already knows which photo sets and which line-item gaps win under the new rules.
That is the opposite of a third SaaS dashboard. The dashboard is the easy part. The hard part is the map of what actually moves money under the 2026 statutes, kept current by the same people who have the photos and the closed files.
Once the map exists, the next products write themselves: automatic coaching for the appraisal demand, carrier-specific supplement templates that cite the exact WAC or Chapter 1813 language, and a quiet feed of which virtual adjustment systems are currently under-counting which damage types. None of that works without the first free checker that strangers will use this week.
What to build this week
Pick one surface. Collision or residential storm. Offer the free photo or estimate upload. Return a short, numbered list of flags with the specific statutory or regulatory hook that makes the flag matter. Keep every outcome. After a few hundred files the checklist stops being generic and starts being local.
Do not sell the platform first. Sell the moment the short-pay is still reversible. The rest follows from the map.
This is a live Friday morning snapshot of local storm-type events across the United States as of the early hours of Friday, September 11, 2026. Overnight into this morning the organized severe pulse was limited and mostly High Plains–oriented. No convective watches are currently valid. The Storm Prediction Center has elevated a Slight Risk of severe thunderstorms for parts of the Upper Midwest later today, with a broader Marginal Risk covering the central Plains into the Mid-South, Tennessee Valley, Carolinas, and Virginia. The Weather Prediction Center holds a Slight Risk of excessive rainfall in far southern Arizona and northern Minnesota, with localized flash-flood potential still lingering from overnight activity in the Ohio Valley and central Appalachians.
These remain county- and ZIP-scale thunderstorms, not a mainland hurricane landfall. Tropical Storm Norbert is active in the Eastern Pacific well offshore and poses no threat to U.S. land. Restoration exposure today centers on residual wind and hail damage from the Texas Panhandle overnight, lingering water in West Virginia and Ohio counties, and the new Slight Risk corridor from far northeast South Dakota into western and northern Minnesota this afternoon and evening. Conditions change fast. Verify with the National Weather Service for the specific county or ZIP before you roll.
What is live this morning
No severe thunderstorm or tornado watches are in effect as of the 1300 UTC Day 1 outlook. The most recent watch was Watch 665 from Wednesday evening. Overnight Local Storm Reports show a concentrated hail and wind event across the Texas Panhandle and nearby High Plains counties, with measured gusts to 87 mph near Colby, Kansas, and hail up to 2.25 inches near Lake Tanglewood in Randall County, Texas. Flash Flood Warnings and Flood Warnings were issued overnight for portions of eastern Arkansas, north-central West Virginia, southeastern Ohio, and the Virginia Eastern Shore; most of those products have expired or are in their final hours this morning.
SPC’s 1300 UTC Day 1 Convective Outlook highlights a Slight Risk across parts of the Upper Midwest—primarily far northeast South Dakota into western and northern Minnesota—for large hail (isolated 2+ inches possible), damaging winds, and a couple of tornadoes late this afternoon into tonight. A broader Marginal Risk extends south into the central Plains and eastward across the Mid-South into the Tennessee Valley, Carolinas, and Virginia for more disorganized pulse-type storms capable of occasional damaging gusts.
This is the primary organized severe corridor for today. A mid-level shortwave trough ejecting across the northern Plains will support a surface low and cold front. Moderate destabilization and 35–45 kt deep-layer shear favor initial supercells capable of large hail, with a transition to clusters and bowing segments producing damaging winds this evening. A low-end tornado threat exists if any cells remain discrete into the early evening when low-level shear increases. Confidence is higher in the far northeast SD–western MN axis than farther south into the central Plains, where initiation remains more conditional.
Cities and counties to watch: Aberdeen and Watertown areas in South Dakota; St. Cloud, Willmar, Duluth, Superior, Hibbing, and the Minnesota Arrowhead. Restoration read: stage for hail and wind. Large hail can produce concentrated roof and vehicle damage; clustering storms raise the tree-and-wire risk after dark. Photograph in remaining daylight only if safe.
Hotspot 2 — Texas Panhandle and High Plains overnight hits
Thursday evening into early Friday produced the most significant Local Storm Reports of the overnight window. Hail reports included 2.25-inch stones near Lake Tanglewood (Randall County, TX), 2.00-inch at Timbercreek Canyon, and multiple 1.00–1.75-inch reports around Pantex and Lake Tanglewood. Wind reports included an 87 mph gust 1 SE of Colby (Thomas County, KS), 67 mph near Pantex, 65 mph near Plainview (Hale County, TX) with snapped power poles and overturned vehicles, and additional 60–62 mph gusts across the Texas South Plains. Construction trailers and fences were damaged in the Plainview area.
Restoration read: this is already a just-hit desk. Hail-damaged roofs and vehicles in Randall, Carson, and Hale counties, plus wind-driven tree and pole work around Colby and Plainview, will generate same-day claims. Coordinate with local emergency management for access if power poles are down.
Hotspot 3 — Residual flood pulse (Ohio Valley, central Appalachians, eastern Arkansas)
WPC’s Day 1 Excessive Rainfall Outlook carries a Slight Risk for far southern Arizona (Santa Cruz County area) and northern Minnesota. Overnight, Flash Flood Warnings were active across Randolph County, Arkansas; multiple north-central West Virginia counties (Braxton, Gilmer, Upshur, Lewis, Roane, Calhoun, Ritchie, Wirt, Jackson, Wood); southeastern Ohio (Gallia, Jackson, Meigs, Vinton); and southern Accomack County, Virginia. Several of those products noted observed flooding, including impassable sections of US 33 near Glenville, West Virginia, and residual high water into Friday morning.
Restoration read: water extraction and drying are already on the books in the warned West Virginia and Ohio counties. Northern Minnesota joins the slight-risk language later today as the same system that supports the severe threat also produces 1–2 inch (locally 3 inch) rainfall amounts with rates approaching 1.5 inches per hour. Southern Arizona remains a monsoon-style flash-flood pocket.
Just hit
Wednesday’s Ohio–Pennsylvania–western New York Slight Risk and Watch 665 produced residual tree and wind damage that carried into Thursday. Thursday’s Marginal Risk corridor from the southern Plains to the Mid-Atlantic generated the Texas Panhandle hail/wind event detailed above and scattered overnight flood warnings. Iowa river flooding from earlier in the week continues to recede in places. No new U.S. mainland tropical cyclone is present; Tropical Storm Norbert remains well out in the Eastern Pacific.
Pulse table
Region
Main threats
SPC / NWS / WPC level
Status this morning
NE SD / western & northern MN
Large hail (2+” possible), damaging wind, couple tornadoes
SPC Slight
Late afternoon–tonight
TX Panhandle / High Plains
Hail to 2.25″, 60–87 mph gusts, pole/vehicle damage
Overnight LSRs
Just-hit / recovery
Central WV / SE OH / E AR
Flash flooding, residual high water
Expired/expiring FFWs + Flood Warnings
Aftermath / still draining
Far southern AZ
Flash flood rates
WPC Slight
Afternoon cells
Mid-South / TN Valley / Carolinas / VA
Occasional damaging gusts, pulse storms
SPC Marginal
Afternoon–evening
Atlantic / Gulf vs. U.S. mainland
No landfalling tropical cyclone
Quiet on the mainland coast
Quiet
What this means for restoration teams
Overnight hail and wind in the Texas Panhandle is already producing roof, vehicle, and pole claims. Residual flash flooding in West Virginia and southeastern Ohio is extraction-and-dry work with a 24–48 hour mold clock on any wet drywall. Today’s new Slight Risk in the Upper Midwest is a classic late-afternoon to evening supercell-to-cluster transition: large hail first, then damaging wind as storms grow upscale. Stage tarps, generators, and tree crews for the Minnesota corridor before the evening transition. Property owners should photograph damage in daylight if it is safe, call the carrier, and start extraction the same night if water is inside.
What this is not
This is not a regional derecho and not a U.S. mainland hurricane landfall. The work today, if it verifies, will be scattered: a hail swath through a Minnesota or South Dakota county, residual high water in a West Virginia hollow, or a wind-damaged construction site in the Texas South Plains. That is the local-storm pattern this desk should staff.
Looking ahead
Saturday the convective outlook drops to Marginal. Critical fire-weather conditions are also noted by SPC for today over parts of the West. Watch the next Storm Tracker update rather than assuming the Upper Midwest Slight Risk is the last line of the week.
Sources and how to verify
Primary sources: NOAA Storm Prediction Center Day 1 Convective Outlook issued 1226Z Friday, September 11, 2026; SPC Local Storm Reports for the 10 September period; Weather Prediction Center Day 1 Excessive Rainfall Outlook updated 0832Z; National Weather Service warning text for Amarillo, Lubbock, Charleston WV, Little Rock, Wakefield, and neighboring offices. No active convective watches as of 1205Z.
