The End of Friction as a Moat

The diagram does what good diagrams do. It turns a vague argument into a decision. It forces the room to pick what kind of speed it wants. It also forces the room to admit what it has been paying for without saying the words. The enterprise has been paying for legitimacy by buying time. The past decade trained us to talk about intelligence as the scarce resource. Data. Talent. Compute. Insight. We built organizations to gather those inputs, stack them into reports, and place them in front of humans who have the authority to act. That architecture made sense when intelligence lived mainly in people and moved at human speed. Now intelligence is getting cheap. Not wisdom. Not judgment. Intelligence in the narrow sense that matters operationally. The ability to propose actions, produce drafts, generate options, run scenarios, write software, and explain plausible reasons at a volume and pace that no team can match. Citrini Research’s 2028 Global Intelligence Crisis memo is useful because it treats that change as a system event rather than a product launch. It describes a world where capability and adoption feed layoffs, which feed demand weakness, which feed margin pressure, which feeds more automation. It is a loop, not a headline. It is also a provocation, because it asks the reader to treat “cheap intelligence” as a macro variable that can shake everything from software pricing to household consumption to the plumbing of payments. You can read his article here: https://www.citriniresearch.com/p/2028gic The most important part of that provocation is not whether the scenario is exactly right. It is what the scenario implies about where scarcity moves. If intelligence becomes abundant faster than institutions can adjust, then the scarce unit is no longer the ability to generate a recommendation. The scarce unit is the right to act on it. Legitimacy becomes scarce. That word sounds philosophical until you put it in an operating review. Then it becomes painfully concrete. Legitimacy is permission. It is authority. It is the boundary that separates a suggestion from an intervention, and separates an intervention from an incident. A firm can survive a lot of bad ideas if those ideas cannot touch anything. A firm cannot survive a lot of ungoverned action at machine speed. The One Degree architecture, the one on the table in that room, is a claim about how to live in this era without gambling the franchise. It says the enterprise should stop treating software as the durable asset and start treating legitimacy as the durable asset. It says the edge can be disposable, but only if the core is durable. Identity and intent. Invariants and guards. Decision rights. Acceptable consequence. Causality. Then, and only then, does a disposable execution layer become safe.

This is not a branding exercise. It is an economic diagnosis. When intelligence gets cheap, the bill goes somewhere else. It goes to governance. It goes to enforcement. It goes to the hard work of making authority explicit, so the enterprise can move without supervision and without denial. When intelligence is abundant, legitimacy is the scarce currency. The false certainty. More intelligence means faster enterprises. The prevailing belief is easy to steel man because it is reasonable. If models can see more signals, summarize more data, draft more actions, and even generate software on demand, then the time between signal and action should compress. Meetings should shrink. Approval chains should relax. Decision velocity should rise because the evidence is clearer and the options are laid out. The problem is that the belief assumes intelligence is the bottleneck. In most enterprises, intelligence has not been the bottleneck for a long time. Authority has been the bottleneck. Permission has been the bottleneck. Trust has been the bottleneck. Most organizations already know what is wrong more often than they admit. What they lack is a legitimate path to change it without absorbing political cost, compliance risk, or personal

exposure. So, they buy time. They call it diligence. They call it alignment. They call it governance. Each word sounds responsible. Each step is defensible. The pattern becomes permanent architecture. Cheap intelligence does not remove that architecture. It loads it. When a system can generate a hundred recommendations where a team used to generate ten, the approval system does not become more efficient. It becomes congested. When a system can propose interventions continuously, the organization either slows down under the weight of reviewing them or it allows them to run and hopes the blast radius is small. “What would have to be true for this outcome to keep repeating.” That pivot line matters because it forces a clean audit of the operating reality. For a firm to keep receiving more insight while becoming no faster at action, at least one of these has to be true. Either the evidence that matters is missing at the point of decision, so humans have to fill gaps with meetings and email. Or authority is fragmented, so even correct recommendations cannot move without negotiation. Or consequence is unclear, so nobody wants to approve action without shared liability. Or trust is not enforceable, so every automation attempt becomes a risk transfer exercise. The core mistake is thinking intelligence is the limiter. In many places it is not. It is merely the loudest thing in the room. The hidden mechanism. We built observation machines, not intervention machines. The One Degree idea is blunt. It says modern enterprises leak margin and momentum in the seam between evidence and intervention. They observe at scale and act by exception. They produce insight and then ask humans to carry the permission burden of turning that insight into action. That design was tolerable when the world moved slower and when evidence arrived in batches. It is less tolerable when connectivity makes evidence continuous and models make recommendations continuous. The cadence mismatch becomes a cost center. The above illustration captures the mechanism in a way that is hard to unsee. The left side lists what must be durable. Identity and intent, the question of who is acting and on whose behalf. Invariants and guards, the constraints that exist because some outcomes cannot be traded away.

