AGaaS breaks that vocabulary because AGaaS sells something structurally different. AGaaS — Agentic-as-a-Service — charges for the execution of outcomes by agents, not for access to tools operated by humans.

That single reframing is the disruption. It rewires what gets sold (outcomes, not access), who does the buying (business budgets, not IT budgets), where margin lives (substrate, not interface), and which metrics still predict the future (consumption, not seats). Every SaaS moat was built for a world where the seat was the atomic billing unit. In AGaaS, the seat is gone. The agent is the atomic unit, and the moats have to be rebuilt from scratch around it.

Three sequential inversions define the transition, and understanding them is prerequisite to understanding what defensibility looks like inside the shift:

• The operator inversion. The agent, not the human, operates the workflow. The billing unit stops tracking headcount and starts tracking agent activity. Most enterprise software companies have completed this inversion architecturally by mid-2026, even if they have not repriced.

• The buyer inversion. The person authorizing the purchase is the executive who owns the outcome (the CRO, the COO, the general counsel), not the IT function that owns the tool stack. Procurement, budget line-items, and the sales motion all rearrange. Most vendors are still mid-flight on this one.

• The margin inversion. Gross margin structure shifts from “software plus support” (high fixed margin, low variable cost) to “consumption minus inference” (variable margin dominated by token cost). The P&L reshapes. This inversion is deferred at most incumbents through mechanisms like internal absorption (”Customer Zero”), buybacks, and reclassification, but it becomes visible once consumption revenue scales past a threshold.

The AGaaS transition is what these three inversions look like when they run through the enterprise software category. It has a canonical form, and its canonical form has been mapped in the prior work of this analytical arc:

Access My Harness Via The BE Platform!

Follow me on The AI Supercycle as well!

Subscribe Now at 50% Discount, Expiring!

• “From SaaS to AGaaS: The Full Cascade” (March 2026) mapped the underlying value-layer inversion — value migrating from the interface layer, where SaaS captured it, down to the substrate layer, where AGaaS captures it — and the five-layer cascade this inversion produces across the enterprise software stack. It also established the three canonical AGaaS pricing models: outcome-based, consumption-based, and hybrid.

• “The Four Frictions of AGaaS” (April 2026) mapped the frictions that slow the transition — financial, operational, competitive, commercial — and why they multiply rather than add.

• “The Tell: Salesforce Q1 FY27” (May 2026) used the largest pure enterprise-software incumbent as an instrument to locate where the transition actually sits. The verdict: architecturally migrating, mechanically still SaaS. Operator inverted, buyer not, margin deferred.

• “The Four Intelligence Moats” (June 2026) — the direct parent to this piece — mapped how the entire AI stack builds defensibility across paradigms: corpus, verifier, harness, container. That piece established the machine-side moat map.

This piece completes the arc by mapping defensibility inside the transition itself. If old SaaS moats no longer apply and machine-side moats alone are not sufficient, what moats does an AGaaS company actually build? The answer is six — three inherited from the machine-side (verifier, harness, container), three new to the buyer relationship (trust, integration, feedback). Together they define what AGaaS defensibility looks like once the transition matures. They also determine, mechanically, which of the three AGaaS pricing models a company can actually charge — a link the closing section of this piece will make explicit.

The order in which the six moats are built matters more than the number of them. They are not parallel. They are serial. Each one unlocks the next. A company that tries to build them out of order finds itself with moats that do not compound — and, more consequentially, with pricing power that stalls at whichever inversion its missing moat was gating.

Access My Harness Via The BE Platform!

Follow me on The AI Supercycle as well!

Subscribe Now at 50% Discount, Expiring!

Read more

• The inversion: routers turn models from products into suppliers, migrating pricing power from the model layer to the allocation layer — whoever makes the purchasing decision captures the leverage.

• The pincer: labs compress inference costs from the supply side (compute multipliers) while routers compress demand from the buy side; the gains land in different pockets.

• The cascade: routing reshapes every layer beneath it — extending GPU fleet life, redirecting silicon roadmaps toward inference-specialized chips, and turning energy allocation into a per-query decision.

• The barbell: optimizing allocators hollow out the mid-tier model market, splitting demand between irreplaceable frontier intelligence and near-free commodity models.

• The meta-moat: evaluation data — knowing empirically which model is good at what — is the routing layer’s defensible asset; the scoreboard beats the switch.

The routing paradigm is not a product story. It is the moment the AI stack acquired an internal market — a mechanism that prices intelligence continuously and transmits that price signal down to the physical world and up to the regulatory one. Whoever operates that mechanism operates the stack’s capital allocation.

The Architecture: A Market Grows Inside the Stack

Access My Harness Via The BE Platform!

Follow me also on The AI Supercycle!

Subscribe Now at 50% Discount, Expiring!

Strip away the product names and a router is one thing: a capital allocation engine for intelligence.

Every query entering an AI system carries two hidden variables — the difficulty of the task and the value of getting it right. For three years the industry priced neither. Users manually selected a model, defaulted to the most expensive one out of habit or brand trust, and paid frontier prices for tasks a model one-tenth the cost could handle. Structurally, this was a market without price discovery: heterogeneous demand met heterogeneous supply through a single crude interface — the model picker dropdown — and the mismatch was absorbed as waste.

Routers are the price discovery mechanism arriving. They estimate task difficulty, match it against a live map of model capabilities and prices, and dispatch each query to the cheapest supplier that clears the quality bar. The Information’s reporting this week catalogued the forms this now takes, and the taxonomy is worth holding onto because each form represents a different owner of the allocation decision:

Lab-internal routing — OpenAI’s GPT-5 switching between sub-models under the hood. The lab keeps the allocation decision in-house and arbitrages its own portfolio. The customer never sees the spread between what they paid for and what actually ran.

Neutral marketplace routers — OpenRouter, which raised $120 million on the thesis, plus Martian and Not Diamond underneath it. These sit outside any lab and optimize honestly across the full supplier population.

Platform gateways — Databricks’ Unity AI Gateway, Palantir’s Evolve. Enterprise infrastructure players bundling routing into the data and workflow platforms enterprises already run on.

Agent-level routers — Cognition’s new sidekick architecture, which delegates easier subtasks to cheaper agents mid-workflow. Here routing happens inside a running agentic process, not at the query boundary.

DIY and model-as-router — IT departments vibe-coding their own switches, or developers handing a cheap model like DeepSeek a menu of models and asking it to pick. The Arcee AI approach: use the cheapest competent judgment available to allocate the expensive judgment.

Five forms, one mechanism: a decision that used to belong to the user — or default silently to the model vendor — now belongs to an intermediary layer. And in business architecture, whoever makes the purchasing decision captures the negotiating leverage.

The reported numbers establish that this is not marginal optimization. Palantir says Evolve cut computing costs for one task by 97% by swapping a frontier OpenAI model for its Nano sibling. McCarthy Building, a $9 billion construction firm, cut token consumption 60% year-over-year — partly through model swapping, partly because the router rewrites prompts to burn fewer tokens for the same outcome, which is a second and underappreciated function: routers optimize not just which model but how the model is asked.

Cognition’s router reportedly matched Anthropic’s Fable 5 on a coding benchmark at 35% lower cost. Sakana claims a coordinated multi-model system competitive with frontier flagships by routing math to one lab and science to another.

When an intermediary reliably delivers frontier-equivalent outcomes at a third to a thirtieth of the cost, it is not a feature. It is a new layer of the stack asserting itself. Which raises the structural question this piece exists to answer: where exactly does it sit, and what does it do to everything above and below it?

Read more

Let me start by saying, this is not a framework.

It is a complete grand-strategic apparatus, built over the last decade, that stacks four layers on top of each other: a philosophy about what reality is and how it can be known, a theory about how complex systems in the AI business era actually behave, a method for producing structural understanding of specific domains, and a set of frameworks that are outputs of the method rather than the substance of the practice.

Most of what gets called strategic analysis in the AI economy occupies only the fourth of those layers — a framework, imported from somewhere, applied to whatever domain the analyst is looking at. The Business Engineer occupies all four, and the value comes from the stack being complete.

This piece is the description of that stack. What sits at each layer? Why does the stack have to be complete for any layer to work? And why it matters that the whole apparatus operates at the grand strategy altitude — reading the territory — rather than at the strategy or tactics altitudes, where most business analysis lives.

Access My Harness Via The BE Platform!

Follow me also on The AI Supercycle!

Subscribe Now at 50% Discount, Expiring!

Grand strategy, strategy, tactics — and why the confusion is expensive

Access My Harness Via The BE Platform!

Follow me also on The AI Supercycle!

Subscribe Now at 50% Discount, Expiring!

I have written about this before and I will repeat the frame here because it is foundational for everything that follows.

Grand strategy is reading the territory. It is understanding the underlying structure of the reality you are operating in — the distributions, the forces, the constraints, the dynamics that determine what is possible and what is not. Grand strategy is upstream of everything else. It is the layer where you look at the world and try to see what it actually is, before you decide what to do about it. Without grand strategy, everything downstream is guessing.

Strategy is the map. It is what you draft after you have read the territory — a working representation of the terrain that you can use to plan movement. The map is provisional; it is corrected when the territory turns out to be different from what the map showed. But the map is always derived from the territory. Any map that is not derived from a proper reading of the territory is not a strategy — it is a fiction being applied to a situation that does not match it.

Tactics are the routes. Given the territory and the map, tactics are the specific paths you can take. Many paths are possible. Some lead where you want to go. Most of what people call “strategy” in business is actually tactics — the selection of specific paths — dressed up in strategic language.

The confusion between these three altitudes is one of the most expensive mistakes in business, and it is the specific mistake most strategic analysis is currently making in the AI era.

People are producing tactical outputs, calling them strategy, and skipping grand strategy entirely — which is to say, they are drawing maps and selecting routes without ever having read the territory.

In a stable environment, this can be gotten away with; the territory doesn’t move fast, and old readings still roughly hold. In the AI era, the territory is moving faster than any map can keep up with, and any strategy or tactics not derived from continuous fresh reading of the territory becomes obsolete before it can be executed.

The Business Engineer is, first and foremost, an apparatus for reading the territory. That is what makes it grand-strategic rather than strategic or tactical. Everything else — the strategies it derives, the tactics it enables — is downstream of this. The apparatus is designed to do the grand-strategic work that most business practice skips, and to do it repeatedly, at scale, against the specific class of complex systems that define the AI era.

The philosophy

Access My Harness Via The BE Platform!

Follow me also on The AI Supercycle!

Subscribe Now at 50% Discount, Expiring!

Every apparatus that reads territory operates on a philosophy — a set of underlying commitments about what reality is, what can be known about it, and what counts as knowing. Most strategic frameworks skip the philosophy layer entirely, which is why they produce outputs that are internally consistent and externally wrong when the underlying reality doesn’t match the framework’s implicit metaphysics.

The Business Engineer has an explicit philosophy, and it is worth naming because everything else derives from it.

Reality is structural and structurally knowable. The world is not a collection of narratives, opinions, or perspectives. It has underlying architecture — distributions, forces, positions, constraints — that determines what is possible in it. This architecture is knowable, not in the sense of being fully specifiable, but in the sense of having foundational properties that can be identified, tested, and used to make decisions. Structural knowability is the first commitment. Without it, no analytical apparatus can be evaluated as right or wrong, only as more or less persuasive.

Reality is authoritative over the analyst. When the analyst’s model and reality disagree, reality wins. This sounds trivial and is not, because most analytical frameworks are structured in practice to be defended against disconfirming evidence rather than corrected by it. The Business Engineer’s second commitment is that the apparatus exists to be corrected by reality, not to survive against it. Any framework that cannot be wrong, cannot be right either; falsifiability is the property that makes structural knowledge distinguishable from ideology.

Complexity is a property of reality, not a failure of analysis. Most classical business analysis treats complexity as noise to be filtered out on the way to a clean model. The Business Engineer treats complexity as the substance of the phenomenon. Power-law distributions, fat tails, non-stationary dynamics, opaque causal chains, unbounded competitive fields — these are not analytical inconveniences. They are properties of how the AI economy actually behaves, and any apparatus that filters them out to produce a clean model has produced a clean model of something that isn’t there. Complexity-as-substance is the third commitment. It changes what “understanding” means.

Compression is possible without loss of foundational structure. Even in complex domains, it is possible to identify the small number of properties that carry the weight of the phenomenon — the distributions, the positions, the constraints that determine the domain’s behavior. The rest can be discarded. This is what distillation means, and it is a philosophical commitment before it is a methodological one: you have to believe that reality has this property — that its complexity is not uniformly load-bearing, that some structural properties matter much more than others — in order to build an apparatus around finding them. If everything about a complex domain matters equally, no apparatus can produce a portable, actionable understanding of it. The Business Engineer’s fourth commitment is that this is not the world we are in. Complex domains have concentrated structural mass, and finding that mass is the analytical project.

Structural understanding must be portable and actionable, or it is not understanding. An analytical output that cannot be held in a working mind, cannot guide a specific decision, cannot survive the analyst leaving the analysis behind — that output has failed regardless of how comprehensive it is. Portability is the fifth commitment. It rules out the class of analytical outputs that look rigorous, take three hundred pages to communicate, and produce no consequential action.

These five commitments together — structural knowability, reality’s authority, complexity-as-substance, concentrated structural mass, portable understanding — constitute the philosophy of The Business Engineer. Every commitment is defended against a specific failure mode in classical business analysis. Every commitment shapes what the apparatus can and cannot do at the layers above. This is the deepest layer of the stack and the one most other frameworks don’t have at all.

The theory

Access my harness with the exec plan!

Follow me also on The AI Supercycle!

Subscribe Now at 50% Discount, Expiring!

On top of the philosophy sits a theory — a set of foundational propositions about how the specific reality of AI-era complex systems actually behaves. The theory is not the philosophy; the philosophy is about reality in general, the theory is about this reality specifically. And the theory is not the method; the theory tells you what kind of world you’re in, the method tells you what to do about it.

The Business Engineer’s theory, compressed to its essentials, holds that:

• AI-era domains are power-law and fat-tailed by structure, not by accident. The concentration of value at the top of every distribution — labs, platforms, models, capabilities, returns — is not a temporary condition of an immature market. It is a structural property of how systems built on massive fixed capital costs, learning curves, and network effects distribute their outputs. Any analysis that treats these distributions as normal, or as convergent-toward-normal, is making a category error.

• Categories in the AI economy are dissolving and reforming continuously. The industry boundaries that used to organize strategic analysis — software, media, financial services, retail, consulting — are becoming accidents of historical accretion rather than meaningful strategic units. The unit of analysis has shifted from industry to capability layer, and any framework that operates on the old units produces increasingly ceremonial outputs.

• Competition is unbounded and multi-scalar. The relevant players in any domain include the labs upstream, the platforms downstream, the specialized incumbents in the vertical, the horizontal AI-native firms that could enter tomorrow, and the customers who might build their own and stop buying. Competitive analysis that identifies “the players” is producing a snapshot of who is visible today, not who will be competing tomorrow.

• Causal chains are opaque in real time and legible only in retrospect. In the AI economy, the drivers of outcomes often become identifiable only after the outcomes have occurred. Cause and effect happen at inference speed. Strategic planning that assumes causal legibility in advance is assuming a property the domain does not have.

• Capability migrates outward from cores to peripheries at fractal scales. This is the specific claim the Harness Trilogy developed — that in the AI era, the locus of value shifts from the model to the harness around it, and the same shape appears at the individual, organizational, and societal scales. This is a theoretical claim about how AI-era systems evolve over time, and it has predictive content that the last eighteen months have validated.

• Structural transformations run on multiple nested clocks. The AI Supercycle framework specifies this: there are cycles within cycles within cycles, each running on its own clock, and the interactions between the clocks determine what looks like a bubble, what looks like a supercycle, and what actually is happening structurally. Any theory that operates on a single timescale misses the interaction effects that produce the phenomena everyone is trying to explain.

Together these propositions constitute the theory of how AI-era complex systems behave. They are not exhaustive. They are the foundational propositions — the ones that survive against reality repeatedly, produce non-obvious predictions, and structure how the method should be applied. The theory is what makes the method appropriate to this reality specifically, rather than to reality in general. A method without a theory is a technique; a theory without a method is an interpretation. The Business Engineer has both, and they are calibrated to each other.

The theory is also falsifiable, per the philosophy. Any of its propositions could be wrong. Any of them could be found not to hold in some specific domain. When that happens, the theory is corrected, and the method is recalibrated. This is what it means for the theory to sit on the philosophy: it is defended by the philosophy’s commitment to reality’s authority rather than by rhetorical defense against critique.

The method

Access My Harness Via The BE Platform!

Follow me also on The AI Supercycle!

Subscribe Now at 50% Discount, Expiring!

On top of the theory sits the method — the specific practice for producing structural understanding of a given domain. The method is what most other analytical frameworks think they are; The Business Engineer’s method is one layer of a four-layer stack, not the whole thing. The method’s power comes from being anchored in the philosophy and calibrated to the theory. Detached from either, it becomes a technique that can be misapplied.

The method is what I have previously described as distillation of a domain via contextualization, and I will restate it here compactly because the previous piece walked through it in detail.

• Contextualize. Identify the local distribution of the domain (power-law, fat-tailed, bimodal, normal — where does the mass sit, where are the tails) and identify where the domain sits in the broader architecture (upstream or downstream, substrate or superstrate, early or mature, regulated or unregulated). This is the grand-strategic reading of the specific territory. Everything downstream depends on getting it right.

• Abstract. Extract the foundational structural properties from the context. Discard the surface. Identify what makes the domain behave as it does at the level of underlying structure.

• Model. Build a working model of the domain’s dynamics that captures the foundational properties and is small enough to reason with. Not comprehensive. Distilled.

• Act. Use the model to make specific decisions with real stakes and real consequences. Predictions without decisions produce no feedback.

• Refine and revalidate. When outcomes arrive, feed them back. Adjust the model where the model was wrong. Adjust the abstraction where the abstraction was wrong. If the outcomes contradict the original context framing, the framing itself was wrong — go back to step one and rebuild. This is the step most methods skip, and it is the step that keeps the apparatus honest.

This is the method. Six operational moves, applied repeatedly, tightening with use. The method is what makes the apparatus a practice rather than a theory — it is what someone actually does when they are being The Business Engineer, as opposed to what they are thinking about.

But — critically — the method is not the whole apparatus. The method calibrated to a different philosophy would produce different outputs. Applied to a domain the theory doesn’t fit, it would produce wrong outputs. The method’s validity depends on the layers below it, which is why the frameworks it produces cannot be extracted from the stack and used alone. This is the specific way in which most attempts to copy analytical frameworks fail: the framework is extracted from its philosophical and theoretical context and applied in a different context, where it produces outputs that look right and are structurally wrong.

The frameworks

Access my harness with the exec plan!

Follow me also on The AI Supercycle!

Subscribe Now at 50% Discount, Expiring!

At the top of the stack sit the frameworks — the specific structural readings The Business Engineer has produced by applying the method to specific domains. These are what most readers encounter first, and they are the least fundamental layer of the practice. They are outputs, not the substance.

The frameworks include, among others:

• The AI Supercycle — the reading of the AI economy as a whole, in terms of three nested cycles, three phases, and the specific ways in which the aggregate looks like a bubble and behaves like a structural transformation

• The Map of AI — the reading of the AI stack as nine layers with different structural properties, distributions of return, and positional dynamics

• The AGaaS Trilogy and its extensions — the reading of the shift from selling access to selling outcomes as a structural transformation, with four intelligence moats and a set of derived mental models

• The Harness Trilogy — the reading of capability migration from model to harness as a fractal phenomenon at three scales, with four repeating patterns and one bedrock

• The Routing Paradigm — the reading of agentic infrastructure as a routing problem with specific structural properties

• The Five Postures — the reading of firm positioning in the agentic era as a set of five stable configurations with specific tradeoffs

Each of these is a strategic map — in the grand-strategy sense of the term — derived from a grand-strategic reading of a specific territory. Each is provisional; each is corrected when the underlying territory is found to have moved. Each is portable, actionable, and load-bearing in the specific senses the philosophy requires.

But these frameworks are not The Business Engineer. They are what The Business Engineer produces. Anyone who reads the frameworks without understanding the philosophy, theory, and method beneath them is holding the output without the apparatus that produced it — which means they cannot update the frameworks when the territory changes, cannot produce new frameworks for domains the existing ones don’t cover, and cannot evaluate whether a framework applies in a given case. The frameworks are the visible surface of the practice, and the invisible layers underneath are where the actual work lives.

This is why “framework” was the wrong word for the whole apparatus. Frameworks are outputs of the apparatus. The apparatus itself is the four-layer stack.

Why the stack has to be complete

Access My Harness Via The BE Platform!

Follow me also on The AI Supercycle!

Subscribe Now at 50% Discount, Expiring!

The stack could theoretically be broken. Someone could hold the philosophy without developing a theory. Someone could develop a theory without a method. Someone could apply a method without frameworks. Each partial version fails in a specific way, and enumerating the failures is worth doing because it clarifies why the complete stack is what the practice actually is.

• Philosophy without theory produces a general commitment to structural reading of reality without any specific claims about the reality being read. This is philosophy of science, not applied analysis. It is not wrong, but it does not produce guidance for consequential decisions in a specific era.

• Theory without philosophy produces claims about how AI-era systems behave that are not anchored in commitments about how such claims should be evaluated. This is what most AI-era analysis currently does: it makes claims about power laws, network effects, capability migration, and so on, without an underlying commitment to falsifiability and reality’s authority. The claims float, get defended, and become ideology when they should be corrected.

• Method without theory produces a technique that can be applied to any domain, without a way of knowing which domains the technique is appropriate for. The method’s contextualization step becomes generic — “understand the domain” — rather than specifically targeted at the distributions and positions the theory identifies as foundational.

