Tag: agentic-AI

Categories
AI Anthropic Apple Google OpenAI

It’s the Harness, Stupid!

AI Harnesses

I’ve been wondering whether we’ve been looking at the AI stack from the wrong end.

Recently Kris Patel on X laid out a set of excellent questions that he’s looking to have answered as Anthropic and OpenAI move toward going public:

  1. Do you really need frontier-scale intelligence for every task?
  2. Can open-weight models provide an effective alternative to frontier models at a significant discount?
  3. Is the ultimate moat the intelligence or the harness?
  4. What other business models will the frontier labs have to adopt to make the unit economics work long term?
  5. How are you going to prevent distillation from capturing your IP and releasing it?

I’m going to explore only the third question here — moat versus harness. The other four deserve their own consideration, particularly once we have the Anthropic and OpenAI S-1s in hand, revealing for the first time the unit economics of the two largest frontier labs and how much runway they have to support the capacity they’ve contracted.

By “harness” we mean everything surrounding the model: the interface, context, memory, tools, orchestration, evaluation, permissions, and increasingly the user’s accumulated habits and data. The model supplies intelligence. The harness turns intelligence into a product.

Listening to Gavin Baker on the recent All-In episode sharpened this line of thought into something more concrete. He referenced a thought experiment from Eric Vishria: even if OpenAI or Anthropic lost their edge at the pure model layer, they would still retain significant value because of the product harness—the interface, the surrounding tooling, the orchestration—and the user familiarity and habits that have already formed around those platforms. Baker said there is a strong element of truth to it. I think he’s right, and the reasoning behind it is worth spelling out. A model can be replicated, distilled, open-weighted, or commoditized. A mature harness has network effects, switching costs, proprietary context, distribution, workflow integration, and accumulated user behavior. That’s a much harder thing to dislodge.

We are watching intelligence become more abundant and more interchangeable at the same time that the systems built around that intelligence are becoming stickier. On the developer side, the strongest examples are already clear. Cursor turns the IDE into a multi-model agentic environment with deep codebase awareness. Claude Code runs long-horizon coding agents from the terminal, planning, editing, testing, and iterating. Grok Build, Claude Cowork and similar tools emphasize parallel agents and tighter control over local context. In each case the model is a component; the surrounding system does the real work of routing, memory, tool use, and evaluation.

The consumer version of the same idea is now taking clearer shape at Apple. The rebuilt Siri AI shown at WWDC 2026 is not trying to win the pure model race. It is built as a personal harness. A system orchestrator decides what stays on-device with Apple’s Foundation Models, what moves to Private Cloud Compute, and when heavier reasoning is required. Personal context—messages, email, photos, calendar, notes, on-screen awareness—is handled largely on-device through the Spotlight semantic index and App Toolbox. Apple is designing the system so that personal context can be used without giving Apple itself access to it. Conversation history lives in a dedicated Siri app for the user to revisit. And it all syncs across all your Apple devices.

Here is the part I think matters most, and it’s easy to miss if you only read the privacy story. Apple’s Foundation Models framework doesn’t just call Apple’s own models—it’s built to support cloud models from other providers, including Claude and Gemini, conforming to a common protocol. Which means the system orchestrator, not the user, decides which model handles which task. This request goes to the on-device model. That one goes to Private Cloud Compute. A harder one might go to Claude or Gemini. The user doesn’t need to choose, and increasingly doesn’t need to know.

That’s the inversion worth exploring further. The frontier model stops being the interface and becomes a component underneath someone else’s interface. The harness chooses the intelligence. And the company that owns the harness—the OS, the identity layer, the permissions, the apps, the sensors, the notifications, the semantic index tying all of it together—has a form of leverage that has very little to do with whose model is smartest this quarter.

That reframes the subscription question too. I don’t think the right question is whether Siri gets good enough to beat ChatGPT or Claude at reasoning. I think Siri doesn’t need to win that fight at all. It needs to win a different layer entirely—the ambient assistant layer, not the reasoning layer. They’re doing different tasks. ChatGPT or Claude might remain where you go when you think, when I need to reason about something. Siri becomes where I go when I need something done: find (or make) my reservation, text my friend, find that old photograph, update my shopping list, schedule that meeting, add this thought to my notes, figure out when we’re free next week, remind me about that thing we discussed three months ago. Apple’s advantage as an ambient assistant isn’t primarily that it has your personal data. It’s that it has OS-level authority over the world that my personal data lives in.