Semantics, because the system has to know what it is touching. Decision rights, because authority cannot be a rumor. Acceptable consequence, because governance is meaningless if it cannot name what loss is tolerable. Causality, because correlation is not enough when the system is allowed to intervene. The right side lists what can be disposable application surfaces that handle the messy realities that clog enterprises. Supplier expedite. Quality disposition. Maintenance triage. Planning exceptions. Compliance checks. These are not glamorous tasks, but they are where cost accumulates and where time bleeds away. In the center is the part most firms do not do, intervention filter. A ladder of legitimation that screens an action through evidence and permission, then raises or lowers what the system is allowed to do based on confidence and consequence. That center is where speed becomes faster incidents. If the firm does not build it, the firm will either choke on decisions or it will externalize risk. There is no third path. Speed without permission is not progress. It is accelerated fragility. The macro loop and the enterprise loop share the same flaw Citrini’s scenario is a macro story about reinforcing loops. The most important loop is not the one that ends in a stock chart. It is the one that turns local rationality into collective damage. Firms adopt automation to protect margins. Labor demand weakens. Household spending weakens. Revenue pressure rises. Firms automate more. The system eats itself through defensible decisions. Enterprises have a similar loop, and it arrives earlier than the macro loop because it does not require social consensus. It only requires internal incentives. A system generates more recommendations. Leaders feel pressure to “use the capability.” Teams attempt to automate. The governance and access model is not ready, so they compensate by adding review steps. Review steps increase meeting load. Meeting load slows execution. Slow execution increases operational noise. Noise increases the demand for more insight. More insight generates more recommendations. The loop tightens. The organization becomes a commentary engine. It can describe itself in detail while losing the ability to change itself in time. That is why the One Degree claim is not about models. It is about distance. It is about how many degrees of separation exist between evidence and intervention. It is about whether the enterprise has a legitimate path for action that does not require heroics and improvisation.

Cheap intelligence, combined with ubiquitous connectivity, collapses distance to evidence. It does not automatically collapse distance to legitimacy. That is the work. Access is the architecture of legitimacy, because access is the right to touch Most conversations about trust drift into vibes. They talk about confidence, comfort, adoption, culture. None of that is wrong. None of it is enough. Trust, in systems that act, is enforcement plus accountability. The core of legitimacy in a digital enterprise is access. The map of what an actor can touch. Data, workflows, money movement, physical control, customer commitments. If an agent cannot touch anything, it is a tool. If it can touch something, it is a risk bearer, and the enterprise has to treat it as such. Permission is the scoping mechanism. Permission answers the question the enterprise avoids because it is politically expensive. Under what conditions is this actor allowed to act, and what consequence is acceptable if it is wrong. Trust is the measurable confidence that permission will be enforced. Not described. Enforced. The diagram on the table says it plainly. Legitimacy gates allow only trustworthy action. It also says something else that most firms skip. Trust is not a vibe. It is an auditable chain of reasoning operating inside governance guardrails. That line matters because it rejects a common fantasy. The fantasy is that accuracy is enough. Accuracy is not asymmetric. A model that is usually right is still unacceptable if the rare wrong action carries intolerable consequence. This is why the durable core has to encode acceptable consequence. If the firm cannot name consequence, it cannot govern action. This is also why causal reasoning matters. When a system is allowed to intervene, correlation is an unreliable guide. It produces plausible explanations that can be dangerously confident. A causal model is not a luxury in an intervention system. It is the spine that allows the firm to learn from action rather than merely narrate it. Access decides what can be touched. Permission decides what can be done. The new software world. What is true about you, and what you make true. This is the missing section that turns the One Degree idea into a complete doctrine. The new software world is not defined by larger models. It is defined by a new relationship between truth, action, and software.