• Method without philosophy produces a technique that can be executed but not evaluated. Outputs are produced; whether they are right or wrong becomes a matter of persuasion rather than validation. The revalidation step of the method depends on the philosophy’s commitment to reality’s authority; without it, revalidation becomes rhetorical rather than structural.

• Frameworks without method produces static representations that cannot be updated. The Business Engineer’s frameworks are all provisional; they are corrected when the territory moves. Without a method that continuously reapplies contextualization and revalidation, the frameworks become fossils.

• Frameworks without theory produces representations that cannot be evaluated for appropriateness to specific domains. Every framework has an implicit theory it depends on. Users who don’t hold the theory cannot know whether the framework applies in their case.

• Frameworks without philosophy produces representations that are treated as doctrine rather than as tested structural readings. This is where most strategic framework use ends up: the framework becomes a template, the template is applied without regard to whether the underlying reality matches, and the outputs are treated as strategic even though they are barely tactical.

Every partial version of the stack is a specific failure mode. The complete stack is what avoids all of them. This is why The Business Engineer is a grand-strategic apparatus rather than a strategic framework. It has to occupy all four layers to do what it does. The frameworks it produces are strategic maps; the apparatus that produces them is grand-strategic; and the philosophy underneath is the deepest layer that makes anything above it possible.

What the apparatus demands of its user

Access My Harness Via The BE Platform!

Follow me also on The AI Supercycle!

Subscribe Now at 50% Discount, Expiring!

An apparatus is only as good as the user operating it. Some frameworks are designed to be operated by anyone — that is one of their attractions and one of their limits. The Business Engineer is not designed to be operated by anyone. It is designed to be operated by someone willing to hold the whole stack, and holding the whole stack is itself a discipline.

Specifically, the apparatus demands:

• A commitment to structural reading over narrative interpretation. The user has to be willing to look for underlying architecture rather than for stories, personalities, or plausible-sounding explanations. This is a temperament as much as a skill, and it is not the temperament most business analysis rewards.

• A tolerance for being wrong. The philosophy’s commitment to reality’s authority means the user will be corrected by outcomes, sometimes publicly, sometimes at cost. Users who cannot tolerate being wrong will defend their frameworks against correction, which converts the apparatus into ideology.

• A capacity for compression. The apparatus produces distillations, not comprehensive reports. Users who cannot compress will produce outputs that miss the foundational structure while covering everything else. Compression is a discipline that takes years to develop and is rarely explicitly taught.

• A willingness to hold multiple altitudes simultaneously. The apparatus operates at grand strategy, produces strategy, enables tactics. The user has to be able to move between altitudes without confusing them, which is the specific skill the grand-strategy essay identified as most valuable and most rare.

• A refusal of imported frameworks. Every time the user is tempted to reach for Porter, or SWOT, or disruption theory, or any of the standard business-school toolkit, the apparatus requires them to stop and ask whether the imported framework’s implicit theory matches the domain. Almost always, it does not. The refusal is what keeps the apparatus honest; the temptation to import is constant.

These demands are why the apparatus produces the outputs it produces. They are not casual requirements. They are the specific dispositions the practice requires, and users who cannot meet them will produce outputs that look like Business Engineer work and are not.

What this means for the AI era

Access my harness with the exec plan!

Follow me also on The AI Supercycle!

Subscribe Now at 50% Discount, Expiring!

The AI era is going to reward the users of grand-strategic apparatuses and punish the users of tactical frameworks-dressed-as-strategy. This is a claim about the structural properties of AI-era decision-making, and it follows directly from the theory.

When the territory is stable, tactical thinking can be gotten away with; the underlying map doesn’t change, so old routes still work. When the territory moves, tactical thinking fails, because the routes lose their referent. The AI era is a moving-territory era on every dimension that matters. The distributions are shifting. The categories are dissolving and reforming. The competitive fields are unbounded. The causal chains are opaque. Under these conditions, tactical thinking without grand-strategic anchoring produces confident nonsense.

The apparatus described in this piece is one instance of a grand-strategic anchoring practice. It is not the only possible instance; there are others, some articulated, some tacit. What matters is that anyone making consequential decisions in the AI era needs some grand-strategic anchoring practice, because tactical execution alone will produce systematic errors of a kind that compound. The Business Engineer is what I have built. Whether readers use this apparatus, build their own, or find another that works — the requirement itself is not negotiable in the era we are entering.

That is what The Business Engineer actually is. A grand-strategic apparatus for reading the territory of the AI era, composed of four layers stacked completely: a philosophy of structural reality, a theory of AI-era complex systems, a method of contextualized distillation, and a set of frameworks that emerge as outputs of the method rather than as the substance of the practice. Everything I have written under this banner in the last decade is an application of this stack to a specific domain. Everything I will write is the same. The stack is the practice. The frameworks are downstream.

The correction from framework to apparatus is not cosmetic. It changes what the reader is being asked to hold, and what the practice is claiming to be. Held complete, the stack does the grand-strategic work that most business analysis skips. That is the value. That is what distinguishes it from the tactical frameworks that dominate the field. That is why the practice has held up for a decade and why it will continue to hold up as the territory keeps moving.

Key Takeaways & Mental Models

Access My Harness Via The BE Platform!

Follow me also on The AI Supercycle!

Subscribe Now at 50% Discount, Expiring!

• Framework Is the Wrong Word — The Business Engineer is a grand-strategic apparatus with four layers: philosophy, theory, method, and frameworks. Frameworks are outputs of the apparatus, not the apparatus itself. Most analytical practices occupy only the fourth layer, which is why they produce tactical outputs dressed as strategy.

• Grand Strategy Is Reading the Territory — Not planning, not framing, not selecting routes. The specifically upstream work of understanding what reality is before deciding what to do about it. The Business Engineer operates at this altitude by design.

• The Five Philosophical Commitments — Structural knowability of reality; reality’s authority over the analyst; complexity as substance not noise; concentrated structural mass in complex domains; portable and actionable understanding as the criterion of success. Every commitment is defended against a specific failure mode in classical analysis.

• The Theory of AI-Era Complex Systems — Power-law distributions by structure; dissolving categorical boundaries; unbounded multi-scalar competition; opaque causal chains legible only in retrospect; fractal capability migration from cores to peripheries; multi-clock structural transformations. These are the load-bearing propositions the method is calibrated to.

• The Method Is One Layer, Not the Whole Practice — Contextualize, abstract, model, act, refine, revalidate. Six operational moves. The method’s validity depends on the theory it is calibrated to and the philosophy it is anchored in. Detached from either, the method becomes a technique.

• Frameworks Are Outputs, Not Doctrine — The AI Supercycle, the Map of AI, the AGaaS Trilogy, the Harness Trilogy, the Routing Paradigm, the Five Postures — each is a strategic map derived from grand-strategic reading of a specific territory. Each is provisional. Each is corrected when the territory moves.

• The Stack Has to Be Complete — Every partial version of the stack fails in a specific way. Philosophy without theory is philosophy of science. Theory without philosophy is defended ideology. Method without either is a misapplied technique. Frameworks without any are fossils. The complete stack avoids each failure specifically.

• The Apparatus Demands a Specific Discipline — Structural reading over narrative interpretation, tolerance for being wrong, capacity for compression, ability to hold multiple altitudes, refusal to import inappropriate frameworks. Users who cannot meet these demands will produce outputs that look like Business Engineer work and are not.

• Moving Territory Requires Grand-Strategic Anchoring — When reality is stable, tactical thinking can be gotten away with. When reality moves, tactical thinking produces confident nonsense. The AI era is moving-territory on every dimension that matters. Grand-strategic anchoring is not a luxury; it is what keeps analysis oriented as the territory shifts.

• The Correction from Framework to Apparatus Is Structural — Not cosmetic. It changes what the reader is being asked to hold and what the practice is claiming to be. Held complete, the stack does the grand-strategic work most business analysis skips. That is the value the practice claims and the value it can be tested against.

• The Practice Is Repeatable and Portable, Not Personal — The apparatus is not a set of doctrines dependent on the person who built it. It is a repeatable stack that anyone willing to meet the demands can operate. The specific frameworks I have produced are one path through the apparatus. Others exist. The apparatus is the invariant.

With massive ♥️ Gennaro Cuofano, The Business Engineer

The frame to hold onto: we are inside a 30-to-50-year supercycle, not a news cycle. Everything feels fast because we are living it in real time. But we have time to understand it, adjust to it, and position around it. So before the panic — the mechanism.

Why the Map Had to Be Redrawn

Back in March I added two layers to the Map of AI: a harness layer and a governance layer. This week validated both, hard.

Read more

Two frontier labs published usage data within weeks of each other. OpenAI’s The Shift to Agentic AI: Evidence from Codex and Anthropic’s latest Economic Index read like different projects — one obsessed with delegated workflows, the other with the economic footprint of artifacts. But place them on the same table and they collapse into a single finding, arrived at from opposite directions:

The surface, not the model, governs autonomy. The agentic surface — the harness — is becoming where value pools in the entire AI stack. And we can now read, from real usage data, exactly what stage of that transition we are in.

Most commentary misses this. These reports aren’t just describing two products. Read together, they are a calibrated instrument for measuring how far agentic adoption has actually progressed — because the three populations in the Codex data (individuals, organizations, and OpenAI’s own workforce) are not three customer segments. They are three points on a single timeline, separated only by how much adoption friction has been removed. OpenAI’s workforce is the future running early. Organizations are the present. Individuals are the recent past, still visible in the rearview.

This piece does four things: establishes the stage of adoption the data actually reveals, reads the convergence both reports refuse to state out loud, contrasts the two opposing business models built on top of it, and cascades the consequence through the Map of AI to show where value migrates next.

Access my harness with the exec plan!

Subscribe Now at 75% Discount, Expiring!

Follow me also on The AI Supercycle!

The Conversation Was a Transitional Form

Access my harness with the exec plan!

Subscribe Now at 75% Discount, Expiring!

Follow me also on The AI Supercycle!

The deepest tell in both reports is the same, and neither lab frames it as the headline: their own measurement apparatus broke.

• Anthropic says it plainly: “a chat transcript no longer fully captures how people are using AI.” They moved to higher-frequency sampling and an output classifier. When the interface stops being the right unit of measurement, it’s because AI stopped being something you consult and became something you deploy.

• OpenAI says the same thing structurally: the unit of analysis is no longer the conversation but the delegated workflow — one instruction that triggers an agent to inspect files, run commands, call tools, and produce artifacts autonomously. They warn outright that active users, chats, and message volume “may become less informative as agentic systems diffuse.”

Two independent measurement systems, both built around the conversation, both breaking the same way at the same time. That is not coincidence — it’s a phase change registering on two different instruments.

And both reports show the same proof that the surface, not the model, is what changed:

• OpenAI’s proof is internal cannibalization. Among OpenAI’s own workforce, Codex accounts for 99.8% of the work-related output the company’s employees generate across Codex and ChatGPT combined — meaning the conversational interface didn’t merely decline inside OpenAI, it was almost entirely replaced as the way work gets done.

• Anthropic’s proof is an autonomy gap that holds even when the model is identical. Across 26 of 31 output types, Claude Code runs at higher autonomy than chat or Cowork — and that gap persists when you hold the underlying model constant, which is the whole point: it isn’t the model behaving differently, it’s the surface permitting different behavior. The starkest illustration: the same blog-post task that takes 13 rounds of back-and-forth in chat collapses to a single prompt in Claude Code. Same model, same task, wildly different delegation. The only variable is the surface.

The abstraction: the conversational interface was scaffolding. The harness is the building. Everything downstream is a consequence of value migrating from the thing you talk to toward the thing you delegate to.

Reading the Three-Population Clock

Access my harness with the exec plan!

Subscribe Now at 75% Discount, Expiring!

Follow me also on The AI Supercycle!

Here is the analytical engine the rest of the piece runs on. OpenAI’s three populations form a natural time-lapse of agentic diffusion, and the spread between them tells you precisely how early we are.

The gradient, measured two ways

Look first at how many users touch the agentic surface at all (active users in the trailing 28 days):

• OpenAI workforce: ~98% — almost everyone.

• Organizations: 17.3% — fewer than one in five employees.

• Individuals: under 1% (0.7%) — effectively nobody.

Now look at how much of total work output flows through the agentic surface rather than the chat interface (share of output tokens, the rough unit of AI-generated work):

• OpenAI workforce: 99.8%

• Organizations: 63.3%

• Individuals: 16.5%

The two measures disagree violently, and that disagreement is the most important signal in either report. Among individuals, 16.5% of all output already runs through the agentic surface even though under 1% of users have adopted it — meaning the tiny minority who adopt use it so intensely they dominate output. The same logic, amplified, plays out in organizations: 17.3% of users generate 63.3% of output through the agentic surface. Adoption is not a thin film spreading evenly across many users; it’s a deep pool concentrating among a few intensive adopters.

Three stage-readings fall out:

• Stage zero for the mass market. With fewer than one in a hundred individual users on the agentic surface, the conversational interface still overwhelmingly owns the consumer base. Watch only individuals and you’d conclude agentic AI barely exists.

• Stage one — early majority — inside organizations. At 17.3% of users but 63.3% of output, organizations have already crossed the line where the majority of business work output flows through the agentic surface, even though most employees haven’t touched it. This is the market’s central misread: adoption looks early by seats and nearly complete by output.

• Stage three — near-saturation — already visible at OpenAI. Not a forecast but a shipped reality. OpenAI’s workforce isn’t representative — it’s a preview of the destination once cost, buy-in, training, and tooling friction approach zero (inside OpenAI, AI usage is free at the margin and knowledge-sharing is constant).

The intensity trap — why “% of seats” is the wrong clock

The divergence compounds when you zoom into a single job function. Among engineers in organizations:

• The agentic surface is just 26.8% of the average engineer’s output — and that figure alone makes adoption look early-stage and tentative.

• But it is 88.3% of the total output engineers generate as a group — because the heavy adopters route nearly everything through it, and they dominate the function’s total work.

The same gap appears in legal, a function nobody thinks of as agentic: 1.9% of the average legal user’s output, but 17.6% of the legal function’s total output. Read one number and legal is barely touched; read the other and a sixth of its work output already runs through the agentic surface.

The stage of adoption looks completely different depending on which clock you read. By seats: early. By output: well underway. Anyone reporting “percent of employees active” will conclude the transition is years away when, in output terms, it’s already half-done.

The convergence signal — the laggards move fastest

The clearest evidence of which way time runs is OpenAI’s internal time-lapse. In late 2025, OpenAI’s own usage looked like external organizations look today — engineers leading, everyone else near zero. Then:

• Engineers crossed 50% of their usage onto the agentic surface by January 2026 and passed 90% by March.

• Legal and recruiting sat near zero in January, climbed gradually to about 20% by early April — then jumped from roughly 20% to 75% in a single month.

The technical functions blaze a slow trail; the non-technical functions, once that trail exists, sprint down it. This slow-pioneer / fast-follower signature is exactly what you’d expect if the binding constraint is organizational learning rather than model capability — and it means the laggard functions in every enterprise aren’t permanently behind. They’re pre-inflection. The convergence inside OpenAI coincided with a deliberate internal push of training and feedback loops, which is the tell: the complement that unlocked the laggards was organizational effort, not a new model.

What this fixes the stage at

Synthesizing: we are at early majority for organizations and stage zero for individuals — but with output already concentrated and a convergence dynamic that compresses the remaining timeline. The friction is organizational, not technological: if it were capability, every population running the same models would look the same. They look wildly different. The constraint is access to systems, management expectations, workforce skill, and review processes — the complements, not the engine. That single fact is what makes the rest of the transition predictable.

Two Labs, Opposite Geometries, Same Insight

Access my harness with the exec plan!

Subscribe Now at 75% Discount, Expiring!

Follow me also on The AI Supercycle!

Both labs believe the harness is the future. They are building opposite go-to-market geometries on top of that shared belief — and the contrast is the strategic content.

OpenAI / Codex — The Consolidation Play

OpenAI is betting on one harness that absorbs everything.

• Codex is no longer pitched as a coding tool but as an “agentic coding and work platform.” The product milestones the report annotates — macOS launch, Windows launch, and tellingly a “Knowledge Work App Update” — trace a deliberate march out of the terminal and into general knowledge work.

• The systematization engine is the skill-and-plugin ecosystem: a SKILL.md workflow spec, packaged into plugin manifests that bundle app integrations and tool configuration. Skill use among weekly active users climbed from 5.4% to 26.6% in roughly three months — a near-fivefold rise that shows workflows being codified into reusable infrastructure rather than re-typed each time — and inside OpenAI it’s effectively universal at 96.2%.

• OpenAI ran the experiment on itself and shipped the result: it let Codex consume ChatGPT to that 99.8% work-token dominance. They are not theorizing that the conversational surface dies — they have already killed it internally and published the autopsy.

The bet: pull every workflow into one agent, own the harness, own the skill marketplace on top of it, and the conversational layer becomes a feature, not a product.

Anthropic / Claude Code + Cowork + Embedded Agents — The Proliferation Play

Anthropic is betting on many harnesses, embedded where work already lives.

• Rather than one super-surface, Anthropic spreads across surfaces at different autonomy levels: Claude Code (high-delegation technical), Cowork (multi-step knowledge work), and embedded agents inside the tools work already happens in — Excel, PowerPoint, Chrome, Design.

• The Economic Index keeps the augmentation framing: in high-value work, Claude produces more per turn (1.34× the output) and users engage more (1.53× the turns) — the two rise together, which is why Anthropic argues “more production from Claude does not mean less from the user.” It’s a deliberately less aggressive posture than OpenAI’s “let it replace the chat.”

• But Anthropic flags the expiry date on its own comfort: that augmentation equilibrium is partly an artifact of which surface people happen to use today. Claude Code is named as the leading indicator — the surface where the future autonomy curve is already visible. The human loop stays open mostly where the tooling hasn’t yet closed it.

The bet: embed an agent into every existing workflow rather than dissolve every workflow into one agent; meet the app where it is.

The Contested Question

Strip both strategies to the bone and they reduce to one fork:

Does the harness consolidate into one super-surface (OpenAI’s bet) or proliferate into many context-specific surfaces (Anthropic’s bet)?

Note the asymmetry, and how it maps onto the stage. OpenAI is reporting from stage three — it already ran consolidation on its own near-saturated workforce. Anthropic is reporting from the inflection point — augmentation holding today, with a pointed finger at where it breaks. One lab is telling you what happened after the transition; the other is telling you where to watch as it happens.

Cascading Through the Map of AI

Access my harness with the exec plan!

Subscribe Now at 75% Discount, Expiring!

Follow me also on The AI Supercycle!

The harness shift doesn’t stay in one place. It propagates through the stack, and each layer reprices. Reading bottom to top — and notice how the stage of adoption determines how far each repricing has gone:

• Compute / silicon — the unconditional winner. Agentic use is a demand shock, not a usage tweak. Inside OpenAI, the median worker’s output rose between 10× and 56× across job functions in seven months (Research 56×, Customer Support 32×, Engineering 27×, Legal 13× — the largest multiples landing on the functions that adopted latest, which is the convergence story again). Anthropic shows the same force from the cost side: tokens track wages, with about 44% of the wage-to-token relationship explained by the fact that higher-paid work produces more compute-intensive artifacts. Delegation doesn’t consume slightly more compute; it consumes an order of magnitude more — and because output concentrates before users do, the demand shock arrives ahead of the seat-adoption curve. This layer wins regardless of who wins the harness war above it.

• Model — commoditizing relative to what sits above it. Both reports independently conclude the surface matters more than the model. Anthropic states it directly (”product matters more than model”); OpenAI demonstrates it by showing the same model deliver radically different delegation depending on the harness. This is the AGaaS thesis showing up as physics — the model stays necessary, but value capture migrates upward. The engine becomes essential and unglamorous; nobody pays a premium for the engine once the vehicle around it determines the drive.

• Harness / orchestration — the NEW value layer, and the battleground. This layer barely existed in the old stack. Now it’s where autonomy is decided, where work gets systematized, and where the moat forms. The SKILL.md is becoming the modular unit of delegated work — the line of code of the agentic era. And the stage reads cleanly here too: skill adoption at 26.6% externally versus 96.2% inside OpenAI is the harness layer’s own adoption clock, running the very same friction gradient as every other measure.

• Application — collapsing INTO the harness. This is the AGaaS mutation made literal. Why open a SaaS app when the agent runs the workflow end to end? Codex absorbing documents, spreadsheets, and slide decks as plugins is applications dissolving into skills. The app stops being a destination and becomes a capability the harness invokes. Anthropic’s embedded-agent bet (Claude in Excel, in PowerPoint) is the explicit hedge — keep the app, put the agent inside it.

• Judgment / oversight — where the human relocates. Both reports converge hardest here. As execution delegates, human effort moves to delegation, supervision, review, and integration, and the returns to domain expertise rise. The clearest prototype: 28.6% of OpenAI users run five or more agents at the same time at some point each week, and the most intensive 1% log around 71 hours of agent runtime inside a single day — which is only possible by running many agents in parallel around the clock. That is no longer a person using a tool; it’s a human managing a team of agents. This is the Judgment Layer, confirmed empirically by two independent datasets — and because it’s barely developed anywhere except the frontier, it’s the layer with the most adoption runway still ahead of it.

The reading rule that falls out:

Value migrates model → harness → skill marketplace. Pricing power leaves the model and lands on whoever controls the surface and its reusable workflows. Build at the harness; meter at the compute layer; defend at the skill layer. And read the stage by output, never by seats.

The Skill Standard and the Hidden Dependency

Access my harness with the exec plan!

Subscribe Now at 75% Discount, Expiring!

Follow me also on The AI Supercycle!

Three forces decide the next 18 months.

The skill becomes the contested standard

If the SKILL.md is the line of code of the agentic era, then the format war is the platform war.

• OpenAI’s SKILL.md-plus-plugin format is a land-grab for the standard — own the authoring format, own the ecosystem.