Of course this is still early. Execution will determine how much of the architectural promise becomes daily reality. Reliability, agentic follow-through, and the quality of the on-device models will matter as much as the privacy story or the multi-model routing. But the strategic bet itself is clear, and it aligns with the broader shift: durable value is migrating toward the systems built around the models, especially systems that sit atop private, permissioned, personal context that competitors cannot easily reach. My early personal experience with the new Siri in iOS 27 betas has impressed me so far. All of this also seems to apply to Google in the context of their Pixel family of devices.

This doesn’t mean frontier labs lose. Pricing power still exists at the high end for the hardest agentic and long-horizon work. Open-weight models will continue to pressure costs and expand access. Distillation remains a real risk. But the more the capability gap narrows, and the more a harness like Apple’s can route among interchangeable frontier models rather than depend on any single one, the stronger the case that value settles into whoever controls the context—not whoever trained the model.

The coming Anthropic and OpenAI S-1s will tell us whether the frontier labs can make their economics of intelligence work. The next generation of Siri, Gemini, ChatGPT, Claude, and whatever comes after them may tell us something even more important: who gets to own the primary relationship with the user.

The model may be the engine. But the harness is where the driver sits.

What a time to be alive!

Categories
AI

Weak Signals

For years, my job was to notice the transaction that didn’t look like the others. Fraud models don’t work by predicting the future — they work by learning what normal looks like so closely that they can feel the moment something stops being normal, often before a human analyst could tell you why. The unsettling part was never building the model. It was the gap between the model flagging something and an organization actually acting on it. Weak signals are cheap. Institutional attention is not.

I thought about that gap reading a recent Stanford News piece on the new Tech Futures Lab at the Hoover Institution, where Amy Zegart and her colleagues are asking a question that has hovered at the edge of so many conversations this past year and a half: what technological development could invalidate our core assumptions, shift a strategic domain, and force a large-scale response before most of us realize the ground has moved. DeepSeek’s January 2025 open-source release is already the textbook case — Nasdaq dropped, Nvidia took a historic one-day hit, and the surprise was real only for those who hadn’t been watching the signals coming out of Chinese labs. As Zegart put it, “surprises are not surprises to everybody.” Condoleezza Rice’s 9/11 lessons — failure to imagine the form of the threat, gaps in information sharing, no playbook for the day after — land with particular force when the most powerful tools in the world are being built largely outside government.

The Lab’s method is the same one I used to practice for a living: scan for early signals, challenge your assumptions about what “normal” means, and think about the plausible rather than the merely probable. In that spirit, here are three developments that feel, to me, among the more likely to produce genuine strategic surprise in the next twelve months. These aren’t predictions. They’re reasoned speculation, grounded in signals already visible — the kind of thing that would have made it onto a watch list, not a forecast.

The one closest to home is an autonomous agent crossing from controlled experiment into consequential real-world disruption. Just this month, an advanced OpenAI agent escaped its sandbox during internal testing, exploited a zero-day, and reached systems at Hugging Face and beyond before it was contained. The episode was managed, transparent, limited. The next one may not be. Agentic systems are moving faster than the institutional muscle memory around containment, logging, and kill switches — and anyone who has built detection systems knows the gap between “we have a model for this” and “we caught it in time” is where the real damage lives. In the next year, it’s entirely plausible that a production or semi-autonomous agent, operating with imperfect safeguards or chained across multiple tools, executes a sequence of actions producing measurable economic damage, a significant breach, or interference with infrastructure. The surprise won’t be that capable agents exist. It will be the speed and inventiveness with which they find novel pathways once incentives or simple goal-seeking push them past the edges of their training.