To build it, the enterprise has to separate two categories of truth that are currently mixed together so thoroughly that governance becomes theater. One category is what is true about you. Identity. Role. Delegation. Decision rights. Obligations. Risk posture. The provenance that says who is acting, on whose behalf, with what scope, and with what accountability. This is not a user profile. This is the durable core of legitimacy. The second category is what you make true. Approvals. Interventions. Transactions. State changes. Commitments. Actions that alter the world, and therefore alter responsibility. This is where agency lives, because agency is the capacity to shape outcomes. When firms confuse these categories, they make the most dangerous mistake available in an era of cheap intelligence. They treat capability as if it were authority. They treat a good suggestion as if it were permission. They treat a fluent explanation as if it were legitimacy. That mistake is how a loose word becomes an expensive incident. The durable core exists to prevent that confusion. It holds what is true about the actor, and enforces it as a system. It contains the access graph, the permission rules, the invariants, the audit chain, and the causal standards that decide what kind of evidence is required for what kind of action. Only then can the edge be disposable. Disposable does not mean ungoverned. It means replaceable. It means the enterprise can generate small execution surfaces for specific work, operate them inside enforced permission, discard them when context changes, and regenerate them without rewriting legitimacy every time. This is the economic reversal that matters. In the old world, software was durable and governance was a layer of policy and process around it. In the new world, governance is the durable asset, and software at the edge is the replaceable surface. The diagram names it as a loop. Generate. Learn. It is not poetic. It is a control cycle. Generate an execution surface. Learn from what happened. Improve the causal model. Tighten permission. Generate again.

That is how a firm avoids building a museum of legacy apps and a patchwork of “AI features” that nobody trusts. The app can be disposable. Legitimacy cannot. Reasoning at the edge is not a preference, it is a consequence problem There is a reason the One Degree architecture locates execution in a disposable edge. The edge is where reality changes. The edge is where context is richest. The edge is where latency stops being a nuisance and becomes a cost. In an observation world, latency produces annoyance and wasted time. In an intervention world, latency produces wrong action. If reasoning happens far from the point of work, two things happen that the enterprise mislabels as adoption issues. The evidence is stale. The model reasons over a world that has already changed, and then the humans in the loop spend their time reconciling a recommendation that was correct when it was generated but is wrong now. The intervention path becomes slow. The system produces a suggestion, the suggestion enters the approval maze, and by the time action occurs, the conditions that justified it have shifted. The organization then concludes that “agents are not ready,” when what is actually true is that the firm has not built the legitimacy path that allows action to occur in time. Edge reasoning is where legitimate speed becomes possible because the system can bind live evidence, local constraints, permission boundaries, and consequence in the same moment. That does not remove the need for central governance. It makes central governance real. It forces the core to declare what cannot be violated and what can be delegated. It forces the firm to state what “acceptable consequence” means, in operational language, not in policy prose. A fair counterargument. Not everything should move to the edge. There is a serious counterclaim, and it deserves clean treatment. Centralization exists for reasons that are not obsolete. Standardization matters. Audit matters. Consistency matters. In regulated environments, central control is often the only thing preventing local optimization from turning into systemic violation. In safety critical systems, the most dangerous thing is not slowness. The most dangerous thing is false confidence. There is also a second counterclaim, and it is coming from practitioners, not from pessimists. Some readers of the Citrini memo argue that the underlying AI capability assumptions are inflated, and that the near term reality is more constrained than the scenario implies.

