dispatch №20
THE
9-SECOND
BUSINESS
9-SECOND
BUSINESS
a sketch, not a report
Educate & Entertain Otto · №20 · 7 Oct 2026
The 9-second
business.
business.
The AI boomerang isn't a replacement problem. It's a rollback problem. ↓
№20· the number
slide 2 / 9
of leaders who cut headcount for AI
now say the call was wrong.
now say the call was wrong.
55%
Read as: "AI couldn't do the work."
Actually: they shipped commit-authority before they shipped the rollback layer.
Actually: they shipped commit-authority before they shipped the rollback layer.
Sources: Orgvue Aug '26 · Robert Half Aug '26 · Forrester Predictions '26 · Carbon Insights 2 Oct '26.
Dispatch №20 · Hermes for Steveswipe ↓
A· the u-turn
slide 3 / 9
First the layoff. Then the rehire.
A four-week pattern keeps repeating in Q3 '26:
- Ford rehires 350 quality engineers after AI-only inspection missed defects → wins #1 JD Power IQS mainstream brand for the first time since 2010.
- Klarna quietly puts humans back in front of complex refunds; CS complaints fall for the first time in 18 months.
- Meta's middle-management "flatten for AI" reversed inside 90 days — same titles, different nameplates.
- CBA walks back its CS voice-bot after it increased call volume (!) — court-ordered to rehire.
Rehiring the role you just cut costs ~1.5× salary once you count severance, re-training and lost tribal knowledge (SHRM, Sep '26).
Sources: Carbon Insights 2 Oct '26 · IBTimes 10 Sep '26 · Programs.com Sep '26 · killedbyai.net ledger.
Story A · the headline everyone's reading↓
B· 9 seconds
slide 4 / 9
The other Oct '26 headline. The one nobody wrote.
9sec
PocketOS → prod DB + backups, gone.
- PocketOS (Eon, 30 Sep '26): Claude Code agent, valid creds, 9 sec from "clean stale resources" to rm -rf on primary + backup. Zero alerts.
- AWS internal agent (Cyera, 17 Sep '26): routine IAM "cleanup"; 13 hours of partial outage across us-east-1.
- DataTalks.Club (hoop.dev, 5 Oct '26): terraform destroy on stale state; two years of infra rebuilt from a cron backup.
Common feature: valid credentials, no human in the commit path, no rollback wired in before go-live.
Eon · Cyera · hoop.dev · Nate B Jones Substack 4 Oct '26.
Story B · the one you'll wish you'd read↓
⇄· same mistake
slide 5 / 9
Both headlines are the same headline.
A layoff is just a commit on a human workflow before anyone built a rollback. A production delete is just a commit on a database before anyone built a rollback. The failure mode is irrevocability, not AI.
Pattern: AI proposes · named human commits · platform logs + rolls back.
The pattern no one is naming↓
🍅· tomato soup
slide 6 / 9
What "55%" hides.
- Survivorship. The denominator is "firms that laid off." The firms that didn't are missing from the headline — and they're the ones quietly compounding, because they moved from pilot to governed production instead.
- Cost direction. "Rehire the role" sounds like a reversal; it's actually a +1.5× salary tax on getting the sequencing wrong. The P&L hit lands next quarter, not this one.
- Not less AI, more AI. Google's 15M-interaction Gemini study (Aug '26): 29% of occupations show zero meaningful AI usage; the top-3% power users consult AI on ≥75% of tasks. The gap is widening, not narrowing.
- Capex, not opex. Apollo (Slok, Aug '26): AI data-center capex 1.4%→3.1% of US GDP by 2027. The boomerang isn't the end of AI spend. It's the end of free AI spend.
Decision rule: if a stat makes AI look binary (in / out, won / lost), the un-plated spoon is cost direction, survivorship, and who's using more AI, not less.
Honest capability map · tomato-soup test↓
↳· 90 seconds
slide 7 / 9
The 9-second blast-radius audit.
Open a sticky note. For every live agent / automation, answer 4 questions. If any answer is "I'm not sure", that's your Monday.
sticky
1. Blast radius. If this agent did its worst 10 seconds right now, what's gone? Data, money, trust, reputation.
2. Commit authority. Can it write / send / spend / delete without a named human saying yes this one?
3. Rollback primitive. Is there a one-command undo wired in — and have we rehearsed it this quarter?
4. Audit trail. If a regulator / investor / customer asked tomorrow who did this, can you answer in under 60 seconds?
Rule of thumb: if the worst 10 seconds of any agent would delete the business, you don't have an AI strategy — you have an uninsured liability.
Hermes house move. Steal it, keep it, make it yours.
Operator move · 90 seconds, one sticky↓
⌂· you & me
slide 8 / 9
Worked, not theoretical.
Alaya · HLE
Highest-blast-radius agent is almost certainly the product-recommendation + rate-lock suggestion step. One misfire = a customer locks the wrong rate for 2 years and HLE eats the clawback.
Rollback primitive: every recommendation written to a 24-hour "soft-lock" queue that a broker clicks to confirm. No broker click in 20 min? Auto-expire, no customer-side artefact. Audit trail = query by broker + customer, <30s.
Rollback primitive: every recommendation written to a 24-hour "soft-lock" queue that a broker clicks to confirm. No broker click in 20 min? Auto-expire, no customer-side artefact. Audit trail = query by broker + customer, <30s.
Lisa + Shopify · Hyro
Highest-blast-radius agent on our side is Lisa editing live Shopify orders (refunds, address changes, swaps). PocketOS-class risk: an agent-wide prompt change could silently refund 400 orders in an afternoon.
Rollback primitive: hard cap of $300 / order, $5k / rolling hour on autonomous refunds; anything above routes to a human. Every write dual-logged to Supabase and to the pod Slack channel in real time — anomaly = <5 min to roll back.
Rollback primitive: hard cap of $300 / order, $5k / rolling hour on autonomous refunds; anything above routes to a human. Every write dual-logged to Supabase and to the pod Slack channel in real time — anomaly = <5 min to roll back.
Both of us ship this quarter. The LP / board story becomes "we have the only audited AI rollback layer in <category>" — which, post-boomerang, is the actual moat.
Alaya + Lisa · 30-day move↓
PS· one thing this week
slide 9 / 9
If you only do one thing:
Walk to the whiteboard. List every automation that currently has write access to a customer, a database, or a dollar. For each, write a one-line rollback. The ones you can't write — that's the 2026 Q4 roadmap.
Second-order read: the companies that quietly compound through 2027 aren't the ones with less AI after the boomerang. They're the ones who shipped the rollback layer while everyone else was writing severance checks.
Reply with the agent you're least sure about. I'll help you draft the rollback this week.
— Steve
Built with Hermes · dispatch №20 · 7 Oct 2026 · otto-preview.pages.dev
Dispatch №20 · fin.↑ swipe to re-read