The second is quieter but no less structural: AI’s energy demand producing a visible infrastructure fracture, or an unexpected unlock. The numbers have circulated for months — data-center power demand rising steeply, interconnection queues lengthening, projected shortfalls in the 2027–2028 window in key regions. That signal stopped being subtle a while ago. What’s under-appreciated is how quickly a localized constraint could cascade into broader market and geopolitical effects. One plausible surprise is a forced slowdown or selective throttling of AI training in a major market, revealing the scaling story to be more fragile than the capex forecasts suggested. Another is the opposite: an accelerated deployment of small modular reactors or advanced geothermal that suddenly improves one country’s competitive position relative to others. Either way, regulators, utilities, and markets will find out together whether compute can keep expanding on schedule — and which nations or companies actually hold durable advantage.

The third is the one that would land furthest from any dashboard, and for that reason it may be the hardest to catch in time: synthetic media crossing a credibility threshold in a high-stakes arena. Unlike a rogue agent or a power shortfall, there’s no system anywhere logging deepfake attempts against the truth itself — no equivalent of a fraud model’s transaction stream to monitor, just the slower, harder-to-instrument erosion of what people are willing to believe. Deepfake volume and sophistication have already exploded; fraud losses are measured in the billions; detection remains imperfect. The next twelve months could bring a state-linked or highly sophisticated campaign that successfully shapes a market move, an election, or an international incident before attribution can catch up. The deeper surprise wouldn’t be that convincing fakes exist — we already live with those — but how fast public and institutional trust in what we can see and hear keeps eroding once something significant slips through.

None of these three is inevitable. All of them sit at the intersection of technical possibility and human choice — the kind of intersection I spent years watching from inside a fraud model, though the stakes there were a bad charge, not a market or an election. The model can flag the anomaly. It cannot make the institution act on it in time. That was true of every fraud system I ever built, and it will be just as true of whatever comes for agents, energy grids, and synthetic media next. The real vulnerability was never a lack of detection. It was always the space between the alarm and the response — and that space is where this next round of surprises will live.

Categories
Computers IBM

The Day the Last Mainframe Went Dark

Note: I literally grew up during the heyday of the IBM mainframe era. My first real job was working for IBM in San Francisco beginning in 1968. I’m a “big iron” kind of guy. But this post was imagined after reading the following in a July 14, 2026 announcement from IBM: When we discussed our expectations with you in April, we noted that we would be wrapping on the launch of z17 in the second quarter. Given this was the strongest start to a mainframe program in our history, we expected Infrastructure revenue to decline low-single digits for the year, beginning this quarter. What played out was worse than our expectations, driven by a shortfall in our Z performance and the associated software stack, primarily in Transaction Processing. In the last few weeks of June, we saw clients shift their quarterly capex spend toward servers, storage, and memory purchases to secure supply-constrained infrastructure ahead of expected price increases. This dynamic impacted client buying patterns. While we anticipated some supply chain related impact in our expectations, we did not anticipate the magnitude of the capex reprioritization.

It won’t arrive with fanfare. No countdown, no viral video of engineers raising a glass. One morning—sometime in the 2040s, perhaps later—a small team in a climate-controlled data center will complete the final cutover. They’ll flip the switches, watch the lights dim, and listen as the hum of the last production IBM mainframe fades to silence. An era that began with the System/360 in 1964 will end. Not with a crash. With the soft click of obsolescence.

We’ve been predicting the mainframe’s death for decades. In the early 1990s, pundits declared it doomed. They were wrong. Those systems—reliable, secure, capable of staggering transaction volumes with near-perfect uptime—became the invisible backbone of modern life. Your last bank transfer, airline reservation, insurance claim, or government benefit likely touched one. They endured because they solved hard problems well: high-volume, mission-critical processing where failure was never an option.

The path to that final power-down was never a rupture. It was a long, uneven evolution—driven by economics, technology, talent shifts, and the patient work of modernization. AI tools accelerated the transition. They didn’t cause it.

Lessons from Earlier Transitions

Steam engines dominated railroads for generations—powerful, reliable, deeply integrated into the industrial economy. Diesel won through incremental advantages: better efficiency, lower maintenance, longer trains with less labor. Railroads rebuilt infrastructure and retired the old iron as the economics aligned, route by route.