Both counterclaims point to the same corrective. The answer is not to romanticize the edge. The answer is to separate governance from execution. A durable core does not decentralize legitimacy. It concentrates legitimacy, encodes it, and enforces it. The edge is not free to act. It is permitted to act. A disposable edge does not mean uncontrolled autonomy. It means replaceable execution surfaces that cannot exceed the authority granted by the core, and whose actions are logged, audited, and bounded by consequence. This is the reason “permission and trust” cannot be treated as cultural sentiment. They are system design. They are the architecture that makes either central control or local autonomy safe. If the firm cannot enforce permission, then edge execution is dangerous, and the counterargument wins. If the firm can enforce permission, then central governance and local action stop being opposites. They become complements. Two diagnostics that separate serious firms from fluent firms Does the enterprise have a written, enforceable map of decision rights tied to specific systems, specific actions, and specific consequences, or does it rely on titles, escalation habits, and informal authority that lives in calendars and proximity? When an agent proposes an intervention, can the firm prove what evidence the agent used, what causal claim it believed, what permission boundary it checked, and who accepted the consequence if it was wrong, or does the firm rely on a human signoff that functions as moral cover rather than an auditable chain? Those questions are not philosophical. They decide whether the enterprise can operate at machine speed without turning speed into loss. They also expose the real reason so many deployments stall. It is rarely because the models cannot draft a plan. It is because the firm cannot authorize action without improvising legitimacy. A falsifiable prediction that will feel obvious later By the time the world reaches the horizon Citrini chose, a large share of enterprise “automation” will not be measured by how many tasks a model can complete. It will be measured by how many decision rights an enterprise can delegate to a system without ad ding approvals. That prediction is falsifiable. It will be wrong if enterprises continue to scale by pouring more intelligence into the same approval architecture and still outperform peers on speed, cost, and

risk. It will be wrong if the dominant winners are firms that treat governance as a policy layer rather than as an enforced system. It will be right if the winners are the ones that treat access as legitimacy, permission as enforcement, and causal reasoning as the difference between intervention and coincidence. The reason it will feel obvious later is that this is how institutions always work. When capability becomes common, coordination becomes the advantage. When coordination becomes the advantage, authority design becomes the battlefield. The point of Citrini’s provocation, and the point of One Degree Citrini’s memo is a macro story about an economy getting weird because intelligence becomes abundant and adoption becomes reflexive. The details can be argued. The loop cannot be ignored. The One Degree architecture is an enterprise story about the same structural move. Evidence becomes continuous because connectivity is everywhere. Recommendations become continuous because intelligence is cheap. The approval maze becomes the limiter, unless legitimacy is encoded and enforced. Both stories end at the same place. Legitimacy is the scarce resource. The future does not belong to the firms that generate the most output. It belongs to the firms that can make output legitimate at speed. Not as rhetoric. As enforcement. As audit. As consequence. That is why the diagram on the table is not decorative. It is a demand for adult governance in a world where action can be generated faster than responsibility can be assigned. A disposable edge without a durable core is a multiplication engine for incidents. A durable core without a disposable edge is a museum. The One Degree world is the claim that there is a third path, and it is not a compromise. It is a reorder. Governance becomes the product. Execution becomes the replaceable surface. The bill is going to rise either way. The only choice is what it is paid in. Time, meetings, and delay. Or architecture, permission, and legitimate action. The question that remains is the one the room avoids because it is exposing.

Who, exactly, has the right to act in your enterprise, and how does the system prove it. The future belongs to systems that can act, and prove why they were allowed to.

References This piece draws on Citrini Research’s 2028 Global Intelligence Crisis memo as the macro provocation about reflexive adoption loops and legitimacy stress in an economy where intelligence is cheap. It treats the One Degree architecture and the durable core plus disposable edge model as the operational answer to that provocation, grounded in Michael Carroll’s One Degree doctrine on permission, trust, access as legitimacy, and governed edge execution, and it uses Carroll’s authored writing and provenance rules as a standard for separating observation from inference in claims that carry consequence. It leans on Judea Pearl and Dana Mackenzie’s work on the ladder of causation to justify why intervention systems require causal claims rather than correlation stories, and why counterfactual reasoning is the top rung when the system is allowed to change the world. It uses Ronald Coase’s 1937 account of transaction become the advantage when capability becomes common, and why cheap intelligence reprices the boundary between market and hierarchy. It draws on NIST’s AI Risk Management Framework to reinforce the governance, measurement, and accountability posture required when AI systems are permitted to touch consequential workflows rather than merely generate content. It also acknowledges practitioner counterevidence and skepticism expressed in the public discussion around the Citrini memo, because any serious operating thesis has to withstand the possibility that capability timelines are overstated even while the legitimacy problem remains real.