• A cross-harness, portable skill format is the open-web counter-move — skills that run on Codex, Claude Code, and any future surface, owned by no single lab.

• The load-bearing question: is the skill portable, or is it locked to a harness? This is the most leverage-rich fork in the space, and it’s being decided now, in authoring-format choices that look like documentation but are actually strategy.

The cross-layer dependency nobody is pricing

Here is the argument neither report can see, because it lives between the layers.

The harness’s value depends entirely on diversity preserved in the model beneath it. The cheap training default now sweeping the field — self-distillation, with its “likely-gets-likelier” dynamic — quietly collapses a model’s ability to find multiple solution paths. It optimizes the visible number (average accuracy) while eroding the invisible capability (the ability to route around a blocked path). It’s economic concentration as a training artifact: rich-get-richer at the level of model weights, the Barbelled Distribution reasserting itself inside the model.

Now connect it to the autonomy trend both labs document:

• With a human in the loop every turn, a brittle one-path model gets corrected — the dead end is caught and rerouted by the person.

• When you hand the full multi-step trajectory to an agent in a single prompt — exactly what Claude Code and Codex make possible — brittleness becomes unrecoverable, because there’s no human turn in which to catch the blocked route.

The conclusion is uncomfortable and original:

The consolidation bet — one harness, full delegation — carries a hidden dependency on a training choice happening two layers down. The Judgment Layer can’t save you if the model beneath it can only find one path. Diversity collapse bites hardest exactly where autonomy is highest. The cheap training method and the agentic deployment trend are on a collision course — and the fix (diversity-aware training) exists but isn’t yet the cheap default.

The barbell resolution

So which bet wins — consolidation or proliferation? The honest answer, consistent with everything above, is that the harness barbells.

• Consolidation wins where work is digital, modular, and verifiable — software first, which is precisely the leading edge in both reports. One super-harness absorbing the full software life cycle is already happening inside OpenAI.

• Proliferation wins where work is embedded in legacy tools and human review is non-negotiable — regulated industries, relationship-driven roles, judgment-heavy domains. Here the embedded-agent strategy beats the dissolve-everything strategy.

The harness doesn’t pick one winner. It splits — the barbell distribution reasserting itself one layer up the stack. The two labs aren’t wrong about each other; each is right about a different end of the same barbell.

Key Takeaways & Mental Models

Access my harness with the exec plan!

Subscribe Now at 75% Discount, Expiring!

Follow me also on The AI Supercycle!

• The conversation was scaffolding; the harness is the building. Both labs’ measurement systems broke the same way at the same time — the surest sign of a phase change. AI moved from something you consult to something you deploy.

• Read the stage by output, never by seats. Organizations sit at 17.3% of users but 63.3% of output; engineers at 26.8% of the average user’s output but 88.3% of the function’s total. Adoption looks early by headcount and nearly complete by work produced — and the second number is the true one.

• The constraint is organizational, not technological. Same models, three wildly different adoption levels across individuals, organizations, and OpenAI. The binding inputs are access, management expectations, skill, and review processes — the complements, not the engine. That’s why the transition is predictable, and why laggard functions are pre-inflection, not permanently behind.

• Surface beats model. Proven twice, independently: Codex eating ChatGPT to 99.8% of internal work tokens; the autonomy gap surviving with the model held constant (13 chat turns → 1 Claude Code prompt). Value capture migrates up from the model to the harness.

• The SKILL.md is the line of code of the agentic era. Systematization — codified, reusable workflows — is where the moat forms. Skill adoption went 5.4% → 26.6% in a quarter; the authoring format that wins becomes the platform.

• Two business models, one fork: consolidate or proliferate. OpenAI pulls every workflow into one harness; Anthropic embeds a harness into every workflow. The layer barbells — consolidation for digital/verifiable work, proliferation for embedded/judgment-heavy work.

• The Judgment Layer is now empirical, not theoretical. As execution delegates, humans relocate to delegation, oversight, and integration; returns to domain expertise rise. The 28.6% running five or more concurrent agents are the prototype of the future worker — and it’s the layer with the most runway left.

• The hidden cross-layer trap: maximum autonomy on top of one-path models is a collision, not a synergy. The harness’s value is mortgaged to a diversity choice two layers down — currently being written in the cheapest, most brittle way available.

The frontier of AI is no longer about asking systems for answers. It’s about managing systems that act — and the war for who owns that management layer, and on what terms, is the only fight that matters now.

Recap: In This Issue!

The Conversation Was a Transitional Interface

• The chatbot was never the final destination for AI adoption.

• Both OpenAI and Anthropic show that the interface is shifting from conversation to delegated execution.

• The unit of interaction is no longer a prompt, but an autonomous workflow.

• AI is evolving from a tool users consult into a system users deploy.

We Are Measuring AI Adoption Incorrectly

• User counts and message volume no longer capture how AI is being used.

• The meaningful metric is work completed rather than conversations initiated.

• A small percentage of users already accounts for the majority of agentic output.

• Adoption spreads through intensity before it spreads through ubiquity.

Organizations, Not Models, Are the Bottleneck

• The same frontier models produce vastly different adoption curves across different populations.

• The limiting factors are organizational readiness, governance, workflow redesign, training, and trust.

• Technology is no longer the primary constraint to adoption.

• The next wave of AI diffusion depends more on organizational transformation than on model improvements.

The Harness Has Become the New Value Layer

• The interface now determines how much autonomy AI can achieve.

• Holding the model constant, agentic environments consistently outperform conversational ones.

• Orchestration, memory, tool use, and workflow execution have become the new sources of competitive advantage.

• Value is migrating upward from the model toward the harness.

OpenAI and Anthropic Are Converging on the Same Future

• OpenAI is building a universal harness that absorbs every workflow into a single operating environment.

• Anthropic is embedding autonomous agents into existing software and enterprise workflows.

• One strategy emphasizes consolidation, the other proliferation.

• Both ultimately point toward the same destination: work executed by autonomous agents.

The Entire AI Stack Is Being Repriced

• Compute becomes increasingly valuable as autonomous agents consume significantly more inference.

• Foundation models become relatively commoditized as orchestration layers capture differentiation.

• Applications evolve from standalone destinations into capabilities invoked by agents.

• Human value shifts away from execution toward supervision and decision-making.

Skills Become the Software of the Agentic Era

• Reusable workflows are emerging as the fundamental primitive of autonomous work.

• Standards such as SKILL.md represent the beginning of a new application layer.

• The platform controlling skill creation and distribution gains long-term strategic leverage.

• Future ecosystems may compete less on models than on reusable workflows.

The Judgment Layer Becomes Human Work

• Humans increasingly define objectives instead of executing individual tasks.

• Expertise shifts toward reviewing outputs, coordinating multiple agents, and making strategic decisions.

• The future knowledge worker manages autonomous systems rather than operating software directly.

• Judgment becomes the highest-value layer of work.

Agentic AI Has a Hidden Dependency

• Highly autonomous systems require models capable of exploring multiple reasoning paths.

• Training methods optimized for efficiency risk reducing reasoning diversity.

• Greater autonomy amplifies the consequences of brittle reasoning.

• The future of agentic AI depends not only on better interfaces, but also on preserving model diversity.

The Harness Will Follow a Barbell Distribution

• Universal harnesses are likely to dominate highly digital, modular, and verifiable work.

• Embedded agents will remain preferable in regulated, relationship-driven, and judgment-intensive environments.

• The future is unlikely to converge around a single interface.

• Consolidation and proliferation will coexist across different categories of work.

The Industry Is Entering Its Next Phase

• The market continues to debate chatbots while the real transformation happens one layer above.

• The next competitive battle is no longer about building the smartest model.

• It is about controlling the operating layer through which autonomous work is delegated, orchestrated, and governed.

• The AI industry is approaching the final organizational bottleneck before mass-scale agentic adoption.

With massive ♥️ Gennaro Cuofano, The Business Engineer

There are four moats in production today, one for each data paradigm:

Access my harness with the exec plan!

Follow me also on The AI Supercycle!

Subscribe Now at 50% Discount, Expiring!

• The Corpus Moat — built by pretraining, eroding as the public web is exhausted and synthetic data closes gaps.

• The Verifier Moat — built by RLVR on domain-specific reward signals, building into a new asset class for reasoning-heavy verticals.

• The Harness Moat — built by agentic-loop infrastructure, active and where most current moat construction is happening.

• The Container Moat — built by closed data loops inside a customer’s environment, nascent but the deepest position in the stack.

Each moat is built by a different data pipeline. Each sits at a different altitude in the Map of AI. Each has a different lifecycle stage. Each captures a different kind of intelligence — and exposes a different binding constraint when you try to build it.

Read more

He calls them Prototyper, Builder, Sweeper, Grower, and Maintainer. Some people span two of these, sometimes three. The archetypes cut across disciplines — some designers operate as Prototypers, some as Sweepers; the same is true for engineers, PMs, data scientists. And the right mix changes with where a product is in its lifecycle.

The framing is provisional — Cherny closes with a question, not a claim: maybe product roles of the future will look more like this, and less like the domain-specific roles of today. The provisional tone is correct. The observation itself is more important than its provisionality.

What he is describing is not a curiosity inside one team. It is the visible surface of a structural change that has been working its way through software work for three years, and that is now legible enough to name. The taxonomy that organized software work for the last two decades — we hire engineers, PMs, designers, data scientists, and they collaborate across functional lines — is being replaced by a lifecycle taxonomy that organizes the same people differently.

The new question is not what discipline you are trained in. It is what posture and intersection you take toward the work at this stage.

This piece does three things:

• Anatomizes each of the five postures in operational detail — what the posture is, how it shows up in real work, its binding constraint, its failure modes, and where it ships value versus where it destroys it

• Builds a proper structural framework — the Posture Lifecycle — naming five stages of an AI-native startup and the composition rule at each, including transition signals and characteristic failure modes

• Names the implications for hiring, for careers, and for the founders building these companies

Access my harness with the exec plan!

Subscribe Now at 50% Discount, Expiring!

Follow me also on The AI Supercycle!

Join theYearly Premium Membership To Get The Builder-PM

Access For Yearly Premium Member!

Or

Get It Separately

Read more

What followed was a long, deliberate migration. Not a productivity hack. Not a workflow tweak. A reorganization of where I stood inside my own work, and inside the AI economy that was rebuilding itself around all of us. It took the better part of eighteen months to complete, and the three pieces I wrote at the end of it — the Why, the Life, the Society — were the field notes of someone who had finally arrived at the destination and could look back along the path.

This piece is what’s visible only from the end of the journey. The three essays were never three essays. They were one phenomenon observed from three altitudes, recorded in sequence as the migration completed, and the structure that holds them together is more important than anything any of them said alone.

That structure is the thing worth synthesizing. Not the conclusions — the architecture beneath them.

Access my harness with the exec plan!

Subscribe Now at 75% Discount, Expiring!

Follow me also on The AI Supercycle!

The migration in one sentence

Access my harness with the exec plan!

Subscribe Now at 75% Discount, Expiring!

Follow me also on The AI Supercycle!

Here is what eighteen months taught me, compressed into the one sentence the trilogy was always circling:

AI’s scaling laws keep relocating capability outward — from inside the model to the harness around it. That migration produces leverage at the personal scale, restructuring at the organizational scale, and friction at the societal scale. The bedrock that doesn’t move at any scale is authorship.

Every page of every essay is downstream of that sentence. The Why piece is the migration observed at the level of the AI industry over four years. The Life piece is the same migration observed inside one person’s career. The Society piece is the same migration observed across an entire economy at once. The mechanism is identical. Only the unit of analysis changes.

But sameness across scales isn’t a coincidence. The migration is fractal, and the architecture it produces is fractal too. That is what the synthesis exists to draw.

Three altitudes, deliberately distinct

Access my harness with the exec plan!

Subscribe Now at 75% Discount, Expiring!

Follow me also on The AI Supercycle!

I wrote the three pieces in the order I did because each one had to stay at one altitude to do its work. Mixing them would have blurred the structure that’s only visible when you see the altitudes side by side.

Altitude 1 — the macro forces (the Why, written last). The view from above the AI industry. Pre-training scaling hit a wall in 2024. The frontier didn’t stop; it relocated, first to test-time reasoning (Sept 2024), then to agency (2025), then to swarm orchestration (2026). Four eras in four years, each shorter than the last. The unit of work climbed turn → task → goal → operation. The business model mutated from SaaS to AGaaS. The form factor migrated from screen to phone to ambient surface. This was the engine driving everything else, and it was identifiable from primary sources — Amodei’s 2024 statements, OpenAI’s o-series release cadence, MCP’s adoption curve, the Linux Foundation handoff in December 2025. None of it was prediction; all of it was retrospective accounting on what had already happened.

Altitude 2 — the personal response (the Life, written first). The view from one chair, day to day. Eighteen months of personal restructuring compressed into a description of what the destination looks like. Operating commoditized; framing became the edge. Six framing moves replaced two years of operator instincts. The harness — swarm, self-improving loop, shared memory, gates at the high-stakes edges — became the architecture I worked through instead of the chat window I worked inside. The frame I set in the morning steered a swarm through the day. The thin surface — frame in, gate out — replaced the desk. The harness ran remote; I carried the handle. This was the destination viewed from inside, with the eighteen months of migration mostly invisible behind it.

Altitude 3 — the collective consequences (the Society, written third). The view from above the economy. What the macro forces in Altitude 1 do to the millions of people who can’t or won’t make the migration in Altitude 2. The principal/operator split shows up in measurable data — Anthropic’s 70/80 planning split, the 5× expert-novice output gap, Gallup’s 3× layoff risk for non-adopters. Companies fork into shrinkers (State Farm: 19,000 contracts rewritten, −40% income) and amplifiers (Block: BuilderBot, 15% of code, 1,500 PRs/week). The middle dissolves quietly through macro shocks. AGaaS bottlenecks on the outcome-definition problem most companies can’t solve. The substrate taxes everyone — even the opt-outs paying $200 more for an iPhone because AI absorbed the HBM supply.

Each altitude is structurally complete on its own. None of them is structurally complete on its own. The phenomenon is only visible when you stack all three and notice that the same shape appears in each of them.

That repeating shape — what I’m going to call the fractal architecture — is the trilogy’s deepest insight, and the thing none of the three pieces could carry alone.

Four patterns that repeat at every scale

Access my harness with the exec plan!

Subscribe Now at 75% Discount, Expiring!

Follow me also on The AI Supercycle!

Each of these is a structural rhyme — a shape that appears identically in the Why, the Life, and the Society. The repetitions are not analogies. They are the same mechanism, observed at different magnifications.

1. The forcing cycle is fractal

Access my harness with the exec plan!

Subscribe Now at 75% Discount, Expiring!

Follow me also on The AI Supercycle!

The macro version: when the current scaling axis hits diminishing returns, the frontier relocates outward. New axis → new unit of work → new business model → new form factor → old layer commoditizes → repeat. This ran four times in the AI industry between 2020 and 2026, with each cycle shorter than the last.

The same cycle ran inside my own career over the same period. The skill that produced value in 2023 — operating a chat model well — commoditized by 2025. The edge moved up one rung to framing. Framing-as-craft is itself starting to commoditize now, in 2026, which means it will move up one more rung to orchestration over the next year, then to something beyond that the year after. The arc of one career inside eighteen months mirrors the arc of an industry inside four years. Same shape; smaller scale; faster clock.

And the same cycle is now running inside society. The shift from SaaS to AGaaS isn’t a pricing change — it’s a forcing cycle relocating value outward at the level of the entire commercial economy. The org chart inverts because the old shape (wide operating base, narrow decision-making top) is what gets automated. The middle dissolves because operating commoditized. Governance becomes the scarce resource because authorship is the one layer that can’t commoditize, and there is no societal version of it yet. One mechanism, three resolutions, all of them compressing. This is why the trilogy keeps feeling like it’s accelerating — every altitude is running the same engine at the same time, and the engine speeds up at every level simultaneously.

2. The harness is fractal

Access my harness with the exec plan!

Subscribe Now at 75% Discount, Expiring!

Follow me also on The AI Supercycle!

At the personal scale, the harness is what one person builds around their own work: a swarm of specialist agents, a self-improving loop, a shared memory layer, approval gates at the edges where stakes are high. One person plus a harness produces what used to take a department.

At the company scale, the harness is what one company becomes when it restructures around outcomes. Block’s BuilderBot is the personal harness from the Life piece, run at company scale. A frame set by a human (a Slack message). A swarm of specialist agents executing in parallel (1,500 PRs/week). One source of truth, gates at high-stakes decisions, the orchestration as the work. The pattern is identical. The only difference is the size of the swarm and the weight of the gates.

At the economic scale, the harness is what the AI economy itself is becoming. The frontier labs are running negative-margin subscriptions to acquire workload signal (a self-improving loop at lab scale). MCP standardizes how agents connect to tools (a shared memory layer at economy scale). The Agentic AI Foundation under the Linux Foundation is the gate-and-governance structure forming around the largest swarm of all. The labs are building, at economy scale, the same architecture I built at desk scale, for the same structural reasons.

The harness is not a metaphor scaled up or down. It is a single architectural pattern that emerges wherever there’s a principal with a frame, a swarm of executors, a need for coherence, and stakes worth gating. Every scale that meets those four conditions builds the same architecture. Inevitably. Because there is no other architecture that solves the problem.

3. The bedrock is fractal — and this is the most important rhyme

Access my harness with the exec plan!

Subscribe Now at 75% Discount, Expiring!

Follow me also on The AI Supercycle!

At every scale, the question of what doesn’t commoditize gets the same structural answer. The form changes; the structure is identical.

At the personal scale: authorship. Wanting a particular outcome, choosing which tradeoffs are acceptable, answering for the result when it ships. Not a skill. A position. The bedrock the churn can’t reach because it isn’t a capability to be acquired faster by something faster than you.

At the company scale: defining outcomes. The AGaaS transition’s load-bearing problem isn’t pricing — it’s that most companies can’t articulate what their outcomes actually are at the granularity an agent contract requires. Solving that requires the company itself to do, at company scale, exactly what the individual did at personal scale: figure out what it wants, decide which tradeoffs are acceptable, and answer for the result. Defining outcomes is corporate authorship. The same bedrock, held by an organization instead of a person. The work it takes to define outcomes well is the work it takes to be the principal of a company-scale harness.

At the societal scale: governance. Who is allowed to be the principal of a swarm that can author at scale? Who is accountable when one goes wrong? Whose will and whose liability govern an agent that ran for fifty steps without supervision? These are not technical questions. They are the societal version of “wanting, choosing, and answering for the result.” Governance is societal authorship. Same bedrock, held by political and legal institutions instead of by a person or a company.

The trilogy keeps ending on the same note because the same answer keeps being correct at every altitude. It isn’t three different conclusions that happen to rhyme. It is one conclusion, restated at three scales, because the bedrock is the same shape no matter how far up or down you stand.

And here is the practical implication, which only becomes visible from the synthesis: the muscle you build to be the principal of your own workflow is the same muscle companies need to define their outcomes, which is the same muscle societies need to govern their swarms. Personal authorship trains the capacity for corporate authorship trains the capacity for societal authorship. The trilogy isn’t a sequence of unrelated arguments. It’s a ladder where every rung uses the same muscle and where climbing one rung makes the next one possible.

4. The fork is fractal — and it doesn’t end

Access my harness with the exec plan!

Subscribe Now at 75% Discount, Expiring!

Follow me also on The AI Supercycle!

At every scale, the system splits along the same line: between those who restructure around the harness and those who pay for not doing so.

At the individual scale: principal vs. operator. The 5× output gap between expert and novice using the same tool. The 3× layoff-risk gap between adopters and holdouts. The fork measured from both sides simultaneously.

At the company scale: amplifier vs. shrinker. A 100-FTE team becomes either 150 (build to multiply output) or 30 (cut to save cost). Block on one side; State Farm on the other. Two paths from the same input, with no stable middle.

At the national scale: participant vs. periphery. Countries that organize around AI as substrate vs. those that try to opt out. The opt-outs pay the tax anyway — in goods, energy, talent, attention — but get none of the leverage. The substrate doesn’t ask permission.

Three forks. Identical shape. The dividing line at every scale is whether the actor restructures around the harness or doesn’t, and the gap between the two paths compounds over time at every scale. This is the structural reason the harness society is going to be uncomfortable for a long time. The same forking choice keeps reappearing at every level of the system, with no resting place where the fork doesn’t apply, and the cost of the wrong choice compounds at every scale.

What eighteen months of migration produces, viewed from the end

Access my harness with the exec plan!

Subscribe Now at 75% Discount, Expiring!

Follow me also on The AI Supercycle!

Stack the four fractal patterns and the trilogy compresses into a sentence that contains the whole journey:

Scaling migrated outward; capability followed it; a fractal harness formed at every level of the system from one person’s desk to the world economy; authorship is the bedrock that holds at every scale; and at every scale, the system forks between those who restructure around the new architecture and those who pay for not doing so — and that fork doesn’t end.

That sentence is the field report from eighteen months of moving from one position to another. None of the individual pieces could carry it because each was constrained to one altitude. The synthesis is what becomes visible once you stop moving and look back along the path.

The deeper insight — the one that justifies the trilogy as a unit — is this: the migration is the same shape no matter where you stand, but it has to be made wherever you stand. Reading about my migration doesn’t make yours. Reading about Block doesn’t restructure your company. Reading about the substrate tax doesn’t change the political answer. The structure is fractal; the work to migrate through it is not transferable. Each level of the system has to do the migration at its own scale, with its own actors making its own version of the principal/operator choice.

That’s why the trilogy ends, in all three pieces and in this synthesis, on the same question: who takes on the wanting, the choosing, and the answering at your scale? That question is the only one that matters at any altitude. The migration is over for me. The migration is barely starting for most readers. The migration has not begun, in any serious form, at the societal scale. And the clock is the clock the Why piece established: each cycle shorter than the last, with less time to migrate before the next layer commoditizes.