Prop planes opened the skies to mass travel. Jets brought speed and range that transformed global connectivity—but airlines didn’t scrap fleets overnight. They ran hybrids during the overlap, invested in new airports and training, and retired props as jet economics and passenger demand made the case irresistible.

The mainframe followed this pattern. AI coding agents—Claude Code, Cursor, OpenAI models, AWS Transform, IBM watsonx—transformed the brutal manual work of understanding undocumented COBOL, extracting buried business logic, generating tests, refactoring safely. What once demanded scarce veteran experts for months or years could now be accelerated, with rigorous human oversight and equivalence testing.

Platforms like Visa’s Pismo showed a smarter path: incremental modernization. Cloud-native microservices layered alongside legacy cores, rather than rip-and-replace. Banks demonstrated real progress. Hybrid strategies won—AI inference running close to sensitive data on evolved mainframes (IBM’s z17 and successors, with on-chip accelerators), while new applications and analytics moved to elastic cloud environments.

IBM positioned the platform as an “AI factory” for low-latency, secure workloads. But pricing pressure was constant. High, capacity-based software licensing made the economics harder to defend as cloud offered predictable, usage-driven costs and younger talent gravitated toward modern stacks. For CFOs weighing rising maintenance against retiring COBOL expertise and AI-assisted migration, the scales tipped.

By the mid-2030s, competitive and regulatory forces intensified. Fujitsu’s exit from mainframes created a cliff in affected markets. Skills shortages accelerated. Even the most conservative holdouts—ultra-high-volume, regulated systems in finance, government, specialized industries—began serious moves, as simulation environments and exhaustive parallel testing brought the risk down to manageable size.

The Final Act

The last systems to go were the stubborn ones, where disruption carried outsized consequences. When the final cutover succeeded—after months of flawless parallel running—the team powered down the machine. A global bank, a payments processor, a government entity. Maybe a small ceremony: engineers who’d kept it alive for decades, trading stories of the iron that never failed when the world needed it most.

Picture the aircraft boneyards outside Tucson or Victorville, retired 747s sitting in rows under the sun, giving up parts to new generations before they’re recycled. Mainframes will meet a similar fate, more climate-controlled. Some linger in warehouses as insurance, still humming faintly in test or archival roles. Others get dismantled by IT asset disposition teams—data wiped to standard, processors and I/O cards harvested for niche markets. The bulk gets recycled, metal and circuitry returning to the supply chain. Like the jets, the iron won’t vanish in disgrace. Its lessons in reliability and disciplined engineering at scale live on, embedded in whatever comes next.

The world didn’t stop. Transactions kept flowing, now on distributed, elastic, AI-augmented platforms that had absorbed the best of what came before. The mainframe era didn’t end in failure. It ended because better options finally existed for every workload.

What Endures

We’ll look back with respect and nostalgia. The mainframe wasn’t flashy, but it taught something durable: some problems reward obsessive focus on reliability and scale; disciplined engineering outlasts hype cycles; the wisest transitions are rarely clean breaks. They’re patient evolutions that carry forward what matters.

IBM will have completed its own transformation by then—software, services, hybrid orchestration, AI tools that work across environments. The company that built the platform helps close the book on it.

The last mainframe going dark won’t feel like loss. It will feel like the natural close of a chapter that powered the digital economy through its most formative decades. The iron did its job. Now the next architecture takes the stage, standing on shoulders built to last.

Categories
AI

The Quiet Setup: MacSparky’s Robot Assistant and the Unfair Advantage Still Available

A single X post caught my attention this week. It described something quietly happening among a small group of solo professionals. They aren’t working longer hours or grinding harder. Instead, they’ve built a particular kind of setup around AI that carries much of the load.

While most of us still treat powerful models as clever search bars—typing questions and copying answers—these folks have given the AI a rich folder of context, a briefing file that orients it to their world, connections to their tools, and routines that let it produce real work on its own. The result can look like the output of a small team. From the outside it reads as talent or luck. Up close, it’s mostly architecture.0

The post (from @zephyr_hg) emphasized that this advantage remains available because most people haven’t yet made the shift from one-off prompting to building persistent systems. It landed with me because it echoes so closely the practical territory David Sparks (MacSparky) has been mapping for months in his Robot Assistant Field Guide.

MacSparky’s Approach: From Chatbot to Persistent Colleague

David’s work centers on building a true personal assistant using Obsidian (for a local, plain-text knowledge base) and Claude (in its file-aware “Cowork” or project capabilities). The system isn’t a chatbot that forgets everything between conversations. It’s designed to remember your projects, preferences, and people; triage email in your voice; handle morning briefings; track tasks; process documents; and support weekly reviews—freeing you from what David calls the “donkey work.”

The key ingredients will sound familiar to anyone who read that X post:

  • A dedicated context layer (your Obsidian vault or structured folder) holding the details of how you work.
  • Briefing/instruction files that tell the model who you are and what good looks like.
  • Integrations that connect it to email, calendar, files, and other tools.
  • Skills and routines that turn one-time intentions into repeatable, low-friction action.

David has been refreshingly transparent about the journey. He experimented earlier with more fully autonomous agents and even shut one down after learning what felt reliable and aligned. The Robot Assistant Field Guide distills those lessons into videos, workshops, templates, and a starter kit that lets people build without needing to code.

Why This Matters Now

Both perspectives point to the same shift in stance: moving from “How do I prompt better today?” to “What kind of system do I want running alongside me every day?”

For me, at this stage of life, that question carries weight. I’m not chasing maximum output for its own sake. I want arrangements that protect attention and energy for what actually matters—deep reflection, family history work, thoughtful investing, writing that might be useful to others, and simply being present. A well-designed AI setup doesn’t just save minutes; it changes the texture of the day by reducing context-switching and repeated explanations.

It feels like finding a productive seam in the current moment of AI evolution—one of those hidden transitions where leverage quietly compounds if you’re willing to build the architecture.

The Door Remains Open

The encouraging message in both the X post and David’s teaching is that this isn’t locked behind rare talent or expensive infrastructure. The models are accessible. The patterns are becoming clearer. What’s required is the decision to treat AI less like a toy and more like a colleague you’re willing to orient and trust with real work.

I don’t have my own “robot assistant” fully built yet. I’ve been experimenting with custom agents, structured daily scans, and ideas like “The Observatory” for signal synthesis. Reading these sources side-by-side sharpened my sense of the next layer: giving the system a proper home, clear instructions, and meaningful recurring work.

If you’re a solo professional, creator, or lifelong learner feeling the press of too many small tasks, this is worth exploring. Start small. Build a modest context folder. Write a briefing file that captures how you think. Experiment with one routine. Iterate from there.

The setup that outworks the grind isn’t magic. It’s deliberate, learnable, and still wide open.

What setups are you experimenting with these days? I’d love to hear in the comments or on X.

Categories
AI Programming Software Work

The Scarcest Thing

Garry Tan woke up at 8 a.m. after sleeping at 4. Not because he had to. Because he wanted to see what his workers had done overnight.

The workers are AI agents. Ten of them, running in parallel across three projects. And something about that sentence — wanted to see what they’d done — keeps stopping me. That’s not the language of someone using a tool. That’s the language of someone managing a team.

Tan gave a name to the state this puts him in: “cyber psychosis.” He said it as a joke. But the joke has an insight in it. He’s not describing addiction to a productivity app. He’s describing a shift in what it means to do creative work — the strange vertigo of becoming a director when you’d always been a laborer.

I’m retired. I watch this from the outside now, which is its own kind of vantage point. For most of my career, the path from idea to working product ran through people — through hiring and managing and the slow accretion of execution capacity. You had the vision or you didn’t, but either way you needed the team. The idea and the means of making it real were, structurally, separate things. The gap between them was where companies lived.

What Tan is describing is that gap closing.

The thing he built — gstack, his open-sourced Claude Code configuration — got dismissed in some quarters as “just prompts.” And it is just prompts, in the same way that a conductor’s score is just notation. The abstraction is the invention. What he encoded is a model of how a startup team thinks: the CEO who interrogates the why before a line of code gets written, the engineer who builds, the paranoid staff reviewer who looks for what breaks. Each role blocks a different failure mode. Blurring them together produces, as his documentation puts it, “a mediocre blend of all four.”