What the trilogy still can’t answer

Access my harness with the exec plan!

Subscribe Now at 75% Discount, Expiring!

Follow me also on The AI Supercycle!

Honest about the limits, because a synthesis that pretends to be complete is just a sales document.

The apprenticeship gap. If operating-as-training-ground is the layer being automated, where does the next generation of principals come from at any scale? At the personal scale, the answer is “from the current generation, until it retires.” At the company scale, the answer is “from Block, until competitors learn the restructure.” At the societal scale, the answer is unknown. Nobody — including me — has articulated how a society replenishes its principal class once the apprenticeship pipeline that used to make principals out of operators is gone. This is the most important unanswered question in the entire transition. The trilogy can describe it. The trilogy cannot answer it. The apprenticeship gap is the open edge of the structure at every altitude, and it is the thing that will, eventually, determine whether the harness society stabilizes or collapses.

The governance vacuum. The bedrock at the societal scale is governance, and the trilogy points at the question without filling it. The labs and the hyperscalers will not answer it — they will optimize around whatever answer the rest of the system produces. The answer needs to come from somewhere else — legislators, courts, professional associations, new institutions that do not yet exist — and right now it is not coming from anywhere. The trilogy describes the vacuum. The trilogy cannot fill it. The political question of the decade is sitting open, and no one has begun to seriously address it.

The compression of compression. Each forcing cycle has been shorter than the last: ~4 years → ~1 year → ~1 year → now. If the trend continues, the next relocation arrives faster than this one did, and the time anyone has to migrate to the new layer shrinks toward zero. At some point the migration speed exceeds human adaptation speed at the personal scale, organizational adaptation speed at the company scale, and political adaptation speed at the societal scale — possibly all three at once. The trilogy doesn’t say what happens then because nobody knows. It might not be possible to know until we get there.

These three open edges are the honest closing of the synthesis. They are not weaknesses in the analysis. They are limits of the phenomenon — and naming them is the only way the trilogy can end without pretending to know more than it does.

Key Takeaways & Mental Models

Access my harness with the exec plan!

Subscribe Now at 75% Discount, Expiring!

Follow me also on The AI Supercycle!

The Fractal Harness — The harness is not a metaphor. It is a single architectural pattern — authoring core, swarm of executors, shared memory, gates at high-stakes edges — that emerges wherever there is a principal, a frame, and stakes worth gating. It appears at every scale from one person’s workflow to the AI economy itself. Same shape; different sizes; identical mechanism.

The Fractal Bedrock — The position that doesn’t commoditize at any scale is whoever takes on the wanting, the choosing, and the answering. At the personal scale, authorship. At the company scale, defining outcomes. At the societal scale, governance. Same structure, three altitudes, and the muscle that builds one builds the next.

The Fractal Fork — At every scale, the system splits between those who restructure around the harness and those who pay for not doing so. Principal vs. operator. Amplifier vs. shrinker. Participant vs. periphery. The shape is identical; only the units change. And the fork compounds at every scale simultaneously.

The Single Migration — All three pieces describe one phenomenon: capability migrating outward from the model to the harness around it. The Why traced it at industry scale. The Life traced it inside a person. The Society traced it across everyone else. The mechanism is the same; the unit changes; the work of migrating is not transferable across units.

The Compression of Compression — Each forcing cycle is shorter than the last. The time available to migrate to the new layer shrinks at every iteration. This is the open edge of the structure at the personal, organizational, and political scales — and the limit that may eventually decide whether the harness society stabilizes or collapses under its own speed.

Recap: In This Issue!

The Trilogy Was Always About One Thing

The three essays (The Why, The Life, and The Society) are not separate arguments.

They are the same phenomenon observed from three different altitudes:

• Industry

• Individual

• Society

The core thesis:

AI’s scaling laws continue to relocate capability outward, from the model into the harness around it. That migration creates leverage at the personal level, restructuring at the organizational level, and friction at the societal level. Authorship remains the bedrock at every scale.

The Migration Is Fractal

The most important insight in the synthesis is that the same structural patterns repeat across scales.

The same dynamics shaping frontier AI labs are shaping:

• Individual careers

• Company structures

• Entire economies

The mechanism remains constant.

Only the unit of analysis changes.

Scaling Didn’t Stop. It Moved

The dominant narrative is that AI scaling slowed when pre-training hit diminishing returns.

The argument here is different:

Scaling never stopped.

It relocated.

The progression looks like:

• Pre-training scaling

• Test-time reasoning

• Agentic systems

• Swarm orchestration

Each transition pushes capability outward from the model into the surrounding system.

The harness becomes the new scaling surface.

The Harness Is the New Operating Layer

At the personal level, the harness consists of:

• Specialist agents

• Shared memory

• Self-improving loops

• Approval gates

• Orchestration systems

The chat interface becomes secondary.

The harness becomes the primary environment for work.

The shift is from operating tools to framing systems that operate tools.

The Same Architecture Appears Everywhere

One of the strongest ideas in the piece is the concept of the Fractal Harness.

The pattern repeats at every scale:

• Individual harnesses

• Company-scale harnesses (e.g., Block)

• Economy-scale harnesses (e.g., MCP, agent ecosystems, frontier labs)

The components are always similar:

• A principal

• A frame

• A swarm of executors

• Shared memory

• Governance gates

Different scale.

Same architecture.

Authorship Is the Bedrock

The trilogy repeatedly arrives at the same conclusion.

What survives automation is not skill.

It is authorship.

At different scales authorship takes different forms:

• Personal scale → authorship

• Company scale → defining outcomes

• Societal scale → governance

The underlying structure remains identical:

Wanting. Choosing. Answering for the result.

The Fork Repeats at Every Scale

The synthesis introduces the concept of the Fractal Fork.

The system repeatedly splits into two groups:

Individuals

• Principals

• Operators

Companies

• Amplifiers

• Shrinkers

Countries

• Participants

• Periphery

The dividing line is always the same:

Whether an actor restructures around the harness or resists it.

The Real Question Is Not Technology

The trilogy ultimately becomes less about AI and more about responsibility.

The recurring question at every level is:

Who takes responsibility for wanting, choosing, and answering?

That question determines:

• Individual leverage

• Organizational effectiveness

• Societal governance

The technology changes.

The accountability structure does not.

Three Problems Remain Unsolved

The synthesis explicitly identifies three open questions.

The Apprenticeship Gap

If operators become automated, where do future principals come from?

The traditional path from execution to judgment may disappear.

The Governance Vacuum

Who governs large-scale agentic systems?

No institution currently owns this responsibility.

The Compression Problem

Each transition cycle is becoming shorter.

Eventually adaptation may become slower than the rate of change itself.

The Core Insight

The trilogy compresses into a single idea:

Capability is migrating outward from the model into the harness around it. As that migration occurs, the same patterns repeat at every scale: leverage, restructuring, friction, authorship, and ultimately a fork between those who adapt and those who pay the cost of not adapting.

The harness is not the story.

The migration is the story.

The harness is simply the structure that emerges wherever that migration arrives.

With massive ♥️ Gennaro Cuofano, The Business Engineer

As usual, if you follow the outside chatter, the narrative is that it’s all over: the bubble is bursting, token consumption has plateaued, and the AI boom is losing momentum. I don’t spend much time debating whether we’re in a bubble. Focusing on the short-term financials of the most consequential industry of our time misses the bigger picture.

My job as an analyst is to explain what comes next. And today I can tell you this with confidence: there has never been a wider gap between perception and reality in the AI industry. Beneath the headlines, AI continues to accelerate. What we’re witnessing is not the end of the cycle, but the final bottleneck before mass adoption.

Access my harness with the exec plan!

This is why I’ve also spun off The Business Engineer into The AI Supercycle.

Subscribe Now at 75% Discount, Expiring!

You have probably noticed a strange split in the AI story this year. The demos are extraordinary. Agents that write working software run for hours on their own and manage portfolios of parallel tasks. The benchmarks climb each quarter; every keynote promises an autonomous workforce around the corner.

And then you go back to your actual job. You still type into a chat window. The “agent” your vendor sold you needs hand-holding to file an expense report. The CRM, the spreadsheets, the ticketing system you actually run on haven’t fundamentally changed. The most useful AI in your week is still a glorified assistant you check turn by turn.

This split is usually explained away as adoption lag. The technology is here, the story goes; users and companies just need to catch up. That explanation is wrong, and the way it is wrong matters — because it sends money and attention to the wrong places.

The split exists because three things that look like separate problems are actually one problem wearing three costumes:

• Agents that don’t quite work yet at the frontier of real-world tasks

• Users who won’t leave the chat window for anything that matters

• Traditional software the market keeps funding instead of agent-native replacements

These are not three failures of imagination. They are three rational responses to the same missing piece of infrastructure.

And it’s about verification.

Access my harness with the exec plan!

Subscribe Now at 75% Discount, Expiring!

Follow me also on The AI Supercycle!

The AI Supercycle

The Topology of The AI Supercycle

Over the years, my research on The Business Engineer has turned into the AI Supercycle…

Read more

12 days ago · 44 likes · Gennaro Cuofano

Read more

Eric was one of the people Anthropic’s founders consulted when they were architecting the company. What follows is the conversation, distilled in the four-layer structure Business Engineer readers know.

Get The Book Now!

The Setup

Ries is making a structural argument, not a moral one. He doesn’t want you to be a better person. He wants you to install load-bearing walls before the financial-gravity earthquake arrives. The thesis: every observed competitive advantage at Anthropic, Costco, Patagonia, Novo Nordisk, Tony’s Chocolonely recurses down to two ingredients — structure and ethos. Everything else is downstream.

Five things to know

• Shareholder primacy is forty years old, not eternal: Until the late 1970s, U.S. corporations had to declare a specific purpose and a public benefit just to incorporate. Single-purpose profit-maximization was enacted through a series of Delaware court cases in the 1980s. It is not ancient wisdom — it is a recent legal mutation that can be re-architected with a two-page filing.

• Founder mode solves the wrong problem: It addresses immediate control. It does not address succession. The founder is not immortal. The structure is.

• The Anthropic Recursion is the diagnostic: Lower inference cost → better architecture → better team → top talent picks them → trust in character → culture resists corruption → structure + ethos. Run the cascade on any winning company. You will land in the same bedrock.

• The mission lock is a competitive moat, not a moral indulgence: Tony’s Chocolonely. Novo Nordisk. Vanguard. Anthropic. Once you accumulate enough “exceptional” cases, the rule of inevitability falsifies itself.

• Harder is easier: Upfront governance friction — PBC filing, fiduciary commitments, mission guardian structure — creates counter-gravity. It reduces long-term coordination cost. The companies that skip it pay every quarter in talent, trust, and pricing power.

What it means

For AI-era founders, this is not theology — it is procurement spec. The companies that win the talent war, retain the most demanding users, and survive sovereign-scale pressure will be the ones whose charter, board structure, and operating culture are aligned around purpose before they are tested. The ones that aren’t will be hollowed out on schedule.

Layer 1 — Architecture: The Forty-Year Default

Unlock The Full Interview Notes!

Read more

For two years, AI was a CIO line item and a CEO talking point. In 2026 it became a CFO problem, because the economics finally turned legible — and unforgiving.

The core mechanism is a paradox most finance teams still misread:

The cost of intelligence is collapsing while the cost of deploying intelligence is exploding.

The numbers make the tension concrete:

• Unit cost is in free-fall. Achieving GPT-4-level reasoning cost roughly $60 per million tokens in early 2024. By the start of 2026, high-efficiency models deliver comparable reasoning for $0.30–$0.75 per million — a decline of over 98% (TokenRing / 2026 Unit Economics Reckoning).

• Total spend is in free-flight. The average enterprise AI budget grew from ~$1.2M/year in 2024 to ~$7M in 2026, with some Fortune 500 firms reporting monthly inference bills in the tens of millions (Oplexa, AI Inference Cost Crisis 2026).

• Inference, not training, is now the bill. Inference has grown to roughly 80–90% of total AI compute consumption and ~85% of the enterprise AI budget.

The reason cheaper tokens produce bigger bills is structural, and it is the single most important sentence in this guide:

The world moved from a per-query model to a per-workflow model — where one action can trigger dozens of model calls — so lower cost per token multiplied by exploding token volume increases total spend (Zenskar, Token-Based Pricing: The CFO’s Guide 2026).

As companies move from chatbots to thousands of autonomous agentic workflows running 24/7, the line item that used to be a rounding error becomes the budget.

The substrate for everything below: a token is the unit of intelligence consumed; an agent is a process that consumes tokens to produce work. The new job of finance is to manage the ratio between the two — work produced per token burned. That ratio is the gross-margin equation of the agentic era.

What a CFO Should Start Doing ASAP

Read more

In How I Ended Up in the Harness the question was how that migration happened in the first place — the four-year arc from ChatGPT through o1 through MCP through the swarm era, in which scaling laws didn’t stop, they moved out of the model and into the harness around it. This book asks what comes next — when the migration reaches the team.

The Harness pieces traced changes in the substrate at the scale of a single practitioner. The chat window dissolved into a harness. The keyboard stopped being the primary surface. The work shifted from operating a tool to framing a system that operated tools for me.

Seven structural principles fell out of that shift — agent swarms, self-improving loops, shared intelligence, gates over guardrails, memory as architecture, orchestration as substrate, the one-person-plus-harness-equals-team thesis. SaaS mutated into AGaaS in lockstep because the unit of value travels with the frontier. The thing being priced shifted from a tool a person operates to an outcome a system delivers.

The pieces left one question unanswered. If the harness is the new operating layer for one person — and if the outcome it produces is what gets sold now — what does it look like at the scale of a team?

This book is the answer.

Join Yearly Premium Membership To Get The Builder-PM

Access For Yearly Premium Member!

Or

Get It Separately

The Builder-PM is what product management looks like once the migration has completed and reached the team. Conventional PM was built for an operating substrate that no longer exists — a chat-era world where specs got handed off, roadmaps got reviewed across quarters, and stakeholders got coordinated across functions that were expensive to bridge.

That substrate was the old scaling regime: capability inside the model, value inside the seat, work inside the spec. All three have moved.

The new substrate is the harness, applied at the unit of a team rather than the unit of one person. The five-to-ten-person founder cell is one person with a harness, scaled up by an order of magnitude and given a bet portfolio.

Same role compression. Same direct line to the source of authority. Same negative space — the deliberately absent functions that protect the unit’s geometry. Same collapse of the spec-to-prototype handoff into a single artifact. Same posture toward the curve: the bet lives in the gap between what just became possible and what has shipped.

What the Harness series argued at the scale of one person — that the edge has moved from operating to framing, and that authorship is the Accountability Floor that cannot be automated because it is not a capability — this book argues at the scale of an organization.

The Builder-PM does not operate the harness. The Builder-PM frames what the harness gets pointed at. The job is bet selection, prototype calibration, loop ownership — the authorship work that survives because nothing in the harness can do it for the team.

The Builder-PM Manifesto — fifty-two compressed statements organized in nine sections — sits alongside the book as the form that travels. The book persuades the reader who will invest ninety minutes. The manifesto reaches everyone the book’s readers want to send something to. Both belong to the same argument.

If you read the Harness pieces and found yourself asking what does this mean for the way I run a team, you are reading the right book next.

If you didn’t read them, you don’t need to. The argument stands on its own. But it stands more clearly if you saw the migration first.

The harness was the precondition. The cell is the application. The Builder-PM is the role inside it.

This manifesto is the compressed form of an argument I have been working on across the first half of 2026, in three editorial pieces and one consolidating book — The Builder-PM: How Product Management Is Being Rebuilt for the AI Era.

The work started by accident. In late 2024, while running many enterprise AI conversations, I kept hearing the same question phrased five different ways. Some version of: we are hiring product managers, we have always hired product managers, and the people we hire now seem to be working on a different job than the ones we hired three years ago — what is happening to the role?

The question came from CEOs, CPOs, VPs of Product, founders, and individual PMs trying to figure out their next move. The question was structural, but every answer offered for it at the time was tactical: better frameworks, new certifications, AI-PM bootcamps, prompt-engineering courses. None of the tactical answers addressed what was actually changing.

What was actually changing — once I started looking at the pattern — was the substrate. The operating environment underneath the role had shifted. Frontier model capability had begun doubling roughly every three months, while the integration of that capability into shipped products climbed in months rather than weeks.

The accumulating gap was the product overhang, and it rewarded a fundamentally different strategic posture than the one most product organizations were trained for.

Inside the companies pulling ahead — Anthropic, Cursor, Cognition, Replit, and a small number of others — a different unit shape had emerged: five-to-ten people, direct CEO reporting, broad decision rights, hybrid roles, communication overhead at roughly one-tenth of a comparably-staffed conventional product unit.

And inside that unit shape, a different role had emerged: framing strategic bets on capability ahead of public release, prototyping specifications directly with agentic tools, owning continuous validation loops in place of project cadence. Cat Wu named this role the Builder-PM in her March 2026 essay for Anthropic, and the name has stuck because it captures what the role actually does.

The three editorial pieces — the Anthropic Labs founder-cell analysis, the Product Overhang Doctrine, and the Anatomy of a Founder Cell — were my attempts to anatomize each layer of this shift in operating detail.

The book consolidated and extended them, adding two new chapters: one anatomizing the Builder-PM role itself, and one on the transition for individual PMs, PM leaders at incumbents, and founders hiring into AI-native cells.

The manifesto is what remained after I wrote the book and tried to compress the argument into a form that travels.

A manifesto, to do useful work, has to be different in genre from the book it sits next to. The book is a structural argument — patient, layered, cumulative. The manifesto is a declaration — short statements, each one quotable on its own, each one anchored by a brief mechanism.

The book persuades the reader who will invest ninety minutes. The manifesto reaches everyone the book’s readers want to send something to.

I wrote it for three readers in particular.

The first is the individual PM — typically with five to fifteen years in the conventional discipline — who can sense the substrate shifting underneath them but cannot yet name what is happening. The statements that follow are the names. If you find yourself nodding at the early ones and arguing with the later ones, the book is the longer working-out of each disagreement. If you find yourself nodding at all of them, you are probably further into the transition than you realize.

The second is the PM leader at an incumbent — VP of Product, CPO, Head of Product — who is responsible for an organization that is increasingly the wrong shape for the work that is now possible to do. The statements about the operating environment, the Envelope Problem, and the political precondition for the carved-cell pilot are written specifically for the conversation you are about to have with your CEO. They are designed to be quoted from.

The third is the founder or CEO — particularly at AI-native startups, but also at incumbents pursuing AI-native bets — who is making decisions about hiring, organizational design, and strategic frame at a moment when conventional product organization advice will produce predictable underperformance. The statements about hiring, screening signals, and patience in cell construction are written for you.

Each numbered statement is a claim. Each paragraph beneath it is the mechanism — short, but enough to anchor the claim in evidence and reasoning rather than slogan. Read straight through, the fifty-two statements walk the entire structural argument of the book in compressed form. Read selectively, any single statement stands on its own as a small argument with its own internal logic.

A note on what this manifesto is not. It is not a methodology. It is not a certification curriculum. It is not a framework to be adopted in twelve weeks. It is a statement of position on a discipline that is being rewritten in real time, and the rewriting is happening whether or not the manifesto exists. My contribution is to name the rewriting in terms that are precise enough to be acted on.

The fifty-two statements that follow are organized in nine sections — the role, the strategic frame, the operating environment, the activities, what stays human, the transition, the incumbents, the founders, and what does not change. The order matters. The argument is cumulative even in compressed form. The final two statements — we are the people doing the rewriting — name the position from which the manifesto is written, and the position the manifesto invites its readers into.

What follows is the position.

SECTION I

On the role

1. The title is the same. The job is not.

Access For Yearly Premium Member!

Or

Get It Separately

On the fracture inside a single job description.

The same company posts a Senior Product Manager role in late 2024 and another in mid-2025 with almost no overlap in the actual responsibilities. The first lists roadmap ownership, spec writing, stakeholder coordination, quarterly business reviews. The second lists framing strategic bets on capability six-to-twelve months ahead of public release, prototyping specs directly with agentic tools, operating inside a small autonomous unit. The title is the same because HR systems and career ladders haven’t caught up. The job is not the same, and pretending otherwise misreads what is happening to the discipline.

2. We run specs, we don’t write them.

Access For Yearly Premium Member!

Or

Get It Separately

On the collapse of the spec-to-prototype handoff into a single artifact.

With agentic tooling, the spec and the prototype collapse into the same object. A description handed to Claude Code becomes a working branch in the same session. The conventional PM cycle — write the spec, hand it off, wait for the build, review the implementation — has been compressed into a single working session that the Builder-PM owns end-to-end. The Jira ticket has been replaced by the commit, and that is not a cosmetic change.

3. No roadmap. A bet portfolio.

Access For Yearly Premium Member!

Or

Get It Separately

On what replaces the conventional forward queue when there is no stakeholder layer to make visible to.

A roadmap is a forward queue maintained for stakeholder visibility — it exists because people outside the team need to see what’s coming. Pre-PMF work inside a founder cell has no stakeholders to make visible to. The roadmap document, with its quarters and themes and milestones, is replaced by two to four active bet briefs that the cell is currently working. The bets are not a future queue. They are the live state of the unit’s work.

4. No stakeholder reviews. Pre-PMF work isn’t stakeholder business.

Access For Yearly Premium Member!

Or

Get It Separately

On why the review function dissolves when the unit shape no longer requires it.

Stakeholder review exists to absorb the consequences of building the wrong thing at scale — a 50-person product org cannot afford to ship a quarter’s work and discover after the fact that it was misaligned. Inside a five-to-ten-person cell shipping for capability that has not yet arrived, the review costs more than it protects against. The cell’s accountability is to the CEO sponsor and to the bet portfolio itself, not to a stakeholder layer it was specifically designed to escape.

5. We don’t translate. The functions have compressed.

Access For Yearly Premium Member!

Or

Get It Separately

On what happens when the cost of crossing between engineering, design, and PM collapses.

The conventional PM role’s largest value-add was integration across disciplines: translating between engineering capabilities, design considerations, business priorities, and research findings. That translation work was expensive because the boundaries between disciplines were expensive to cross. Agentic tools collapse most of those costs. The integration is now done inside the work itself, by people who can move fluidly across disciplines because the tools make that movement cheap. The translator function has nothing to translate.

6. The role is its own discipline.

Access For Yearly Premium Member!

Or

Get It Separately

On disambiguating Builder-PM from technical PM, founder-PM, and AI engineer with product duties.

The technical PM was a conventional PM with engineering literacy, operating inside conventional org structure on technical products. The founder-PM is a CEO operating in PM mode, drawing on their strategic authority to push product direction through. The AI engineer with product duties is execution-weighted and taste-light. The Builder-PM is none of these. It is a PM whose PM-ness is the primary qualification and whose technical fluency is built into the role as a non-negotiable supporting capability, supported by tooling that did not exist for the prior eras.

7. The substrate changed. Not the bar.

On why a more senior conventional PM is not a Builder-PM.

A more senior conventional PM does not become a Builder-PM by adding years. The role exists because the operating substrate — the org shape, the strategic frame, the tooling — has all shifted at once. Layering seniority onto the old substrate produces a senior conventional PM, not a Builder-PM. The transition is across, not up.

SECTION II

On the strategic frame

8. The gap is where we work.

On the product overhang as the only place an organization can structurally pull ahead.

Frontier model capability roughly doubled every three months across 2024–2026 by the METR long-horizon agentic benchmark — from ~21 minutes of human-equivalent task duration on Sonnet 3.5 to ~12 hours on Opus 4.6. Integration into deployed products takes months per release cycle. The accumulating gap between these two curves is the product overhang, and it is the only place an organization can structurally pull ahead. Everyone is competing in the integration band; almost no one is shipping for the overhang.

9. Bet on demonstrated capability, not wished or shipped.

On why the bet has to live in the gap between research demonstration and production deployment.

The bet has to live in the gap. Capability that doesn’t exist yet, even in research demonstrations, is speculative fiction — building for it is a bet on the lab’s roadmap, not on the curve. Capability that has already shipped into products is closed competitive ground — the overhang for that bet has been closed. Only the gap rewards an asymmetric bet, and the gap is narrow enough that the bet has to be specific about which capability, on which axis, at what horizon.

10. Build for the next model, not the current one.

On why optimizing tightly for today’s model produces obsolete work.

Anything built tightly against today’s model — its context limits, its tool-use quirks, its specific reasoning failures — is technical debt that gets settled on the next release. Building for the trajectory rather than the snapshot is the only durable posture. The product that ships into next quarter’s capability landscape, designed against today’s snapshot, has already aged out of relevance before it reaches users.

11. No named axis, no bet.

On axis selection as the Builder-PM’s first activity.

Capability does not climb monolithically. It climbs differently across reasoning depth, tool use, context length, multimodality, and agentic horizon. “AI is getting better” is not a bet — it is a weather report. “Long context will reach production reliability by Q3” is a bet, because it specifies which axis, what reliability threshold, and what horizon. The Builder-PM’s first activity is axis selection, and a brief that does not name its axis is a brief that has not done its first activity.

12. Scaffolding is decaying inventory.

On why the default posture on every model release is deletion, not preservation.

Every prompt-engineering trick that papers over a current model’s limitations, every retrieval system built to compensate for a context limit, every fine-tuned eval against a specific model’s quirks — all of it loses value the moment the underlying model improves. The default posture is deletion, not preservation. Hardening scaffolding into permanent infrastructure is the moment the unit stops treating the overhang as moving and starts treating its current integration position as a defensible product. The curve then moves past it.

13. Capability before cost.

On why the inference math closes itself and shelving correctly-framed bets is the most expensive form of risk aversion.

Shelving a correctly-framed bet because the inference math doesn’t pencil against today’s pricing is the most expensive form of risk aversion. Inference cost has fallen by roughly an order of magnitude per year across the frontier, and there is no structural reason to expect that to stop. The bet is on whether the capability will exist at production reliability; the cost curve closes the cost gap on its own. Optimizing for current pricing means missing the window every time.

14. Last quarter’s capability is the wrong question.

On the inverted strategic question that separates doctrinal from conventional product organizations.

The conventional question optimizes for what shipped — it asks how to integrate the most recent capability release into the existing product. The doctrinal question optimizes for what arrives — it asks what will be possible when the next release lands, and ships toward that horizon. Asking the second question is the strategic posture. Asking the first is the conventional one, and it produces conventional results.

15. The discomfort is the point.

On why the doctrine is a selector, not a prescription.

It requires placing bets without current product traction, absorbing months of pre-PMF work, deleting scaffolding the unit has already built, and hiring for axis-selection taste rather than for execution capacity. Most organizations cannot do these things. The doctrine selects for the small subset that can, and the small subset is increasingly the set of organizations pulling structurally ahead. The doctrine is not popular because it is hard. The hardness is what makes it valuable.

SECTION III

On the operating environment

Read more

This is not metaphor. It is an institutional event of the same class as the New Deal’s administrative state or the Cold War’s national security state — and like those, it will not unwind on its own once produced.

This piece argues the reshape has a central feature most commentary is missing: the emergence of a fourth leg of US institutional power, occupied by frontier AI leadership, in dyarchic relationship with the executive. Everything else — the legislative recession, the judicial dependence, the open-source weakening, the reentry of sub-sovereign actors — is consequence, not cause.

Read more

Because the same forcing function that pulled me out of operating is now reorganizing everyone else, and the receipts are landing.

What follows is what I see. Not predictions — patterns. Five frictions, each one a force fighting another, each one already visible in the numbers. And one frame to hold above them all, because it changes how the rest reads:

You do not get to opt out of the harness society. It is cascading down to you whether you participate or not.

Start there.

Access my harness with the exec plan!

Cold open: the iPhone you didn’t choose

Access my harness with the exec plan!

The iPhone 18 Pro is projected to cost about $200 more than its predecessor. The reason is mechanical: memory chip prices have risen roughly 3.7× in a year because AI buildouts have absorbed essentially all available HBM capacity. Apple is not an “AI company” in the frontier-lab sense. It still pays the AI tax — and passes it through to you.

That’s the entire piece in one consumer transaction. You didn’t sign up for the harness society. You’re paying for it anyway, because the inputs your phone needs are being absorbed by an economy you didn’t agree to join. And the iPhone is the easy case — the one where the cost is visible on a sticker.

The harder cases — power grids, talent markets, the political bandwidth absorbed by the AI story itself — work the same way. The harness society is not a destination one walks toward. It is a substrate the rest of the economy is already inside, and the people who never thought about it are paying their portion silently.

Five frictions follow. Each is a force fighting another. Each is already measurable.

Friction 1 — The Principal / Operator split is here, with receipts

Access my harness with the exec plan!

For two years the line “AI will divide workers into a small group who direct it and a large group who compete with it” has been theory. As of last week, it is measurement.

Anthropic published a study of 400,000 real Claude sessions, and the structure is unambiguous:

• Humans make ~70% of the planning decisions. AI handles ~80% of the execution.

• The same model produces 5× more output for an expert than a novice.

• Domain expertise dominates over coding background — occupations cluster within seven points of one another regardless of technical fluency.

• Debugging fell from 33% to 19% of session activity. Building rose 43%. Work is moving up the value stack in real time, inside the same tool.

That is not a trend; it is the Accountability Floor showing up as a usage pattern. The people who get 5× output are not pressing keys faster. They are better at the part the model cannot do — deciding what is worth doing and what “good” looks like before the agent runs. The 70/80 split is the principal at work: humans authoring, models executing.

Then Gallup, separately: tech workers who have not adopted AI face roughly 3× the layoff risk of those who have.

The split is now visible from both sides. On the producer side, a 5× output gap between expert and novice using the same tool. On the labor side, a 3× employment-risk gap between adopters and holdouts. That is not a gradient. It is a fork.

The structural read: non-adoption stopped being a preference and became a career risk multiplier. That is true even for capable, experienced workers — especially for them, because the ones being out-produced are usually the ones who used to be good at the layer the machine just took.

Friction 2 — The companies forking, with two extremes already visible

Access my harness with the exec plan!

The same data set shows that AI does not push every company in the same direction. It pushes them in opposite directions depending on what they decide they are for.

Gartner’s IT 2030 model lays this out cleanly. A 100-FTE IT team, run through AI, becomes one of two things:

• 30 FTE producing the same output (the shrinker: same work, fewer people, lower cost), or

• 150 FTE, all builders, producing far more (the amplifier: same people, more output, redefined work).

Same technology. Two opposite org charts. The fork is not AI; the fork is what the company chose to do with the leverage.

Both ends are running, with names:

The amplifier case: Block (Square’s parent). Their internal “BuilderBot” agent produces ~15% of all production code shipped at the company. Roughly 1,500 pull requests merged per week. Around 200,000 agent operations per day. Tasks that took months take days. The system is triggered from a Slack message — a frame, set by a human, executes through a swarm. This is the harness, in production, at scale, with the headcount intact.

The shrinker case: State Farm. 19,000 agent contracts rewritten. Benefits cut. Retirement eliminated. Commissions tied to AI-tracked metrics. Income reductions of up to 40%. Meanwhile Progressive — running an AI-driven underwriting model — has overtaken State Farm as the #1 U.S. auto insurer. The shrinker pattern is not speculative; it is a finished restructuring with measurable consequences for the people it touched.

The pattern across both:

AI does not decide the org chart. It amplifies whatever the company was already trying to be.

Shrinkers shrink. Builders build. The technology is the multiplier; the choice is the company’s.

This is the structural reason most transitions will be painful. The political weight inside almost every organization is concentrated in middle management — and middle management is the layer most exposed to either path. The amplifier path turns middle managers into orchestrators of agent swarms (a new and difficult job). The shrinker path eliminates the role they currently occupy. Expect the fight inside organizations over which path to take to be more bitter than the one happening in public, because the people deciding the path are the people most affected by it.

Friction 3 — The hardest problem isn’t pricing the task. It’s defining the outcome.

Access my harness with the exec plan!

Per-seat software pricing held for nearly twenty years. That ended last week.

Microsoft launched Copilot Cowork at $0.01 per task — explicitly described as the first pricing-model change in nearly two decades. Nadella was direct: the unit being priced is no longer a user-month; it is a piece of work an agent completes. That is the SaaS → AGaaS transition I have been describing in the prior pieces, with a date stamp on it.

But the story most read out of this announcement misses what is actually hard about the transition. The token-cost stress is real — Meta, Microsoft, and Amazon all cut internal AI token budgets in the last fortnight; Uber burned its annual AI budget in four months; agentic AI consumes roughly 1,000× more tokens than chat for equivalent work; Microsoft canceled internal Claude Code licenses while expanding Copilot. Nadella himself called tokenmaxxing “addictive”. Those numbers will compress over the next 12–24 months as token deflation does its work.

The deeper problem won’t compress on its own. It is this: most companies cannot define what the outcome of a task actually is at the granularity an AGaaS contract requires.

Per-seat SaaS worked because the unit being purchased was access — a fuzzy, hard-to-measure good that everyone could agree on the price of without agreeing on the value. Per-task AGaaS does not have that luxury. The vendor charges per outcome delivered. The customer pays per outcome received. And both sides have to know what an outcome is. Most companies do not.

Consider the gap:

• What is the outcome of a customer-success interaction? Resolved tickets, retained accounts, expanded contracts, satisfaction scores, all of them weighted somehow? Most orgs don’t have a definition.

• What is the outcome of a software engineer’s day? Merged PRs, shipped features, reduced incidents, mentored juniors, refactored debt? Most orgs don’t have a definition.

• What is the outcome of a marketing campaign? Impressions, MQLs, pipeline, attributable revenue, brand lift? Most orgs argue about it for years.

When the unit being priced is a seat, the outcome can stay ambiguous. When the unit being priced is a task, the ambiguity is the bottleneck. Companies cannot buy AGaaS at scale until they can articulate what their outcomes are, and articulating outcomes is an organizational restructure, not a procurement decision.

The revenue impact, where companies do solve this, is enormous. The Block case is what it looks like when a company restructures around outcomes: a Slack message becomes a frame, the frame becomes 1,500 PRs a week, the unit of value is the merged change, and it is measurable. The companies that build that scaffolding internally will see 5–10× output gains, possibly more. The companies that try to buy AGaaS without doing the restructure will spend money, fail to measure return, and conclude that AI “doesn’t work for us.” Both outcomes are happening simultaneously in the same market.

There is a clean structural symmetry worth naming here. The frontier labs are running the same problem in reverse. They are subsidizing power users at deeply negative margin to acquire workload signal at the frontier of difficulty — because they, too, cannot yet define what the outcome of an agentic task should be without watching real users grind real problems against it. The labs are buying outcome-definition data from power users at the same moment customer companies are trying to sell their own work as outcomes to vendors. Same denominator problem, opposite sides of the trade.

The outcome denominator is the load-bearing organizational problem of the next three years. Whoever solves it inside a company captures the AGaaS productivity multiplier. Whoever does not, doesn’t.

Friction 4 — The middle dissolves quietly

Access my harness with the exec plan!

Here is the friction the political discourse keeps getting wrong.

Gartner, last week: of all 2025 layoffs studied, only 1% were AI-productivity-driven. Repositioning layoffs — companies pivoting to AI strategy — dropped from 17% to 7%. A full 87% of layoffs were macroeconomic, not AI at all.

Read in isolation, that is reassuring. Read against the Gallup 3× number, it inverts. AI is not doing the firing. It is deciding who survives the macro shock when one arrives. The displacement is not loud, broad, and AI-branded. It is quiet, selective, and macroeconomic-shaped — and consistently weighted against the people who did not restructure their work.

The harder question is: who is being filtered out, exactly? The data and the cases point at a non-obvious answer. It is not the juniors. It is not the seniors. It is the middle.

Look at where the displacement is actually landing:

• State Farm’s 19,000 agent contracts — these are not entry-level workers. They are mid-career independent insurance agents, the operating layer between underwriting (top) and customer-facing service (bottom). The middle.

• Microsoft’s Claude Code cancellations — these were mid-level developer tooling subscriptions. The cheap stuff at the bottom stayed; the high-end enterprise stayed; the middle got cut.

• Anthropic’s session study — debugging (mid-level technical work) fell from 33% to 19% of activity; building (senior-level authoring) rose 43%. The activity mix shifted away from the middle.

• Gartner’s IT 2030 archetypes — the role that disappears in both the shrinker and the amplifier paths is identical: “traditional IT worker doing manual tasks.” Mid-career operators of established systems. The middle.

The pattern is consistent across every data point: AI is not a junior-replacer or a senior-replacer. It is a mid-level dissolver. Juniors survive at the bottom because supervised execution is still cheaper than agentic supervision in most settings, and because juniors are the cheapest training pipeline a company has. Seniors survive at the top because their value is judgment, authorship, relationships, and accountability — exactly the bedrock the bedrock-piece pointed at. The middle is where competence-at-operating used to live, and operating is what just got automated.

This is more politically explosive than a broad displacement would be, for two reasons:

• It is deniable. Every individual firing has a non-AI cause: budget cuts, restructuring, “performance.” No company is forced to say “we let her go because she did not restructure her work.” But statistically, that is largely what happened.

• It compounds. Each downturn becomes an additional filter. The principal class gets reinforced at the top; the junior class survives at the bottom as the training pipeline; the middle gets winnowed. By the third macro shock, the workforce has been silently restructured into a barbell without anyone announcing the restructuring.

The harness society is not producing dramatic firings. It is hollowing out the middle of the labor market, one macro shock at a time, deniably.

And the political weight of the people being hollowed out is, in most countries, the political weight of the median voter.

Friction 5 — The substrate tax

Access my harness with the exec plan!

Back to the opener — but now widened beyond consumer electronics.

The iPhone case is the most legible instance of a pattern about to repeat across many goods and markets: AI buildouts are pulling key inputs out of every other industry that needs them, and the prices in those industries are reorganizing around that absorption.

Memory is the visible case. The next instances are already running:

• Power grids. Data center buildouts are absorbing grid capacity that was assumed available to homes, factories, and existing commercial customers. New industrial projects are quietly losing interconnection slots to AI campuses willing to pay more and wait less. Power is being priced as if AI demand is the only demand that matters.

• Talent. A few thousand people doing frontier ML are compressing technical wages across the entire economy. Companies that have nothing to do with AI compete with hyperscaler comp because their engineers can leave for it. The wage curve has rotated.

• Capex absorption. Frontier-lab capex commitments are at a scale that crowds out other infrastructure investment. The pension funds and sovereigns financing the AI buildout are not financing other things at the same scale.

• Political and regulatory bandwidth. Legislators, regulators, journalists, and academics now spend a disproportionate share of attention on AI — at the expense of every other policy question. The harness society is buying attention as an input the same way it buys memory.

This is the move from AI as one industry to AI as a substrate the whole economy now pays into. Substrates do not ask permission. They reshape the prices and the attention around them.

You do not have to participate in the harness society to live in it. The substrate taxes everyone — and the people who never opted in pay in goods, energy, wages, and attention.

This is the friction that closes the piece, because it is the one that converts the personal-scale “transition” of the prior pieces into a societal-scale reality. The principal class is being formed. The middle is being hollowed. The companies are forking. The pricing model is being rewritten. And the substrate is taxing everyone in the room — including the people who never read a piece like this one.

The structural read: three second-order patterns

Access my harness with the exec plan!

Step back from the five frictions and three deeper patterns emerge — the second-order consequences the trilogy’s first two pieces deferred to here. Each is worth its own paragraph because each is a real, structural change to how the economy is organized.

The org chart inverts. The shape companies have used for the last hundred years — a wide base of operators, a layer of supervisors, a small top of decision-makers — is mechanically incompatible with the harness. The wide base is what gets automated. The supervisory middle is what gets dissolved. What is left is a small top of principals authoring outcomes and a thin pipeline of juniors apprenticing toward the top, with a swarm of agents in between doing the actual work that used to require the operating layer. Block is the shape running well. State Farm is the shape running badly. Most companies will spend the next five years trying to figure out which one they are, and the political fight over that decision will be the dominant internal story of the late 2020s. The companies that resolve it cleanly will become unrecognizable to their employees of three years prior. The companies that do not will fail in slow motion against competitors who did.

The apprenticeship pipeline breaks, and nobody is fixing it. Framing judgment was historically forged by operating. You became a principal by spending years as an operator, learning what the work actually is, accumulating the pattern recognition that lets you eventually direct it from above. If operating is being automated, the training ground for the next generation of principals quietly disappears. This is the genuine fragility in the harness thesis, and the data does not address it. Block’s BuilderBot is producing 15% of code, but where do the engineers who can direct a BuilderBot in 2030 come from, if there is nothing for them to operate in 2026? The answer right now is “from the existing pool of seniors, until that pool retires.” That is a transitional state with a hard expiration date. This is the most important unanswered question in the entire transition, and the people closest to the harness (myself included) have not yet articulated what replaces the operating-as-training-ground pipeline. Until someone does, the principal class is finite, ageing, and not being replenished.

Governance becomes the scarce resource. Personal harnesses are governed by personal authorship — the bedrock the first two pieces ended on. Societal harnesses need a societal version of the same thing, and it is genuinely missing. Who is allowed to be the principal of a swarm that can author at scale? Who is accountable when a swarm authors something that goes wrong — the operator, the lab, the regulator, the customer? Whose will and whose liability govern an agent that ran for fifty steps without supervision? These are political questions, not technical ones, and they are the ones that determine what the harness society actually feels like to live in. The labs and the hyperscalers will not answer them; they will optimize around whatever answer the rest of the system produces, the same way every other industry has done. The answer needs to come from somewhere else, and right now it is not coming from anywhere. That is the political vacuum the next decade fills. Whoever fills it — legislators, courts, professional associations, customer cartels, a new institution that does not yet exist — defines the terms of the harness society more than any line of code will.

The structural read

Access my harness with the exec plan!

The harness society is not coming. It is here, and it is being born under pressure.

The personal version of the transition — the one I wrote about in the first two pieces — is real and available to people who can see the forces and move. It is the optimistic story, and the data supports it. Block-style amplifier orgs, Anthropic’s 70/30 planning split, Nadella’s human-capital framing, the AGaaS pricing transition where outcomes are well-defined — these are all the harness society going well.

But the same data set contains the structural story. State Farm’s 19,000 contracts. Gartner’s 1% / 87%. Gallup’s 3× — concentrated on the middle. Apple’s supply tax, generalized. The middle dissolves. The pipeline breaks. The substrate taxes the opt-outs. The new pricing model arrives bottlenecked on a problem most companies cannot solve. The political conversation has not begun.

These are not competing narratives. They are the same forcing function — capability migrating outward from the model to the harness around it — playing out at two scales simultaneously. At the scale of one person who can read the forces, it produces leverage. At the scale of a society that mostly cannot, it produces friction. Both are happening at once, and the gap between them is what makes this period feel uncomfortable to live inside.

The trilogy’s first two pieces ended on the bedrock — authorship, the position the churn cannot reach. That answer holds at the personal scale, and it holds here too, restated upward:

At the personal scale, the bedrock is being the principal of your own harness.

At the societal scale, the bedrock is deciding who gets to be a principal at all — and answering for the rest.

The first is a choice anyone reading this can make. The second is the political question of the next decade, and it has not been asked yet.

The harness society is here. The question is who runs it, and on what terms.

Key Takeaways & Mental Models

Access my harness with the exec plan!

The Substrate Tax — AI is no longer one industry among many; it is a substrate the rest of the economy pays into whether or not it participates. Memory chips are the visible instance. Power grids, talent markets, capex, and political bandwidth are the next.