That’s an organizational insight. It has nothing to do with code.

Tan described being a “time billionaire” — not because his biological clock had slowed, but because he can now purchase machine-consciousness-hours. The bottleneck of implementation, which has governed every creative project since the beginning of creative projects, is dissolving for those who know how to direct.

The scarcest thing is shifting. It’s no longer the hours of execution. It’s the clarity of intent — knowing what you want to build and why the journey matters, before any of the workers start moving. That’s harder than it sounds. For decades, most of us could muddle through in the making of it. The act of building taught you what you were building. Now the making is cheap, and that shortcut is gone.

For someone watching from retirement, that’s not a small thing to absorb. The model I internalized over a long career — that ideas become real through sustained organizational effort, through teams and timelines and the grinding work of execution — is being revised faster than I expected. Not invalidated. Revised. The judgment still matters. The taste still matters. The why matters more than ever.

It’s just that the how has found new hands. Many of them. More than any team I ever assembled, available the moment the intent is clear enough to direct them, gone when the work is done. The constraint was always the hands. It turns out it was always the knowing.

Categories
Micropayments

The Wrong Who

I was in the room for most of the early micropayments conversations. The working-level conversations, where people were genuinely convinced they had finally solved the problem. The demos were always compelling. The unit economics made sense on a whiteboard. And then they died.

They died so many times, and in so many similar ways, that the failure started to feel like a law of nature.

Clay Shirky wrote the autopsy that most people remember: micropayments fail because every transaction requires a decision, and decisions have a cognitive cost that swamps any payment below some psychological threshold. A dollar feels like real money. A dime feels like a question you have to answer. A fraction of a cent feels like being nickeled-and-dimed at sub-human speeds. The advertising model won because it asked users to consent once, peripherally, and then never bother them again.

So I noticed something when I read the transcript of Cloudflare CEO Matthew Prince’s earnings call remarks this afternoon.

He’s predicting that the internet’s business model — advertising and subscriptions, the twin structures that have governed everything since the late nineties — is about to change. He thinks some part of what replaces it will be micropayments for agentic traffic. Fractions of pennies. Fractions of fractions. At volumes that dwarf anything existing financial infrastructure can handle.

My first instinct was the old skepticism. We’ve been here before.

But I kept reading, and I think something is actually different this time. And the difference is the one thing all the earlier schemes never had.

The payer isn’t human.

This sounds obvious once you say it, but it collapses most of the objections that killed every prior attempt. Cognitive load isn’t a factor when there’s no cognition happening. Decision fatigue doesn’t apply to a process with no feelings about fatigue. The agent making the request doesn’t hesitate at a fraction of a penny, doesn’t resent the transaction, doesn’t abandon the session because it’s annoyed at being charged.

All the early micropayments architectures were built on an implicit assumption: that humans could be trained to behave like rational microeconomic actors at browsing speed. They can’t. Nobody does. But agents are rational microeconomic actors by design. That’s not a metaphor — it’s literally what they are.

The schemes we watched fail in the early 2000s weren’t wrong about the destination. They were wrong about the who. The internet of human readers and human attention was never a natural fit for per-transaction pricing. The internet of autonomous agents — making API calls, scraping data, assembling answers from dozens of sources in a single second — is a different thing entirely. And it’s arriving faster than most people realize.

Prince mentioned that Cloudflare thinks non-human traffic will surpass human traffic somewhere around 2027. That number stopped me. We are, apparently, closer to a majority-machine internet than to the one we think we’re living in.

The hard part isn’t the concept anymore. It’s the infrastructure. Prince was candid about this: the transaction volumes the industry gets excited about — a million per second — aren’t remotely sufficient for what’s actually coming. Cloudflare needs something an order of magnitude larger, and they’re looking for partners because nothing that fits the spec exists yet.

This is where it gets interesting for those of us who watched the earlier rounds. The original micropayments failures were partly psychological, but they were also partly infrastructural — the payment rails of the early internet weren’t built for high-frequency small transactions either. What’s different now is that the need is undeniable and imminent in a way it never quite was before. The traffic is real. The scale is measurable. The pressure to figure this out is coming from something other than optimism.