The Principal / Operator Split, Measured — Anthropic’s 70/80 planning-vs-execution split, the 5× expert-vs-novice output gap, and Gallup’s 3× layoff risk for non-adopters are the same fault line measured from three angles. The split is here, with receipts.

The Org-Chart Fork — Same AI, opposite results: 100 FTE → 30 FTE or 150 FTE. Shrinkers shrink. Amplifiers build. The technology multiplies whatever the company was already trying to be.

The Outcome Denominator — The hard part of the AGaaS transition is not pricing the task; it is defining the outcome. Most companies cannot articulate their outcomes at the granularity an agent contract requires. Solving this is an organizational restructure, not a procurement decision — and it is the load-bearing problem of the next three years.

The Middle Dissolves Quietly — AI is not firing juniors and not firing seniors. It is hollowing out the mid-level operating layer through the deniable mechanism of macro shocks, one cycle at a time. The political weight of that layer is the political weight of the median voter.

The Apprenticeship Gap — Framing judgment was forged by operating. If operating is automated, the training pipeline for the next generation of principals quietly disappears. Nobody is fixing this, and it is the most important unanswered question in the transition.

Governance as the Scarce Good — Personal harnesses run on personal authorship. Societal harnesses need a societal version of authorship: who is allowed to be the principal of a swarm, and who answers when one goes wrong. That is the political question of the decade, and it has not been asked.

Recap: In This Issue!

The Harness Society Is Not Optional

The central thesis is simple:

You do not get to opt out of the harness society.

Even people who never use AI directly are already paying for it through higher prices, constrained infrastructure, distorted labor markets, and redirected capital flows. AI is becoming a substrate, not an industry.

The Principal–Operator Split Has Become Measurable

For years, the idea that AI would separate people into those who direct intelligence and those who compete with it was largely theoretical.

Now the data is showing it:

• Humans make ~70% of planning decisions.

• AI performs ~80% of execution.

• Experts generate 5× more output than novices using the same tools.

• Non-adopters face roughly 3× higher layoff risk.

The emerging divide is not technical skill.

It is the ability to frame, direct, and evaluate work.

Companies Are Forking Into Two Models

AI is not producing one organizational outcome.

It is creating two.

The Amplifier

• Similar headcount

• Dramatically higher output

• Humans orchestrate agent swarms

• Example: Block

The Shrinker

• Lower headcount

• Cost-focused restructuring

• AI used primarily for efficiency

• Example: State Farm

The technology is neutral.

The strategic choice belongs to leadership.

The Outcome Economy Is Replacing the Seat Economy

The shift from SaaS to AGaaS changes the unit of value.

The old question:

How many users need access?

The new question:

What outcome is being delivered?

Most organizations cannot answer that question with precision.

This becomes the biggest bottleneck in AI adoption.

The companies that can clearly define outcomes unlock massive leverage.

The companies that cannot remain trapped in experimentation.

AI Is Quietly Hollowing Out the Middle

The most politically important insight:

AI is not primarily replacing juniors.

AI is not primarily replacing seniors.

AI is dissolving the middle.

The operating layer that historically sat between execution and leadership is becoming increasingly automated.

The result is a barbell structure:

• Principals at the top

• Apprentices at the bottom

• A shrinking middle

This happens gradually, often hidden inside macroeconomic restructuring rather than explicit AI layoffs.

The Apprenticeship Crisis Has No Answer Yet

One of the deepest unresolved questions:

How do future principals emerge if operating work disappears?

Historically:

Operator → Experience → Judgment → Principal

If AI automates the operating layer, the traditional training ground for judgment disappears.

The industry has not yet solved this problem.

This may become the defining talent challenge of the next decade.

The AI Tax Is Becoming a Substrate Tax

AI is beginning to absorb scarce resources across the economy:

• Memory chips

• Electricity

• Technical talent

• Infrastructure capital

• Political attention

This is what happens when a technology stops being a sector and becomes infrastructure.

Everyone pays the tax, including those who never participate directly.

Governance Becomes the Scarce Resource

The biggest unanswered question is no longer technical.

It is political.

Who gets to direct increasingly autonomous systems?

Who is accountable when they fail?

Who determines the rules under which agentic systems operate?

The next decade is likely to be defined less by breakthroughs in AI capability and more by the struggle to define legitimate authority over those capabilities.

The Core Insight

The first two Harness essays were about the transformation of the individual.

This piece expands the lens to society.

The underlying force remains the same:

Capability is migrating from the model into the harness around it.

At the individual level, that migration creates leverage.

At the organizational level, it creates restructuring.

At the societal level, it creates friction.

The harness society is not a future scenario. It is the operating environment that is already emerging around us.

With massive ♥️ Gennaro Cuofano, The Business Engineer

The question worth asking in June 2026 is not whether open source AI is sustainable. That question is too coarse to answer. The sharper one is: is open source dying at the top frontier of AI — and if it is, under what conditions does that hold, and what would break the bet?

DeepSeek V4 shipped in April 2026 under MIT — 1.6 trillion total parameters, one-million-token context, at one-thirtieth the cost of Claude Opus 4.7 and GPT-5.5. It is the closest open weights have ever come to the frontier. It is also, on the hardest benchmarks, three to six months behind. The gap has been stable for two years. By some measures it is widening.

Two readings of that fact are possible. The first: open source is converging on the frontier, just slowly. The second: open source has reached an asymptote, and the gap from here is structural, not temporal. Both readings are defensible from the data alone. Which one is right depends on conditions the data cannot answer — conditions about capital, governance, the architecture of the safety stack, the mechanics of how open source has been catching up, and the strategic posture of Chinese labs once they reach the frontier.

The argument of this piece is conditional, not declarative. If four gates hold — and if China’s open-weights moment turns out to be strategic rather than structural — open source is dying at the top frontier. If any one of these breaks, the bet breaks. Naming the gates, naming what would break them, and naming the Chinese question is the work.

Stay Ahed of The AI Supercycle →

Read more

What makes this moment unique is that it is often misunderstood as a story about automation. In reality, it is increasingly a story about augmentation.

The emerging model is not AI replacing humans. It is humans equipped with AI, and increasingly with fleets of AI agents, becoming capable of orchestrating work that …

Read more

In that regard, Jensen Huang’s ability to zoom out, connect the dots, and articulate the broader transformation underway is truly exceptional.

I highly recommend watching the talk below, along with the accompanying article it inspired.

The piece builds on Huang’s perspective while incorporating several frameworks and mental models I’ve been developing to better understand and navigate the AI Supercycle.

Every industrial age is defined by a machine that consumes one substrate and emits another. The substrate that gets emitted — not the machine that emits it — is what reshapes the economy. Three hundred years of industrial history compress into three of these conversions, and the third one is being installed in real time, in concrete and copper, on every continent simultaneously.

The machine is the dynamo. The substrate is intelligence. The cocoon is forming now.

Stay Ahed of The AI Supercycle →

The Substrate Doctrine — Atoms, Electrons, Tokens

Stay Ahed of The AI Supercycle →

A substrate becomes infrastructure when three conditions hold. It must be generable on demand (a machine can produce it). It must be transportable at near-zero marginal cost (a wire, a fiber, a rack). It must be universally consumable (everything plugs in). Three substrates have ever passed all three tests at planetary scale.

Electrons. A coil rotated through a magnetic field emits an invisible force. Within a century, that force cocoons every continent in a grid. Total addressable market: every joule of useful work humanity wants done.

Bits. Electrons routed through switches at near-luminal speed emit packets. Within three decades, those packets cocoon the planet in a network. Total addressable market: every act of human coordination.

Tokens. Electrons fed into massively parallel arithmetic emit numbers that encode meaning — text, code, images, video, protein structures, control signals, decisions. The substrate is intelligence. The economy is reorganizing for the third time. Total addressable market: every act of cognition humanity wants performed, plus the cognition of the machines themselves.

The implication of the lineage is not that AI is “like” electricity. The implication is that AI is on the same curve as electricity — same generational capital requirements, same regulatory eventualities, same commodity endpoint, same hundred-year reorganization of everything downstream. We are not in the chatbot phase. We are in the dynamo phase. The chatbot is one light bulb.

A second, deeper claim sits underneath the lineage: anything with structure is convertible to tokens. Proteins fold predictably. Cells behave predictably. Genes express predictably. Physics is predictable. Materials are predictable. The token is therefore not just a unit of language — it is the universal carrier of any learnable structure in the universe. The substrate is wider than language by orders of magnitude.

The Primitive Inversion — From Retrieval to Generation

Stay Ahed of The AI Supercycle →

For sixty years, computing was a retrieval architecture. You wrote, you stored, you fetched. Every screen ever looked at served something pre-recorded by someone, somewhere, earlier. The most valuable real estate of the prior internet was the index — the catalog of what had already been made.

That primitive has inverted. Output is now produced originally, in real time, contextually, for one consumer, once. Every pixel, every word, every frame, every recommendation — generated, not retrieved. This is not a refinement of the old computing. It is a different machine emitting a different substrate. Hence the rename: data centers do not produce intelligence; AI factories do.

The unit economics of an AI factory are unlike anything in software history. One rack carries seventy-two accelerators, weighs two tons, costs around four million dollars, and contains roughly one and a half million parts. One gigawatt of factory capacity costs around fifty billion dollars to build and emits three hundred to four hundred billion dollars of token output per year — a revenue-to-capex multiple of six to eight times at the asset level. The total capital flowing into the stack in 2026 is on the order of one trillion dollars, against an implied steady-state ecosystem of roughly twenty trillion dollars per year. This is not a software business — it is a fab. This is the unit economic that breaks every capex-normalization forecast in the market. Forecasters are pricing buildings; operators are pricing production lines.

The second-order consequence is retrieval decay. Every business priced on retrieval economics — search advertising, content aggregation, social feeds, recommendation networks — is in slow runoff. Retrieval businesses paid pennies per query because they re-served stored content with marginal cost approaching zero. Generation businesses meter compute per query because each output is originally produced. The cost curve is different. The pricing model is different. The defensibility is different.

The third-order consequence is the agentic demand shock. Today, intelligence is consumed by roughly one billion humans through chat interfaces. In the agentic phase — already underway — intelligence will be consumed by roughly 100 billion agents running continuously, talking to each other, executing tasks, calling tools, and coordinating workflows. That is a hundredfold demand step change layered on top of the existing consumer demand. The factories under construction are not overbuilt. They are underbuilt relative to a demand curve that has not yet materialized.

The Nine-Layer Cake — A Deeper Reading

Stay Ahed of The AI Supercycle →

The standard investor framing of the AI stack has five layers — energy, compute, infrastructure, models, applications. It is a useful public-facing compression, but it hides at least four separations that have become structurally consequential. A more accurate reading of the stack has nine layers.

The five-layer framing collapses what are now separate profit pools. Networking has separated from compute — rack-scale interconnects consume more than twenty percent of system cost and are growing roughly two hundred percent year-on-year, with one company holding monopoly economics on the interconnect.

Foundries have separated from silicon — allocation power at the leading-edge fab and the high-bandwidth memory oligopoly is now more consequential than chip design itself.

Governance has separated from generic policy and trust — it is now a priced variable in enterprise procurement and a binding constraint on cross-border deployment. Silicon itself has bifurcated into a generalist substrate, hyperscaler custom silicon, and merchant custom challengers. Each of these separations is its own market with its own incumbents, moat, and bottleneck.

Bottom-to-top, the nine layers are:

1 · Energy & Physical. Generation, transmission, water, cooling, land, permits. The first serious grid investment cycle in roughly a century. Power is the binding constraint for everything above it. Rare-earth supply, transformer steel, and grid-scale storage chemistry are the physical chokepoints that govern the pace of the entire stack. Capital intensity is extreme; margin is regulated; the moat is physical and political.

2 · Foundries & Packaging. The fab and the package — the physical conversion of designs into silicon. Allocation power at the leading-edge foundry and the HBM oligopoly is now a more consequential bottleneck than chip design. Advanced packaging (CoWoS and equivalents) is the binding constraint on supply for the next two generations of accelerators. Capital intensity is the highest in the entire economy. Margin is high at the frontier and structurally protected by twenty-plus-year capability gaps to the next-best competitor.

3 · Silicon. Chip design itself — generalist accelerators, hyperscaler custom silicon (custom TPUs, training accelerators, inference accelerators), and merchant custom challengers. The layer has bifurcated into three structurally different positions: the dominant generalist who sets the software stack, the captive customs who optimize for one workload, and the merchant customs who specialize on inference or specific architectures. Margin concentrates at the generalist; volume disperses to the customs.

4 · Networking & Protocols. Rack-scale interconnect, optical fabric, switching silicon, and the protocols stitching factories together. This layer carries monopoly economics on the leading edge — the interconnect is the most under-priced asset in the public market. Networking is now growing faster than compute itself because every additional accelerator demands a non-linear increase in interconnect bandwidth.

5 · Compute Capacity. The actual deployable rack-and-power-contract bundle — what hyperscalers and neoclouds sell. The difference between owning silicon and being able to deploy it at scale is now its own market. Capital intensity is extreme. Margin is high while scarcity holds and will normalize toward utility-like over a decade as the physical layer catches up.

6 · Foundation Models. The visible language models cover one slice. The industrial layer is everything else — protein, cell, genome, materials, physics, climate, robotics control, autonomous driving, code, design, audio. Anything with structure is learnable; anything learnable becomes a model; every model is a vertical market. The layer is shaped by three structural philosophies: maximalist capability frontiers (capability is the moat), trust and safety frontiers (refusal and reliability are the moat), and integrated platform frontiers (distribution into existing ecosystems is the moat). These are not interchangeable strategies — they produce structurally different products and command different multiples. The safety-positioned frontier in particular commands a refusal premium — enterprise buyers pay materially more for a model whose refusal behavior they can underwrite.

7 · Agentic Harness. The orchestration substrate that turns model output into operational output — tool calling, memory, planning, retries, evaluation, guardrails, sandboxing, multi-agent coordination. This is the layer that most application-layer companies confuse with their product. It is in fact a horizontal infrastructure layer in its own right, comparable to the cloud-native infrastructure layer of the prior decade. The companies that own the harness — and the persistent state that agents accumulate inside it — will become the next generation of infrastructure incumbents.

8 · Distribution. Applications, surfaces, and channels — the layer that touches the user. $100B of venture capital deployed in 2025 alone, the largest year in the history of the asset class. It is also the most fragmented layer and the one with the highest failure rate. Most application-layer companies built on a single model capability are absorbed by the next model release. The breakouts here own a workflow, not a feature, and reprice from per-seat to per-token or per-outcome.

9 · Governance. Policy, sanctions, export controls, deemed-export rules, AI safety regulation, model accountability, antitrust. This was treated for years as a soft layer — a horizontal constraint, not a market. It has now become a control plane perpendicular to the entire stack. A single jurisdictional directive can switch off a frontier model across every customer on the planet in seventy-two hours. Governance does not sit on top of the stack — it cuts through it. This is the most consequential reframe in the deeper reading: Layer 9 was never a layer. It is the dimension along which every other layer is conditional.

Two reading rules govern the stack. Each layer is constrained by the one below it — you cannot ship a model without compute, you cannot ship compute without silicon, you cannot ship silicon without foundries, you cannot ship foundries without energy. Each layer is commercialized by the one above it — silicon needs models to monetize, models need a harness, the harness needs distribution. Read top-down to see what gets priced. Read bottom-up to see what gets bottlenecked.

Where profit pools concentrate. Read the stack as a column to see one company’s full vertical posture — only a handful of operators in the world are deeply present across more than three layers, and those that are command the largest market capitalizations on Earth. Read the stack as a row to see who owns one layer in isolation. The diagonal between vertical integration and horizontal monopoly is where the supercycle’s profit pools live. Capex concentrates at L1–L5. Margin concentrates at L3 (silicon), L4 (networking), L6 (models), L7 (harness), and L8 (distribution). Demand concentrates at L8. Bottleneck concentrates at L1. Control concentrates at L9.

Any portfolio that touches only one layer carries dependency risk on all the others. The complete investment thesis specifies which layer is being financed, which adjacent layer the position depends on, and which jurisdictional governance regime the position assumes.

Task vs Purpose — The Cognitive Jevons Paradox

Stay Ahed of The AI Supercycle →

There is a single mechanism that controls how the labor market reorganizes in the intelligence age. It is the same mechanism that controlled the steam age, the electrification age, and the computerization age, and it has been misread every time. The mechanism is the distinction between task and purpose.

A task is the thing a person does in a given hour. A purpose is the reason the task exists. Automation collapses tasks. It does not collapse purposes. And when the underlying purpose is demand-unconstrained — when there is more of it wanted than is currently supplied — automating the task expands employment in the role, not contracts it.

Twelve years ago, a leading voice forecast the extinction of the radiology profession on the strength of superhuman computer vision. Computer vision did saturate radiology. Every reading is now augmented by it. And the number of radiologists is up, scan volume is up, departmental profitability is up. The mechanism: AI made each radiologist more productive, which lowered the cost per scan, which expanded the volume of patients who could be admitted, which increased departmental revenue, which justified hiring more radiologists. The same forecast made about software engineers in 2024 — “ninety percent of coding will be automated” — is being falsified in real time by record hiring at the foundation model labs.

This is a cognitive version of Jevons’ paradox: in 1865, William Stanley Jevons observed that more efficient steam engines did not reduce British coal consumption — they expanded it, because lower cost per unit of work expanded the universe of work being done. Cognitive labor sits in the same regime. Cheaper cognition expands the demand for cognition. The plumber becomes a bathroom designer. The carpenter becomes a home architect. The salesperson becomes an interior consultant. The accountant becomes a strategic advisor. The radiologist becomes a clinician with infinite scan capacity.

Three predictions follow directly. First, aggregate cognitive employment grows, not shrinks — the roles change shape, the headcount expands. Second, roles defined by task automate while roles defined by purpose elevate — a clear definition of purpose is now a labor market moat. Third, the geographic and educational concentration of cognitive work flattens — the prior dominant programming language was known by roughly two percent of humanity, the new programming language is human language known by roughly one hundred percent, and the population of programmers therefore becomes the population of humans. Returns to scale move from technical populations to user populations.

Practical Implications

Stay Ahed of The AI Supercycle →

Read more

Not as a passing trend or productivity hack, but as a signal of what’s coming next for many of us, whether we’ve realized it yet or not.

What I left out, however, was the most important question: did I choose this transformation? Was it a deliberate decision? A reality I consciously created?

I wish I could say yes.

The truth is that I didn’t arrive here entirely by choice. This shift is largely the result of forces much bigger than me. It is the natural consequence of how the most powerful industries in the world are evolving. And because I’ve spent my career operating at the edge of the AI industry, being “in the harness” wasn’t a tactical choice. It became a strategic constraint.

Am I disappointed by that?

Not at all.

In fact, this is the most exciting professional transformation I’ve experienced in my life.

Today, I can do things I only dreamed about a decade ago. I can fully embrace my hyper-generalist nature. I can reconnect disciplines that were previously separated by time, expertise, and organizational boundaries. I can become the kind of business polymath that modern specialization had almost made impossible.

AI has given me leverage to think broadly again.

And that’s why this moment is both terrifying and exhilarating.

Being in the harness is infinitely more interesting than being locked inside a gaming console. The real world becomes your environment. Every industry becomes your playground. Every inefficiency becomes an opportunity.

The ability to create business arbitrage, to identify opportunities between what is possible and what is currently being done, is becoming one of the most valuable skills of our era.

For anyone working in business, the defining skill of the coming decades will be the ability to transform intelligence into outcomes.

To turn tokens into decisions.

To turn decisions into execution.

To turn execution into business results.

That is the new game.

Welcome to the new world.

The only question is:

Are you ready to embrace it?

Access my harness with the exec plan!

I want to tell you how I ended up living inside a harness of agents instead of in front of a computer. To make that story land — and to make clear it wasn’t a personal preference but a forced move — I have to walk you through what happened to AI between late 2022 and now.

Not as a list of models. As a sequence of inflection points, each one breaking the rule the previous era ran on, each one forcing the next. There are four such breaks. They land roughly one a year. Together, they are the reason it is no longer possible to keep working the way I, or anyone, used to.

Access my harness with the exec plan!

Read them in order, because the logic only resolves at the end. By the time you reach the fourth break, the personal arc will look like what it actually was: a delayed response to an exponential the rest of the system had already absorbed.

2022 → 2024: pre-training scaling, and the chat era it produced

In November 2022, ChatGPT became public. Within months, the rule that had been quietly running AI since 2020 became visible to everyone: make the model bigger, feed it more data, and it gets smarter.

Access my harness with the exec plan!

This was pre-training scaling — the original scaling law. Dario Amodei put it plainly in 2024: from 2020 to 2023, the thing being scaled was pre-trained models trained on increasing amounts of internet text, with a tiny bit of fine-tuning on top. The recipe was simple, the gains were stunning, and the product was equally simple — chat:

• One model, one turn, one human. The user prompted; the model answered. The user prompted again. Every step was driven from the outside.

• The interface was a window. Operating happened by hand, in real time, at the chat surface.

• What it rewarded was operating skill. Knowing how to structure a prompt, work the window, read the output, push it again. Being good at chat was a real edge. It carried a lot of careful, capable people for two years.

Underneath, though, the engine driving the gains was already running into a wall. By 2024, the conversation in papers and at NeurIPS had shifted to “diminishing returns”:

• Doubling pre-training compute no longer doubled the improvement. The curve was bending, not breaking — but it was unmistakably bending.

• High-quality training data had largely been exhausted. The internet had been scraped. The books had been ingested. Code had been processed. The cheap, dense tokens were gone.

• The labs knew it before the public did, and started saying so by the end of 2024.

This is the structural fact everything else is downstream of. Pre-training scaling hit a wall. But the frontier didn’t stop — it never does. It had to find a new place to put compute. The era of “just make it bigger” was ending, and scaling itself had to relocate.