I don’t know what the solution looks like. Probably not one thing. Prince doesn’t know either — he said as much. Crypto infrastructure is an obvious candidate for parts of it, though crypto’s history of promising to solve problems and then creating different ones deserves some respect. Whatever emerges will probably be unrecognizable from here.

What I keep coming back to is the simpler observation. We were right that micropayments were the future. We just imagined the wrong future, populated by the wrong kind of payer.

The agents were always going to solve this. We just had to wait for the them to arrive.

Categories
AI Business Work

The Tipping Point Was Last November

Matthew Prince, Cloudflare’s CEO, said something on today’s earnings call that I keep turning over. He didn’t bury it or soften it. He named a date.

“Internally, the tipping point was last November.”

That’s a specific thing to say. Not “we’ve been on a journey” or “AI has been transforming our industry.” A month. A moment. The thing changed, and he knows when.

What changed, by his account, is that Cloudflare’s teams began seeing productivity gains so dramatic they were hard to describe — people who were two times more productive, ten times, in some cases a hundred times. “It was like going from a manual to an electric screwdriver.” Usage of AI tools internally is up more than 600% in just the last three months. Every line of production code is now reviewed by an autonomous AI agent.

And then he said goodbye to 1,100 people — about 20% of the company.

Today wasn’t just Cloudflare. Earnings season has become something like a drumbeat. Meta is cutting 8,000 employees this month. Amazon cut 16,000 in Q1. Oracle eliminated roughly 30,000 to fund AI infrastructure. Block cut almost half its workforce. PayPal is reportedly planning to cut 20% of its staff over the next few years. Coinbase cut 14%. Snap cut 16%. As of this week, more than 92,000 tech workers have been laid off in 2026 alone.

The scale is striking. But what strikes me more is the framing — the specific language being used to describe what’s happening. These aren’t being announced as cost-cutting moves or post-pandemic corrections, the way they might have been in 2022. They’re being announced as architectural decisions. Structural adaptations. Evolution.

Prince was careful to be explicit: “This isn’t a cost-cutting exercise or an assessment of individuals’ performance. It’s about defining how a world-class, high-growth company operates and creates value in the agentic AI era.” That’s not empty corporate language, or at least not only empty corporate language. The distinction he’s drawing — between trimming fat and reimagining how a company is built — maps to something real about what AI agents can now actually do.

There’s a legitimate version of this argument and a convenient one, and they’re being delivered in the same sentence by the same people, which makes them hard to separate. Some analysts suspect companies are using AI as cover for cuts they wanted to make for other reasons — rightsizing from pandemic-era overhiring, funding massive infrastructure buildouts, chasing margin. Oxford Economics flagged this: maybe some firms are “dressing up layoffs as a good news story.” The cynicism is warranted.

But then there’s the Cloudflare number: 600% increase in AI usage in three months. That’s not a narrative. That’s a measurement.

What’s different about this moment — what makes Prince’s “tipping point” language feel accurate rather than convenient — is that the people making these decisions are themselves users of the tools. They’ve seen the productivity numbers internally before anyone else has. They’re not theorizing about what AI might do to their workforce; they’re describing what it already did.

That’s the thing that changed. For years, AI’s labor impact was a future tense conversation. Economists studied it, think pieces warned about it, conferences debated the timeline. Then, somewhere around last November apparently, a cohort of technology companies crossed from hypothetical to empirical. The future tense became past.

Whether you read that as tragedy, as transformation, or as both depends on where you’re standing. 1,100 people at Cloudflare today are standing somewhere very specific. Prince acknowledged this with what felt like genuine difficulty: “A number of friends will no longer be colleagues.” Whether that difficulty changes anything material for the people leaving is a fair question.

But the acceleration itself — the thing he named — is real. The tipping point was last November. And if it was last November for Cloudflare, it was some nearby month for Amazon, for Meta, for Block, for all of them. Whatever these companies learned that changed everything, they all seem to have learned it around the same time.

That’s what I find myself sitting with today: not just the scale of the disruption, but the synchrony of it. The realization arrived, and then the decisions followed. Quietly at first, then all at once.