Hold that move in mind: when one axis flattens, the frontier moves outward to the next layer. It happens four times in this story.

September 2024: the frontier moved to test-time, and reasoning began

On September 12, 2024, OpenAI released o1 — a model designed to spend more compute thinking at the moment you used it, not at the moment it was trained. The full version shipped in December as part of the “12 Days of OpenAI” event. Within months, every major lab had reasoning models in production: OpenAI o3-mini (January 2025), o3 and o4-mini (April 2025), Anthropic’s reasoning Claude, Google’s Gemini Thinking, DeepSeek R1.

Access my harness with the exec plan!

The technical detail mattered less than the structural fact. Scale had migrated. The new way to make models smarter was not to grow them, but to let them deliberate. Compute that used to be spent in training was now being spent in inference — the budget moved from before deployment to during use.

That single migration kicked off the second era, and it had three immediate consequences:

• The unit of work expanded from a turn to a task. A reasoning model could chew on a problem for minutes, not seconds. The human’s role shifted from “operate every step” to “pose the problem, judge the result.”

• Smaller models became serious contenders. A small model with a sufficient thinking budget could outperform a much larger model with none. The “biggest model wins” rule of pre-training quietly stopped applying.

• Latency stopped being a vice. The market accepted models that took longer to answer, because the answers were structurally different — they showed work, reasoned across steps, caught their own errors mid-stream.

But the real consequence wasn’t visible until you looked one step further. A model that can think step by step can also act step by step. It can call a tool, check the result, decide what to do next, and call another tool. It can run for minutes, not seconds. It can chase a goal across many turns without a human between them.

Reasoning, in other words, was the precondition for agency. The chat era’s defining shape — human in the loop, every turn — was about to break, and o1 was the first crack.

2025: the agent era, and the protocol that made it real

The agent era didn’t arrive because models suddenly got smart enough. It arrived because two things landed in the same window:

Access my harness with the exec plan!

• Reasoning unlocked autonomous step-taking from the inside. A model could now run a chain of thought, evaluate intermediate results, and adapt its plan mid-task.

• The Model Context Protocol gave it hands. In November 2024, Anthropic open-sourced MCP — a single standard for how an AI model connects to external tools, data, and applications. The industry called it “the USB-C of AI.”

MCP went from announcement to infrastructure faster than any AI standard before it:

• March 2025 — OpenAI adopted MCP across the Agents SDK, Responses API, and ChatGPT desktop.

• By late 2025 — 97 million monthly SDK downloads, 10,000+ active servers, first-class support in ChatGPT, Cursor, Gemini, Microsoft Copilot, and Visual Studio Code.

• December 2025 — Anthropic, OpenAI, and Block jointly formed the Agentic AI Foundation under the Linux Foundation and donated MCP into it, with AWS, Google, Microsoft, Cloudflare, and Bloomberg as supporting members.

The plumbing had become industry infrastructure. What that combination produced was a fundamentally different thing in your computer. Not a chat companion. An agent — a system that takes a goal and runs with it, calls tools on its own, reads its own results, corrects its own errors, and comes back when the work is done.

Through 2025, every major lab shipped autonomous agent products:

• OpenAI — ChatGPT Agent mode (operator-style autonomous browsing, scheduling, multi-step tasks).

• Anthropic — Computer Use (the model controlling a real desktop, clicking, typing, navigating).

• Microsoft, Google, Meta, Amazon — all shipping agentic equivalents through 2025.

The shape of work changed underneath my hands while I was still operating. Where the chat era was operate every turn, the new way was:

• Hand a goal to the system.

• Let it run.

• Judge the result.

That is not the same job. It is a different job entirely. The most productive people quietly stopped operating. I had not.

This is the period — roughly mid-2025 onward — when I started getting out-produced by people working the same hours with the same tools. The gap widened week by week. I just hadn’t yet identified the layer the gap lived on.

2026: swarms, AGaaS, and the form factor leaves the desk

The shift from chat to a single agent was the visible break. The less visible one — the one happening as I write this — is from a single agent to a swarm.

Access my harness with the exec plan!

Once orchestration is standardized over MCP, an agent stops being a thing you launch and becomes a unit you compose:

• One agent becomes many specialists. Narrow agents — one for content, one for analytics, one for outreach, one for review — each with a single job.

• They run in parallel, on independent schedules. Not a serial pipeline; a swarm.

• They share a single source of intelligence. A common memory layer, a cached source of truth, gated approvals where stakes are high.

The unit of work climbed again — from a turn (chat), to a task (agent), to an operation (swarm). And the scaling axis migrated one more rung outward: not the model, not the loop, but the orchestration around them.

Capability is now grown by adding agents, loops, gates, and memory in coordination. The harness is the new scaling layer.

The business model mutates to match, because the unit of value travels with the frontier:

• SaaS sold a tool and charged for the seat. A human did the work inside it. The pricing assumed human operation as the rate-limiting step.

• AGaaS — agents-as-a-service — sells the work itself. You don’t buy the software and operate it. You buy the outcome an agent or a swarm delivers.

• The thing being priced shifts from an instrument a person uses to a result a system produces. AWS’s leadership has stated openly that agentic AI applied to e-commerce could be “the next multibillion-dollar business for AWS.” OpenAI has projected that roughly one-third of its 2025 revenue would come from agentic AI tooling. Outcome-based pricing is moving from edge case to default.

And the form factor follows the same vector outward:

• Chat needed a screen. You sat at it; the work happened where you were.

• Agents tolerate a phone. The work runs in a runtime elsewhere; you steer through a thin handle.

• Swarms can be steered from anywhere a goal can be uttered. Voice. Glasses. An ambient surface. The screen shrinks because the work it used to hold has moved off it.

The next surface won’t be a laptop. It will be an AI-native object — closer to an always-on personal-agent appliance than a PC — that you speak goals into and tap approvals on.

That is where we are in June 2026. Not at the end of any cycle, but visibly running the fourth scaling era after pre-training, post-training, and test-time: agency and orchestration as the place where capability is now grown.

The forcing function: one rule, four iterations

Step back from the four breaks and a single move repeats:

Access my harness with the exec plan!

When the current scaling axis hits diminishing returns, the frontier doesn’t stop — it relocates outward, one layer further from the model. Each relocation creates a new unit of work, a new business model, and a new form factor, and renders the prior layer’s defining skill a commodity.

The cycle, named: new axis → new unit of work → new business model → new form factor → old layer commoditizes → repeat.

Run that against the actual record:

• Pre-training (2020–2024) scaled the model.

  • Unit: a turn. Business: SaaS. Form: a desktop chat window. Skill rewarded: operating it well.

  • What broke it: data exhaustion + diminishing returns from naive scaling.

• Test-time (Sept 2024 → 2025) scaled the thinking.

  • Unit: a task. Business: reasoning-tier subscriptions ($200/mo Pro, dedicated reasoning APIs). Form: still a screen, but the human stepped further back. Skill rewarded: framing and judgment.

  • What broke it: reasoning made agency feasible; the loop wanted to close.

• Agency (2025) scaled the loop.

  • Unit: a goal. Business: outcome delivery. Form: agent + phone. Skill rewarded: setting frames the loop runs inside.

  • What broke it: once agents work, you want many of them, coordinated.

• Orchestration / swarms (2026 →) scales the harness.

  • Unit: an operation. Business: AGaaS. Form: ambient surface. Skill rewarded: authorship across a swarm.

Each iteration is faster than the last:

• Pre-training ran ~4 years (late 2020 → late 2024).

• Test-time ran ~1 year (Sept 2024 → late 2025).

• Agency ran ~1 year (2025).

• Orchestration is the era we are inside right now.

The compression isn’t rhetoric or vibe; it is the visible spacing of inflection points since 2020, and it is the part that hits humans hardest. You no longer get years to learn the new layer before it commoditizes.

This is what I mean when I say the transition was forced, not chosen. I didn’t pick a workflow. I got carried by a scaling law that kept relocating capability outward — and the only way to stay near where value was being made was to move with it.

What this did to me

For about eighteen months — while the second and third eras were happening — I worked the way I always had. In the loop, turn by turn, operating well. I was good at it. I had been good at it for two years. I had built habits around it.

And I was being out-produced. At a widening rate. By people working the same hours, on the same models, with the same access.

For a long time, I misdiagnosed it:

• First I told myself it was a discipline problem. I tried longer hours. Sharper focus. Better prompts. The gap kept widening.

• Then I told myself it was a tooling problem. I tried better models, better wrappers, better workflows. The gap kept widening.

• Eventually I realized it was a layer problem. The rung I was standing on — operating — had quietly become the part the machine does for itself. Every hour I spent operating by hand was an hour spent doing something the system now does at scale, for almost nothing.

Access my harness with the exec plan!

That is the punchline of the four-year arc seen from inside one person’s career. Each scaling relocation deprecates the previous layer’s defining skill. The people who tripled their output in 2025 had not found a better tool. They had stepped one rung outward — from operating to framing, from doing the work to authoring it — while I was still working harder at the part that no longer mattered.

When the world’s software output roughly tripled while the number of people doing the work stayed flat (GitHub’s own April 2026 figures), the people producing three times as much were not typing three times faster. They had restructured how the work happens — one person directing a system, instead of one person performing the steps.

Access my harness with the exec plan!

And the moment enough people did that, the market quietly reset its expectation of what a single person produces. Producing careful, excellent work at the old volume stopped being a stable position; it became a slow exit, because the baseline had moved.

So I moved. Not because the new way was exciting, but because the alternative was to keep doing careful work at a level the market had already priced as not enough.

• I stopped operating and started framing.

• I stopped working inside a chat window and started directing a harness from wherever I happened to be.

• The frame I set in the morning steered a swarm through the day.

• The work stopped running at my desk and started running in a remote runtime I held a thin handle to.

I didn’t leave the desk on purpose. The work left, and I followed it.

The bedrock underneath the four eras

A reasonable objection follows immediately, and it deserves an honest answer.

Access my harness with the exec plan!

If every rung commoditizes, and the cycle keeps accelerating, what stops the rung I just moved to from sinking next? Won’t framing get automated the way operating did?

Yes — as a craft, it will. Models will draft problems, propose constraints, generate evaluation criteria. The skill of framing will get machine help, and within a year or two it will get a lot of it. So if framing-as-a-skill were what I was relying on, I would just be one rung higher on a sinking ladder, with the floor coming up faster.

But the four-era arc points at something deeper than any single skill. Every rung the frontier has climbed has been a capability — and every capability eventually commoditizes when scale relocates. Operating fell. Framing-as-craft will fall. Orchestration-as-craft will fall after that.

The thing that can never be automated, because it isn’t a capability at all, is authorship.

• Wanting a particular outcome. Not the ability to produce a particular outcome — the underlying wanting of it.

• Choosing which tradeoffs are acceptable. Not the analytical work of comparing them — the moment of deciding, with the weight of consequence.

• Answering for the result when it ships. Not the work of producing it — the liability for what it does in the world.

The machine can take on any competence given enough capability. It cannot take on wanting, or liability. It can draft a thing; it cannot be the one who owns it.

That is the bedrock the churn can’t reach, because it isn’t a skill that can be learned faster by something faster than you. It is a question of whose will, and whose responsibility.

So the deep “why” of my transition isn’t “use agents.” It is a migration of where I stand:

• From the person who performs the work

• To the person who authors it

That is the only ground the next scaling relocation cannot reach, because it isn’t on the ladder. Everything else I do now — the frames, the gates, the swarm — sits on top of that one position. I stopped trying to be faster than the machine and started being the thing it answers to.

That is the why.

What it actually looks like to live there — what life in the harness feels like day to day — is the next piece.

Key Takeaways & Mental Models

Access my harness with the exec plan!

The Scaling Migration — AI’s scaling laws didn’t stop; they keep relocating outward from the model. Pre-training (2020–2024) → test-time reasoning (Sept 2024 → 2025) → agency (2025) → orchestration / swarms (2026). Each relocation grows capability at a new layer.

The Forcing Cycle — Each new scaling axis creates a new unit of work, a new business model, and a new form factor, and turns the prior layer’s defining skill into a commodity. Run it four times: chat → swarms, SaaS → AGaaS, screen → ambient surface.

The Compression — Pre-training ran four years. Test-time ran about one. Agency ran about a year. Orchestration is now. The compression is the visible spacing of inflection points since 2020 — not rhetoric, geometry.

The Operating Trap — Continuing to compete on the rung the frontier just left feels like diligence. It is the fastest way to fall behind, because the system now does that rung for free, at scale, and without rest.

The Output Asymmetry — When output triples on flat headcount, the gap isn’t effort — it’s restructuring. Once the baseline resets, holding the old layer isn’t a preference; it’s a slow exit.

The Accountability Floor — Every rung on the ladder is a capability, and every capability eventually commoditizes. The one position that doesn’t is authorship — wanting, choosing, answering for outcomes. It’s not on the ladder, which is exactly why the churn can’t reach it.

With massive ♥️ Gennaro Cuofano, The Business Engineer

As an analyst, a student of history, and someone deeply interested in structural realities, I see it as my responsibility to make a deliberate effort to contextualize, abstract, compress, and build mental models that help explain the world around us.

That is what The Business Engineer is about. For me, it is a lifelong quest.

So when ChatGPT was released, I felt it was essential to provide a framework, a mental model capable of making sense of the emerging AI era.

At the time, despite the relentless pace of progress in AI, it is easy to forget how many people believed everything would change within a single year. The expectations were immense. In that environment, I felt a better frame was needed.

That is where the AI Supercycle Thesis emerged.

And a word of caution: the term supercycle should not be interpreted as a purely economic concept. It goes far beyond economics. It describes the intersection of three powerful forces: geopolitics, cultural transformation, and economic change.

The economy is only one layer of the story. In many ways, it is the instrument through which deeper geopolitical and cultural shifts express themselves.

The AI Supercycle is ultimately an attempt to understand the thread connecting these forces and how, together, they shape the next era of human development.

For that reason, the AI Supercycle is not a forecast. It is a structure. A thirty-to-fifty-year economic transformation comparable in scope to the Industrial Revolution, running on three nested clocks, exhibiting the paradoxical dual character of bubble and revolution at the same time, and operating through a nine-layer industrial stack that begins in mineral extraction and ends in geopolitical control. This piece is the map.

Stay Ahed of The AI Supercycle →

Subscribe To The Podcast

The Argument in One Paragraph

We are inside the first decade of a transformation that will run for half a century.

It has three nested cycles operating at different time horizons, a dual character that is simultaneously a bubble and a supercycle, and a layered industrial stack of nine layers, running from energy at the bedrock to governance at the ceiling.

The ceiling does not behave like a layer. It behaves like a control plane perpendicular to the whole stack — one that answers to geopolitics rather than engineering.

The floor does not behave like a market. It behaves like a geopolitical chokepoint — a small handful of countries deciding what the rest of the stack is allowed to build. Everything between the floor and the ceiling is where the next decade of competition lives.

What the Supercycle Actually Is

Stay Ahed of The AI Supercycle →

The launch of ChatGPT on November 30, 2022 was not the arrival of AI. AI had been arriving for years before that night.

What changed is that AI reached the point where it could scale to billions of users on the same day. That capability threshold — distribution at consumer-internet scale — is what triggered the supercycle. It forced every layer of the existing technology economy to absorb a new substrate simultaneously, and substrate-level shifts of that magnitude are what produce multi-decade economic transformations.

Three cycles run inside the supercycle, each on its own clock:

• Short cycle (5–10 years): rapid capability improvements and market disruptions. Where the bubble lives. Where most pundits spend their attention.

• Medium cycle (10–20 years): industry restructuring, business-model evolution, the end of incumbent dominance in software and search.

• Long cycle (30–50 years): civilizational transformation. Comparable to the half-century electricity took to reorganize industrial production around itself between 1890 and 1940.

Conflating these clocks produces the most common analytical errors of the moment. The “AI is overhyped” camp and the “AI changes everything” camp are usually arguing about different cycles without realizing it.

The dual character is the most useful piece of intellectual scaffolding for navigating the present. AI exhibits genuine bubble characteristics — excessive hype, overvaluation, capex commitments that exceed the unit economics of any single application — at the same time as it exhibits genuine supercycle characteristics — real productivity gains, fundamental restructuring of profit pools, civilizational impact. Both are true.

The mistake is treating them as competing claims. They operate on different cycles. The bubble can pop on the short cycle while the supercycle continues uninterrupted on the long cycle, exactly the way the dot-com bust did not stop the internet from becoming the substrate of the next thirty years.

The three phases of integration unfold over the supercycle’s full arc:

• Phase 1 — Linear Expansion. AI as a layer on top of every internet-era industry. Web Squared. E-commerce, social, fintech, digital marketing, software-as-a-service all get amplified rather than replaced. This is the decade we are in.

• Phase 2 — Non-Linear Restructuring. Industries get rebuilt around AI-native architectures rather than retrofitted onto pre-AI ones. SaaS gives way to its successor architecture. Search gives way to assistants. Customer service gives way to autonomous agents.

• Phase 3 — Civilizational Reorganization. What the supercycle is actually for. Machine cognition becomes a general-purpose industrial input, comparable to what electricity became after 1920.

The canonical transition signal is the “BlackBerry moment.” Google’s search revenue is hitting record highs at the exact moment AI assistants pose an existential threat to its core business — the same pattern as BlackBerry peaking as the iPhone arrived. Supercycle transitions look like strength right before they look like collapse. This is the pattern to watch for across every industry the supercycle touches.

The Nine Layers

Stay Ahed of The AI Supercycle →

The AI economy is not a list of companies racing each other. It is a layered industrial stack — and at any given moment the binding constraint sits at a different layer than it did six months ago. Reading the map well means knowing where the constraint currently lives and where it is rotating to next.

The nine layers, top to bottom:

Governance · Distribution · Agentic Harness · Foundation Models · Compute Capacity · Networking & Protocols · Silicon · Foundries & Packaging · Energy & Physical.

Two rules govern the stack:

• Each layer is constrained by the one below it. You cannot ship a model without compute. You cannot ship compute without silicon. You cannot ship silicon without foundries. You cannot ship foundries without energy. The bedrock dictates what the upper floors can do.

• Each layer is commercialized by the one above it. Silicon needs a model to monetize. Models need a harness. Harnesses need distribution. The roof dictates what the lower floors can earn.

Read the map two ways. Read a column to see one company’s full vertical posture — Google’s nine-layer column shows the closed-loop integration that nobody else has matched. Read a row to see who owns a single layer — the networking row, for instance, reveals NVIDIA’s monopoly and the fact that everyone else in the AI economy is paying rent on it. The diagonals where dominance concentrates are where the supercycle’s profit pools live.

Layer by layer, what each one is and why it matters:

• Layer 9 — Governance. The rules that determine whether a model can be released, deployed, sold, or used. Capability gating inside labs, procurement frameworks inside enterprises, export controls between nation-states, litigation over contested deployments. No longer a passive layer; an active priced variable.

• Layer 8 — Distribution. The surfaces through which AI reaches end users. ChatGPT, Gemini, Copilot, the Apple-Gemini handshake, Meta’s social graph. The decade’s most expensive land grab.

• Layer 7 — Agentic Harness. The wrapper that turns a foundation model into a usable agent. Memory, tools, planners, sub-agent coordination, retry and rollback. CUDA’s analog at the agent layer. The most contested architectural layer of the next three years.

• Layer 6 — Foundation Models. The frontier and the long tail. OpenAI, Anthropic, Google DeepMind, Meta, xAI, DeepSeek, Mistral. The layer everyone watches and the one most likely to commoditize first.

• Layer 5 — Compute Capacity. Hyperscaler GPU clusters, neoclouds, custom-silicon estates. Where the capex bubble lives. Where the binding constraint sat in 2024 and where it is gradually rotating away from.

• Layer 4 — Networking & Protocols. The interconnect that turns thousands of GPUs into a single coherent compute fabric. NVLink, InfiniBand, optical interconnects. Now over 20% of rack-scale system cost; growing faster than any other line item.

• Layer 3 — Silicon. Three competitive categories within one layer: generalist substrate (NVIDIA), hyperscaler custom (TPU, Trainium, MTIA), merchant custom challengers (Cerebras, Groq, SambaNova). The within-layer split is what makes silicon strategically interesting again.

• Layer 2 — Foundries & Packaging. TSMC, Samsung, Intel Foundry, and the HBM oligopoly (SK Hynix, Samsung, Micron). Allocation power at the foundry is now more consequential than chip design itself. The binding constraint for the entire upper stack.

• Layer 1 — Energy & Physical. Gigawatts, transmission, cooling, land, water, rare-earth magnets. The bedrock everything else stands on. The constraint that defines the ceiling on how much intelligence can be produced in any given year.

The supercycle is not unfolding in time. It is unfolding in layers. The job of any operator, investor, or builder is to know which layer they are operating inside and which layer the binding constraint is rotating toward next.

The Ceiling Is a Control Plane

Stay Ahed of The AI Supercycle →

Layer 9 does not behave like a layer. It behaves like a control plane perpendicular to the whole stack — capable of switching off any company at any layer beneath it on a timeline measured in days rather than years.

A single government directive can darken a frontier model globally in seventy-two hours. A single procurement framework inside a Fortune 100 buyer can shift demand at the model layer overnight. A single litigation outcome can re-architect what is permissible at the harness layer. Capability gating decisions inside the labs themselves can withhold a model class from market for reasons that have nothing to do with technical readiness.

Layer 9 answers to geopolitics, not to engineering. That is the structural read, and it changes the valuation logic at every layer beneath it. Models, compute, silicon, foundries — none of them can be priced as standalone technology assets anymore. They have to be priced with an embedded discount for the political volatility of the control plane.

The supercycle has a ceiling now, and the ceiling is political.

The Floor Is a Chokepoint

Stay Ahed of The AI Supercycle →

If Layer 9 is the ceiling, the physical floor is a geopolitical chokepoint. The supercycle runs on rare earths before it runs on tokens. Every GPU cooling fan, every data-center motor, every robotic actuator, every EUV lithography machine depends on neodymium-iron-boron magnets. One country controls roughly 60% of global extraction and over 90% of processing capacity.

That concentration has been weaponized. Extraterritorial export controls — modeled on US semiconductor restrictions and applied in reverse — now reach any product containing 0.1% or more Chinese-sourced rare earths by value, regardless of where it is manufactured.

Twelve of the seventeen rare-earth elements are under restriction. The “Affiliates Rule” presumptively denies export licenses to any importer with 50%-or-greater ownership by entities on China’s control lists.

The response is a triangular competition:

• United States — multi-billion-dollar EXIM commitments, Defense Production Act invocations, Brazil partnership, domestic processing buildout.

• European Union — strategic stockpiling, Australia partnerships, processing investment.

• China — processing dominance, vertical integration from mine to magnet, regulatory leverage applied with surgical precision.

Brazil emerged as the pivotal countermove — second-largest proven reserves behind China, only 30% of the country geologically mapped, US-Brazil rapprochement driven explicitly by the shared interest in breaking the processing monopoly. The next decade of critical-minerals supply chains will be reorganized around that pivot.

The supercycle runs on dirt before it runs on tokens. Whoever controls the floor sets the ceiling on what the rest of the stack can build.

The New Stack — Software, Rebuilt

Stay Ahed of The AI Supercycle →

The supercycle’s effect on software is captured by a single sentence: the agent is the consumer, and the human is the principal. Once that shift completes, the existing software-as-a-service stack becomes structurally obsolete. A new five-layer architecture replaces it:

• Knowledge Substrate — typed graph, not relational table. Agents query by description; humans query by SQL. The substrate decides which kind of company you actually are.

• Orchestration Layer — directed graph of agents with planner, sub-agents, retry, rollback, external capability calls. Not a deterministic chain.

• Access Surface — Model Context Protocol endpoints, tool catalogs, machine-readable schema, pricing APIs, policy declarations, rate limits. The exterior surface that agents call into from outside the company.

• Metering Layer — principal delegates budget; agent consumes against a rate card. Outcome definitions, machine-readable rate cards, real-time metering, multi-principal accounting, negotiation-aware pricing.

• Trust Layer — cross-cutting band that cuts through all four horizontal layers. Agent identity-as-buyer, audit trails, attestation, capability scoping.

Three anti-patterns kill incumbents trying to retrofit:

• Database-as-Substrate — relational tables pretending to be a knowledge graph. The agent cannot find what it needs by description.

• Logic-as-Orchestration — sequential code pretending to be agent coordination. Brittle the moment an agent has to plan.

• Pricing-Page-as-Metering — a marketing page pretending to be a rate-card API. The agent cannot transact.

The master diagnostic is one line: a pricing API beats a pricing page. If your competitor exposes a machine-readable rate card and you expose a “contact sales” button, you are not in the same market anymore.

The Mutation Map — Five Archetypes

Stay Ahed of The AI Supercycle →

Every existing software company has to mutate, retreat, or die. The responses cluster into five archetypes:

• Veneer — chatbot bolted onto an unchanged stack. Theater. Dies first.

• Surface — improved interface layer on the same substrate. Buys a year of relevance.

• Reprice — moves from seat-based to outcome-based pricing without rebuilding the underlying stack. Survives medium-term but hits a margin ceiling.

• Substrate — rebuilds the knowledge layer for agent consumption while keeping the upper stack. Survives long-term.

• Rebuild — full agent-native architecture from substrate to metering. Wins the next cycle.

Only Substrate and Rebuild survive structurally. Everything to the left of them is buying time. The five-year window for incumbents to commit closes around 2028, and after that the agent-native companies founded post-2023 begin eating the bottom of the existing market on price and the top on capability simultaneously.

The Analytical Toolkit

Stay Ahed of The AI Supercycle →

Five cross-cutting tools sit above the nine-layer map and help read it:

• The Three AI Tribes — Substrate Tribe (infrastructure plays), Surface Tribe (interface plays), Sense Tribe (data and judgment plays). Tells you which tribe a company belongs to and which one is best positioned at any given layer.

• The Barbelled Distribution Economy — value concentrates at the extremes (massive-scale platforms and deep-niche specialists); the middle hollows out. Explains where value accrues across every layer of the stack.

• The Four Scaling Paradigms — pretraining, post-training, inference-time, agentic-loop. Tells you which scaling regime a model company is betting on and where the next capability gain comes from.

• Cognitive Range — the human variable. AI provides breadth at every level of resolution; humans provide navigation between levels. Full-range cognitive workers earn a structural premium that automation cannot touch.

• The FRED Test — the diagnostic for whether a workflow survives agentic automation. Frequency, Repeatability, Error tolerance, Decomposability. Score high on all four and the workflow is automated within the cycle; score low on any one and the human stays in the loop.

These are not separate frameworks. They are different cross-sections of the same map.

What’s Next

Stay Ahed of The AI Supercycle →

Three structural moves to watch over the next twelve to twenty-four months:

• The control plane hardens. Expect more single-directive shutdowns, more procurement-driven model selection, more litigation deployed as competitive weapon. The companies that price governance into their architecture from day one will outperform the ones that treat it as compliance overhead.

• The floor shifts. Brazil’s reserves come online slowly — five to ten years to scale processing. The interim is where the leverage gets used most aggressively. Watch processing capacity and packaging allocation, not extraction headlines.

• Mutation pressure on the upper stack accelerates. Reprice archetypes hit their margin ceiling. Substrate archetypes start shipping rebuilt stacks. Agent-native companies founded post-2023 start eating the existing market from both ends.

The supercycle does not move evenly. It moves layer by layer, and the binding constraint rotates. The job is not to predict which layer is next. The job is to read the map well enough to recognize the rotation when it happens.

Key Takeaways & Mental Models

Stay Ahed of The AI Supercycle →

Five named models govern the supercycle as a whole:

• The Nested Clock — three cycles (5–10, 10–20, 30–50 years) run simultaneously inside the supercycle. Bubble and revolution are both true, on different clocks. Conflating them is the most common analytical error of the moment.

• The Layered Stack — competition does not happen in “the AI industry”; it happens at specific layers within a nine-layer industrial stack. Read columns for posture, rows for dominance, diagonals for profit pools.

• The Control Plane — Layer 9 is not a layer. It is a plane perpendicular to the stack. It answers to geopolitics, not to engineering, and it discounts valuation at every layer beneath it.

• The Geopolitical Floor — the supercycle runs on dirt before it runs on tokens. Whoever controls extraction and processing sets the ceiling on what the rest of the stack can build.

• The Agent Is the Consumer — once that shift completes, the existing software stack becomes structurally obsolete. Only Substrate and Rebuild archetypes survive the transition.

With massive ♥️ Gennaro Cuofano, The Business Engineer

Somewhere in the last few months, the shape of how I produce has changed. I stopped typing prompts and reading answers one at a time, and started setting a frame in the morning and watching a swarm of agents carry it through the day — drafting, optimizing, scheduling, measuring, adjusting — while I did the one thing none of them can do for themselves: decide what was worth doing, and define what good meant before any of it ran.

And I’m rarely at a desk when it happens. I set the frame from a phone — in transit, between other things, walking — because the work no longer runs where I am. It runs in a runtime somewhere else, and the thing in my hand is just the surface I steer it through. The computer I spent thirty years sitting in front of has quietly left the room.

This isn’t a piece about tools. It’s about what’s left for a person to do once the tools can do almost everything. The answer is smaller and sharper than most people expect — and the whole map of it fits in six moves. Here they are, one at a time.

Access My Full Harness in The Exec Plan

The edge has moved to framing

The scarce, valuable skill is no longer operating the model. It’s framing the work before the model runs.

Here is the rule that governs every technology shift: when a capability becomes universal, it stops being an advantage, and the edge moves up the stack to whatever is still scarce.

Access My Full Harness in The Exec Plan

Trace it. Hardware was once the edge — until hardware became cheap and abundant, and the advantage moved up to software. Software commoditized, and the edge moved to distribution. Then to data. At each step, once everyone had the layer, it stopped being where the advantage lived, and the advantage climbed one rung higher.

AI capability has now reached that point. Everyone has the same frontier models. The compute is cheap, the interfaces are frictionless, and the gap between a well-funded team and a solo operator with a credit card has all but closed. So the edge has already left the model itself. For a short while it sat one rung up — in operating the model: the skill of working a chat window well, structuring the problem, reading the output, re-prompting toward something sharp.

That rung is commoditizing too, and fast — because of agents. An agent doesn’t wait for you to prompt it. It prompts itself, reads its own output, notices its own errors, and re-runs. The skill of working the chat window is being absorbed into the system. So operating, the thing that was briefly the edge, is becoming something the machine does for itself.

Which moves the edge up one final rung — to the one input the agent cannot generate on its own: the frame. Framing is everything you decide before the agent runs. It has four parts:

• Problem definition — what is actually being solved, stated as a mechanism, not a wish.

• Constraints — the boundaries any acceptable answer has to stay inside.

• Evaluation criteria — what “good” looks like, specified in advance.

• Stopping conditions — when the agent should halt, escalate, or hand back.

The frame is the whole of the human contribution. Everything downstream of it is execution. That is the first move, and the rest of the piece follows from it: if framing is the edge, then everything else — why it matters, who’s exposed, how to do it, what it steers, and what it does to the industry — is a consequence.

Autonomy removed the safety net

Access My Full Harness in The Exec Plan

In the old way of working, a weak first attempt was cheap because you could fix it as you went. Autonomy removes that, so the first frame now decides the outcome.

Think about how working with a chat model used to go. You asked a rough question, got a rough answer, saw it was rough, and asked a better one. The cost of a bad first try was low, because you stayed in the loop turn by turn and caught the drift as it happened. Trial and error did a lot of the thinking for you. A careful operator and a careless one both reached a decent answer in the end — the careless one just took longer.

An autonomous agent removes that loop. It runs fifty steps without checking back. There is a frame at the start and a result at the end, and nothing in between where you correct course. If the frame was weak — wrong problem, soft constraints, no definition of “good” — the agent doesn’t notice. It executes the weak frame faithfully, confidently, and fast, and hands you a polished, internally consistent answer to the wrong question, delivered at a speed that makes it look authoritative.

That is the characteristic failure of this era, and it has a shape worth naming: confidently wrong at scale. A small error in the frame fans out into a large error in the output, because every autonomous step compounds the one before it. The old way punished a bad frame with a few wasted minutes. The new way punishes it with a finished deliverable that’s wrong in a way nobody catches until it ships.

Access My Full Harness in The Exec Plan

This sorts people into three tiers, and it’s worth being blunt about who’s where:

• Prompters — whose skill was phrasing. Obsolete; the agent phrases better than they do.

• Operators — genuinely skilled at working the loop turn by turn. Newly exposed, because the loop they were good at is the part being automated away.

• Framers — who can specify a problem, its constraints, and its success criteria before any execution starts. This is the tier that wins, and it’s thin.

The uncomfortable part is that the exposed tier is full of capable people. Skilled operators assume their fluency carries over. Some of it does — but the part that carries over is exactly the part that’s commoditizing, and the part that doesn’t carry over, framing, is the part that now decides everything. It was never the thing they practiced.

Access My Full Harness in The Exec Plan

How to actually frame

Access My Full Harness in The Exec Plan

Framing is a discipline with specific moves, not a personality trait. Three of them matter most.

Find the binding constraint before you delegate. Most problems aren’t what they look like on the surface, and an agent will optimize whatever you point it at — including the wrong thing. Solving the wrong bottleneck at agent speed is worse than solving nothing, because it produces motion that looks like progress. So the first act of framing is to ask: what is the one thing that, if left unaddressed, makes every other improvement irrelevant? You answer that before the agent opens, because the agent can’t.

Decide what “good” means before anything runs. When you worked in a chat window, you judged the output by eye, after the fact. You cannot eyeball fifty autonomous steps, and you certainly cannot eyeball a hundred parallel runs. So the judgment has to move earlier: you specify what a good result looks like in advance, in terms concrete enough that correctness is checkable without you re-reading everything. Evaluation stops being a final glance and becomes part of the frame. This is the hardest of the three, because it forces you to know what you want with a precision most work never demands.

Separate the mechanism from the story — because the agent won’t. Hand a model a compelling narrative and it will execute the narrative. It has no built-in defense against a frame that reads well and is structurally false. Knowing the difference between what is mechanically true and what is merely a good story is the difference between a system that compounds correctness and one that compounds a plausible mistake.

There’s a practical upshot. A thinking system — a repeatable way of mapping constraints, classifying what’s a real advantage versus a temporary one, separating mechanism from narrative — stops being a personal habit and becomes the thing you load into the machine. It’s the specification you hand the agent so it inherits your structure instead of improvising its own. The frame isn’t just the prompt you type. It’s the encoded judgment you front-load so the autonomous system runs inside it.

What the frame steers: the harness

Access My Full Harness in The Exec Plan

The frame is the human’s input; the harness is the system that executes it. The model is commoditized. The harness is where the real differentiation now lives.

A harness is the orchestration wrapped around the model: which agents you run, on what schedule, with what feedback loops, what approval gates, and what memory. The same model is available to everyone, so the model isn’t the edge. The harness is — and the ones that actually compound follow a handful of structural rules.

Use a swarm of specialists, not one mega-agent. A single agent asked to do everything degrades under load — the same reason companies have departments instead of one person who does all jobs. What works is a swarm of narrow specialists, each with one job, running on their own schedules. The agent producing content doesn’t need to know how a call-to-action gets tuned; the title optimizer doesn’t care about delivery. Specialization here is org design, not engineering.

Make the loop self-improving, or it’s just a cron job. An agent that runs the same playbook every day is automation that slowly decays. The agents that compound read their own results — which headline drew clicks, which copy converted — and feed that back into the next run. The durable asset isn’t the agent; it’s the learning loop.

Share one source of intelligence. If every agent independently asks “what’s working,” they drift and contradict each other. The fix is a shared module they all read from — one cached source of truth — so every decision is made from the same picture. Coherence is something you design in, not something you hope emerges.

Use gates, not guardrails. The instinct is to fence agents in with rules everywhere. What works is to let them run freely on low-stakes work — updates, optimization, scheduling — and put hard approval gates only in front of high-stakes actions: publishing, sending, spending. The ratio is the discipline: roughly 95% autonomous, 5% gated. Gate too much and you become the bottleneck, which destroys the speed that justified the system.

Treat memory as architecture. A system without persistent memory rediscovers its context every session, like a tourist. Structured memory — feedback rules, project state, preferences, reference pointers — loaded into every run is what lets the system accumulate knowledge. Mistakes become permanent rules; preferences become defaults. That accumulation is what turns a tool into an operating system.

The orchestration is the real engineering. Getting a model to write or send was never the hard part. The hard part is wiring eight or ten systems — content, analytics, delivery, social, payments — so an action in one triggers the right response in another. The plumbing between systems is the work now; the reasoning is the easy part.

Put those together and you reach the punchline: one person with judgment plus a harness produces what used to take a team. The old org chart for this kind of workload was a department — several content people, an SEO specialist, an email marketer, a social manager, an analyst, a developer, a designer. The harness collapses it to one person who supplies taste, judgment, and direction — the frame — while the harness supplies execution and pattern recognition at scale. The winners aren’t building AI. They’re building harnesses.

The computer left the desk

Access My Full Harness in The Exec Plan

Because the harness runs somewhere else, your physical relationship to computing inverts. The machine stops being a place you sit and becomes a process you steer from anywhere.

There’s a physical change underneath the cognitive one, and it took me a while to see it for what it was. I no longer sit in front of a computer to work. I set the frame from a phone, on the move, and the execution happens somewhere I’m not.

This isn’t a productivity habit. It’s the visible edge of a larger shift: the agent is becoming the computer. The old definition of a computer was a box you sat at — an app, on an operating system, on a chip, operated through a screen. The new definition, the one now being built straight into the silicon, is different: an agent is a brain (the model) plus a body (the harness) plus a runtime — wherever the work actually runs, whether that’s a cloud, a server, or eventually a robot. The runtime is the part that matters here, because by definition it isn’t your desk. Once the computer becomes the agent, it stops being a place you go and becomes a process running elsewhere that you hold a thin handle to.

This is also the end state of a longer progression. AI first ran in a sandbox, then learned to use tools, then learned to operate a whole computer, and finally converges with the computer itself — and convergence, experienced from the user’s side, feels like this: there’s no chair. The interface stopped being clicks and commands and became intelligence. You state a goal; you approve an outcome. And once the interface is intelligence, the form factor is free. A goal doesn’t need a keyboard. An approval doesn’t need a monitor. The big screen and the desk were artifacts of operating — and operating is exactly the part that just left.

What remains for the human collapses to two acts, and both are light enough for any device: set the frame, and clear the gate. A goal goes out; an approval comes back. Neither needs a workstation. A phone does it now. The next surface won’t even be a phone — it’ll be some AI-native object closer to an always-on personal assistant than a PC, something you speak goals into and tap approvals on. The screen shrinks because the work it used to hold moved off it.

Call the pattern the thin surface: when the interface becomes intelligence, the human’s surface shrinks to two interactions — frame-in and gate-out — that fit any device and untether the work from the desk. The harness runs remote; you carry the handle.

The strange part is how natural it feels. For three decades, “using a computer” meant arranging my body in front of one. Now the computer is a process I start with a sentence and check with a tap, from wherever I happen to be standing. I didn’t leave the desk on purpose. The work left, and I followed it.

Where the whole industry is heading

Access My Full Harness in The Exec Plan

The same logic that reorganized my desk is reorganizing the frontier. The entire industry is converging on a single contest — to own the harness.

Follow the harness up the stack and the macro picture falls into place.

The frontier AI labs are running deeply negative margins on heavy agentic usage. The easy reading is “the economics are broken.” The structural reading is the opposite: the harness is where the next moat sits, and the labs are paying to build it. Two facts make that rational rather than reckless. First, token costs are falling by orders of magnitude — what’s subsidized today is cheap to serve tomorrow, so the loss is really a financing cost on a future-cheap good. Second, once someone runs their whole operation through one lab’s harness, the cost of leaving is no longer the model — it’s the accumulated memory, the tuned loops, the wired-up orchestration. You can swap a model in an afternoon. You can’t swap a harness you spent a year teaching.

That’s why the competitive action is migrating to which features get withheld from subscription tiers and which capabilities stay API-only. The fight isn’t over raw intelligence anymore — that’s converging and commoditizing. It’s over the harness layer, because that’s where lock-in is built and where the margin eventually returns. And it’s migrating to the surface, too: if the computer is now a remote process plus a thin handle, then the runtime and the device that holds it become control points — which is why the hardware makers are suddenly racing to ship an always-on personal-agent device, not just a faster chip. Whoever owns where the agent runs, and the surface you steer it from, owns the next relationship with the user.

So here is the whole picture in one line. The model has commoditized. The frame is the human’s edge. The harness is the system’s edge. And the contest to own the harness — fought with the same logic from a solo operator’s phone to a trillion-dollar lab’s data center — is the real story of the AI industry right now. Everyone is arriving at the same realization: you don’t win by having the AI. You win by owning the harness around it, and by bringing a frame sharp enough to steer it.

The career consequence is direct. The old way rewarded lots of operators each working their own loop. The new way rewards a few people who can frame well, each steering many autonomous runs on a harness that compounds. Headcount in the operating tier shrinks; leverage concentrates in the framing tier. And the gap between a good frame and a bad one stops being measured in minutes — it’s measured in the output of the whole machine, correct versus confidently wrong, and invisible until it ships.

That’s the moment we’re in. Having the tools is table stakes. Operating them is automating. What’s left for a person is the part no model supplies for itself: the harness it runs on, and the frame you build before you let it run.

When people ask what I actually do now, the honest answer is: less, and more. Less operating — the harness handles that. More framing — which turns out to be the harder and rarer half. I live in the harness. But the harness doesn’t run on its own. It runs on the frame I bring it each morning, from wherever I happen to be standing. That’s the whole job now, and it may be the whole job for a while.

Key Takeaways & Mental Models — The Framing Models

The Framing Ladder — When a capability goes universal, the edge moves up the stack. It has now moved past operating the model to framing the work before it runs.

The Vanishing Loop — Autonomy removes the turn-by-turn iteration that let a weak first attempt get fixed. With no loop to recover in, the first frame decides the result.

Confidently Wrong at Scale — A bad frame isn’t caught; it’s executed. A small error in the frame becomes a large, polished, plausible error at the speed and volume of the machine.

Pre-Encoded Judgment — When you can’t watch every step, you have to define “good” before execution, not after. Evaluation moves from a final glance to part of the frame.

The Thin Surface — When the interface becomes intelligence, the human’s surface shrinks to two acts — frame-in and gate-out — that fit any device and lift the work off the desk.

The Frame Is the Moat — The one input that hasn’t commoditized is the structure you bring before the agent runs. Tools are universal; operating is automating; the frame is the edge that compounds.

The Harness Principles

Access My Full Harness in The Exec Plan

Swarm Over Mega-Agent — Narrow specialists on independent schedules beat one generalist. Specialization is org design.

The Self-Improving Loop — Agents that read their own performance and adjust compound; static automation decays. The loop is the moat.

Shared Intelligence — One cached source of truth keeps agents coherent; independent lookups produce drift and contradiction.

Gates, Not Guardrails — ~95% autonomous on low stakes, ~5% gated on high stakes. Over-gating makes the human the bottleneck.

Memory Is Architecture — Persistent structured memory turns mistakes into rules and a tool into an operating system.

Orchestration Is the Architecture — The plumbing between 8–10 systems is the real engineering. The reasoning is the easy part now.

Harness Theory — One operator with judgment plus an agent swarm replaces a department. The human brings the frame; the harness brings velocity

With massive ♥️ Gennaro Cuofano, The Business Engineer