Where this essay begins. An earlier essay argued that the application layer of the enterprise is dissolving. Not collapsing, not being torn out, but quietly hollowing while its outward form persists, as the work surface moves to a new layer of agentic software above it. That is the event. This essay takes that event as given and asks the question that follows from it. If the old structure is dissolving, what is the enterprise becoming? The answer is not a repaired version of the old thing. It is a different kind of institution, built alongside the one that is dissolving, serving the same purpose through an entirely different medium. This essay is about that institution, why it has to be built new rather than renovated, and what it asks of the people running it.
Every large enterprise is now trying to become AI-native, and almost all of them are failing, because they have misunderstood what kind of change it is. They are treating it as a renovation of the institution they already have. It is not a renovation. It is the founding of a second institution, with a different unit of value, that becomes the new front of the enterprise, while the old institution does not close but is reconstituted beneath it as the system of record the new front depends on. The two run in parallel permanently, because that is the architecture. This essay offers a single frame for seeing it clearly. The frame is a library.
I. The split that should be a scandal
Begin with the pattern that should be unsettling more executives than it is. Across three years of effort, hundreds of billions of dollars of corporate spending, and a degree of executive consensus that borders on unanimous, enterprises have not converged. They have split. A small group of companies is pulling clearly ahead, capturing real and compounding financial value from artificial intelligence. A much larger group is spending heavily and getting motion without much result. And the distance between the two groups is not closing. It is widening.
The split shows up wherever anyone looks for it carefully. Boston Consulting Group has tracked enterprise readiness for several years, and segments a small leading group, on the order of one company in twenty, that captures a large share of the value, against a long tail that does not, with the gap between them widening rather than narrowing across successive years of the study. McKinsey's surveys of its own client base find that a great many organizations now use AI somewhere in the business, while only a small minority qualify as genuine high performers by the test that matters, which is real earnings rather than activity. Deloitte, surveying several thousand executives across two dozen countries, found enterprises sorting into rough thirds: roughly a third using AI to transform how work is actually done, roughly a third redesigning some key processes, and the rest using AI at the surface, with little real change underneath. These are survey findings and leader self-report, and they should be read as directional rather than audited. But they are independent of each other, they use different methods, and they point the same way. Most enterprises are spending real money and changing very little. A few are changing in kind. And the few are pulling away.
Now the detail that makes the split structural rather than embarrassing. The gap between the small group capturing value and everyone else is not closing. It is widening. If this were a normal technology adoption curve, the laggards would be catching up as the tools matured and cheapened. The opposite is happening. Whatever separates the leaders from the rest, it is not a head start the field is closing. It is something the few understood and the many did not, and the cost of not understanding it compounds every quarter.
If this were a normal adoption curve, the laggards would be catching up. Instead the gap is widening. That tells you the difference is not time. It is comprehension.
This essay is an attempt to name what the few understood. I want to state the answer plainly at the outset, because the rest of the essay is its defense. The companies pulling ahead understood that becoming AI-native is not a renovation of the enterprise they already had. It is the founding of a second enterprise. The companies falling behind are pouring money into upgrading the old institution, and the upgrade does not produce the new thing, because the new thing is not an upgrade. It is a different kind of institution, and you do not get it by improving the old one. You get it by building it.
To make that claim concrete enough to act on, I am going to spend the essay inside a single image. I have tried a number of frames for this transition, and most of them mislead in ways that have cost real leaders real time. The one that holds is the library. It is worth drawing it in full, because once it is fully drawn, almost every hard decision a leader faces becomes legible.
II. The library, fully drawn
Imagine you run one of the great public libraries. It has been a century in the making. Its purpose is straightforward: to give people access to knowledge for their own reasons, to learn, to work, to research, to be entertained, to decide. It serves all of them. The professional comes for the reference she needs that morning. The researcher comes to spend three years inside a single question. The student comes because someone has set him reading. The journalist comes for today's periodicals and will be back tomorrow for tomorrow's. The library is not valuable because of the books on its shelves. It is valuable because of the readers it serves. The books are the means. The readers are the point.
The institution is organized around one particular medium of knowledge. The unit of value is the fixed artifact: a book, written once, printed many times, identical for every reader, found through a catalogue, read from beginning to end, finished or abandoned. Everything about the institution follows from this. The acquisitions process, the catalogue, the conservation department, the reading rooms, the rules about who may borrow what, the very measure of success, all of it is shaped by the fact that the unit of value is the artifact. The institution is excellent at what it does. It has been excellent for a hundred years.
Now imagine the way people want knowledge begins to change. Not the knowledge itself; the underlying corpus of what is known and worth knowing is roughly the same. What changes is the experience people expect. They no longer want, as their default, to walk into a quiet room, work a card catalogue, find a book on a shelf, sit down, and read it through. They want to ask a question and have an answer come back shaped to that question. They want to choose whether the answer arrives as text, as audio, as a summary, as a deep dive. They want it pitched to their level of expertise, in their language, for the context they are asking from. They want to follow up. They want it now. They want it to remember what they asked yesterday. They want it to say when it does not know.
You are asked to stand up an institution that serves these readers. Not a new wing of the old library. A different kind of institution, delivering the same underlying purpose through a wholly different medium. Its unit of value is not the artifact. It is the interaction: the exchange, generated in the moment, shaped to who is asking and why, delivered in the form that serves them best, built on the assumption that they will follow up. Different skills. Different unit of value. Different definition of quality. Different relationship to the reader. The two institutions share a purpose. Almost everything else about them is different.
Here is the part that makes the situation hard, and it is the part most leaders get wrong. The old library does not close. Most of its readers still prefer it. They have spent decades learning to use it, and the fixed artifact and the quiet room and the linear read are not deficits to them, they are the experience they came for. The new institution, however well built, will feel foreign to them, and many will not switch. Meanwhile the readers arriving for the first time will mostly not come to the old library at all. The new institution is simply what they expect knowledge to feel like. They have never known anything else.
So the leadership has been handed a task with an unusual structure. They must keep the old library running for as long as it has readers. They must build the new institution alongside it. They must split investment between the two, hold the trust of two different populations at once, develop two different sets of skills, carry two definitions of quality, and report to their trustees against two different measures of success. They must do all of this knowing that for a long time the new institution will look small beside the old one, and that failure to invest in it will look like nothing at all, right up until the readers have quietly moved on and the old library is empty. There is no closing date. The two institutions run in parallel. The dual-running is not a phase. It is the work.
There is no closing date. The new institution is not a project that finishes. It is a second institution, and the running of both at once is the job from now on.
That is the situation every serious enterprise is now in. Not a migration. Not a transformation program with a target state and a final report. The standing-up of a different kind of institution, alongside the existing one, serving the same customers through a different kind of experience, and the running of both in parallel for as long as both have customers who prefer them. The word for this is not reconstruction. Reconstruction would mean building the old thing again. It is reconstitution: the same purpose, the same underlying corpus of value, reconstituted into an institution of a different kind.
III. Why a new institution, and not a renovation
The instinct of every well-run enterprise is to resist this. A new institution is expensive, frightening, and politically costly. Surely, the instinct says, we can get there from here. We have a good institution. We will modernize it. We will bring AI into the library.
This instinct is the single most reliable way to end up in the group that is falling behind, and it is worth being precise about why, because the reason is not obvious. The reason is not that the old institution is bad. It is that the old institution is excellent, and its excellence is the problem. Every part of it, the catalogue, the skills of its staff, the definition of quality, the measure of success, the layout of the rooms, has been refined for a century around the artifact. That refinement is real and it is deep. And it means that when you try to host the new, interaction-based service inside the old institution, the old institution's excellence quietly bends the new service back into the old shape. The new service gets catalogued. It gets measured by artifact-era metrics. It gets staffed by people whose deep skill is artifact production. It gets governed by rules written for borrowing books. None of this is stupidity. It is the gravitational pull of a well-built institution, and it is strong enough that the new thing, grown inside the old, comes out as a slightly better old thing.
This is what surface adoption actually is. The large group of enterprises that Deloitte finds using AI with little change to their processes did not fail to work hard. Many of them worked very hard. They brought AI into the library. They added the new tool to the old institution, and the old institution did what excellent old institutions do, which is to absorb the new tool into its existing shape and carry on. The result is an institution that has spent a great deal of money to become a marginally faster version of what it already was, while believing it has transformed.
There is a deeper version of the same mistake, and it is worth naming because the people who make it are often the most capable. They accept that the change is real and they decide to do the hard thing. They are going to rewire the institution from within. Rebuild the workflows, restructure the teams, re-skill the staff. And here is the subtle point. If they actually do that, all the way, honestly, they will look up at the end and discover that they have not rewired the old institution at all. They have built a new one. The workflows are not the old workflows repaired. They are different workflows. The teams are not the old teams retrained. They are differently shaped teams doing differently defined work. The thing they have built is not continuous with the thing they started with.
Which means that rewiring in place, done honestly and completely, produces exactly the same destination as deliberately founding a new institution. The two paths converge. So the only real question is whether you name the destination at the start or discover it at the end. And naming it at the start is strictly better, for a reason that is the whole argument of this section. If you tell yourself you are renovating, you will, every single day, make the small decision that protects the old thing. You will treat the existing process as the requirement. You will treat the current org chart as the constraint. You will treat the established metric as the target. Each of those small decisions is locally reasonable and collectively fatal, because together they bend the new institution back into the old shape before it is ever born. If instead you say, plainly, on day one, we are building a new institution here, nothing about the old one is automatically preserved, then every one of those small decisions is reopened. The renovation framing forecloses the choices that the new-institution framing keeps open. That is why the framing is not a matter of motivational language. It is the difference between the enterprises that pull ahead and the enterprises that do not.
Rewiring honestly and founding deliberately reach the same place. The only question is whether you name the destination on day one or discover it on the last. Naming it is strictly better.
Reimagine, then reengineer, then rewire, and in that order, because the order is the discipline. The failure mode is to start at rewiring, because rewiring feels like progress, it produces visible motion. But rewiring without the reimagining means you have changed the wiring of a process you never stopped to question, which is bolt-on wearing the costume of transformation. The reimagining has to come first. You decide what the institution is for and what it would look like if built today, from nothing, for the readers you actually have now. Then you engineer that. Then you wire it. An enterprise that starts at the wiring has smuggled the entire old institution back into the project as the thing being rewired, and it will get, predictably, a rewired old institution.
IV. The medium change, in detail
Everything in the library frame rests on one proposition, and the proposition deserves to be worked through carefully, because every other claim follows from it. The proposition is that the unit of value has changed. The old institution's unit of value is the artifact. The new institution's unit of value is the interaction.
An artifact is written or produced once, distributed many times, identical for every consumer, found through a catalogue, consumed in sequence, and then finished or abandoned. The digital enterprise is built entirely from artifacts. The report, the dashboard, the policy document, the contract, the case file, the customer record, each is produced once, consulted many times, the same for everyone who opens it, navigated through some descendant of the catalogue, a search bar, a folder tree, a saved query. The skills of the digital enterprise are the skills of producing good artifacts: writing the report, designing the dashboard, drafting the contract, maintaining the system of record. Productivity means the rate of artifact production. Quality means the artifact is accurate, well-built, and durable.
An interaction is something else entirely. It is generated in the moment, shaped to who is asking and why, delivered in whatever form serves them best, and built on the expectation that the asker will follow up. The AI-native enterprise, when it is working, is organized around interactions. The customer's conversation with the institution. The employee's answer to a question never asked in quite that way before. The decision support that responds to the specific case in front of it. The skills are the skills of designing interactions: understanding the asker, shaping the response, judging quality in a medium where every response is bespoke and then gone. Productivity means asks answered well. Quality means this asker, in this moment, was genuinely served. The artifacts still exist. The new institution still produces reports and records, and it still depends on a corpus of them. What changes is that the artifact is no longer what the customer comes for. The interaction is the front of the institution now. But an interaction generated in the moment and then gone cannot, by itself, be an institution, and the next section is about what it still needs underneath it.
Five things follow from this one shift, and each is a place where enterprises stumble because they have not named the shift directly.
The skills change in kind, not degree. The workforce of an institution built around artifacts and the workforce of an institution built around interactions are not the same workforce with different software. They are different workforces. This is why the reflexive response of treating AI as a training problem, sending the existing staff on a course, falls short. Training upgrades a workforce within its existing kind. The medium change asks for a different kind. When a recent survey of executives found that the most common talent response to AI was education, what it revealed was an industry diagnosing a change of kind as a change of degree.
Quality means something different, and the difference is hard to hold. An artifact is judged on whether it is accurate, well-made, authoritative. An interaction is judged on whether it served this particular asker's actual need in this particular moment. The same underlying knowledge can be perfectly delivered for one asker and badly delivered for another, and both judgments are correct at once. An institution that has spent a century building the muscle to judge artifact quality does not automatically have the muscle to judge interaction quality. It has to build it, deliberately, as a new capability.
The reader's relationship to the institution changes. In the old library the reader is a consumer of finished work. In the new institution the reader is a participant. What they ask shapes what they get. Their context shapes the response. Over time the institution comes to know who they are. That is a different relationship, and the privacy posture, the consent regime, the institutional ethics, all of it has to be designed for participation rather than consumption. It is not the old relationship with faster service. It is a new relationship.
The competitive ground moves. The old institution competed on the size of its collection, the quality of its artifacts, the reliability of its catalogue. The new institution competes on the quality of its interactions. And this is why a small, well-built new institution can beat a vast old library that has merely been fitted with AI tools. The readers go where the experience is better, not where the collection is larger. The widening gap between the leaders and the rest is this, measured: the ground moved, and only the institutions that understood the move are competing on the new ground at all.
The economics invert. The artifact institution had high fixed costs of production and low marginal costs of distribution; you paid to write the book, then printing and lending were cheap. The interaction institution has low fixed costs of artifact production, since the underlying knowledge is largely already there, and high marginal costs of interaction, since every response consumes computation and every conversation is bespoke. A leader who treats AI as a fixed-cost investment to be made once and amortized is using the wrong economic model, and the wrong economic model will produce the wrong decision at every budget cycle.
The old institution's unit of value is the artifact. The new institution's unit of value is the interaction. Everything that is hard about the transition is downstream of this one sentence.
V. Why the library cannot close
There is a temptation, once the medium change is clear, to assume the old institution is simply on its way out. The interaction is the future, the artifact is the past, and the library survives only as a courtesy to the readers who have not yet adjusted. Hold the new institution steady, wait, and one day the last artifact-preferring reader is gone and the old library can finally close.
This is wrong, and it is wrong in a way that matters, because it leads a leader to underinvest in the one part of the institution that everything else depends on. The old library does not survive as a courtesy. It survives because the new institution cannot exist without it. And the reason is in the nature of an interaction itself.
An interaction is generated in the moment and then it is gone. That is its strength; it is shaped to one asker, one context, one need. It is also, by itself, a kind of amnesia. An interaction captures nothing. It records nothing. It leaves no corpus behind. If an enterprise were nothing but interactions, it would have no memory, nothing to generate the next answer from, nothing to check an answer against, nothing that persists between one conversation and the next. The interaction layer, for all that the customer experiences it as the whole institution, is standing on something. It is standing on a system of record: a maintained, governed, persistent corpus of what is true, what was decided, what happened, what is known. The library is that system of record. It is not the old medium waiting to die. It is the foundation the new medium runs on.
An interaction captures nothing and records nothing. An enterprise that was only interactions would have no memory. The library is the memory.
This reframes the two institutions, and the reframe is important enough to state precisely. They are not two peers running side by side until one of them wins. They are a stack. The interaction institution is the front: it is what the customer comes to, the surface where the value is delivered. The corpus institution is the back: it is where information is captured, validated, recorded, and kept. The front cannot stand without the back. Dual-running is not a tense coexistence with a hidden finish line. It is the architecture. The library cannot close because the thing that replaced it is built on top of it.
Notice what this does to the old institution's century of accumulated skill. The earlier sections of this essay treated that skill with suspicion, as a gravitational pull that bends the new service back into the old shape, and as a warning that remains true. But the skill is not waste. The work the great library always did, the documenting, the cataloguing, the validating, the establishing of provenance, the judgment of whether a source is reputable and an article genuine, is precisely the work the back of the new institution requires. The skill is not obsolete. It is relocated. It moves down the stack, from a front office where it used to face the reader directly, to a back office where it now faces the interaction layer and feeds it. The librarian's craft does not disappear in the AI-native enterprise. It becomes foundational, and it stops being visible to the customer, which is a different thing from becoming worthless.
And here is the part that turns the whole intuition around. You might expect that in an age of generative abundance, when machines can produce plausible text on any subject at no cost, the maintained corpus would matter less. The opposite is true. The world is now flooded with generated content: synthetic text, machine-made images, plausible and unsourced and unverified material produced at a volume no prior era could have imagined. Some of it is slop and some of it is genuinely good, but very little of it arrives with its provenance attached. Information has stopped being scarce. What has become scarce, and therefore valuable, is information you can trust: validated, sourced, genuine, maintained, vouched for. An interaction layer is only as good as what it can reach for, and a good interaction layer has to reach for something it can trust. That trusted thing has to be built and maintained by someone doing the patient back-office work of curation and validation. The flood of AI content does not shrink the need for the library. It is the strongest argument for the library that has ever existed.
There is one more reason the library endures, and it is about the world beyond the single enterprise. The institution is not only serving its own readers. It is also a destination where others come to deposit and share information. Publishers still publish. People and organizations still produce records, filings, research, accounts of what happened. The global marketplace of information is still, for the most part, a marketplace of artifacts produced by humans and human institutions. It may one day become natively agentic, an interaction-to-interaction world with no artifacts in between, and that is worth watching, but it is not close, and an enterprise cannot build for a world that does not exist yet. For as long as the wider world supplies information in the form of artifacts, the enterprise needs an institution that can receive them, validate them, and hold them. The library is that institution. It is not a relic. It is the enterprise's connection to a world that still runs on records.
So when this essay says there is no closing date, it is no longer making a claim about the patience of legacy readers. It is making a claim about architecture. The library cannot close because it is load-bearing. The interaction is the front; the corpus is the foundation; and a foundation is not a phase.
VI. Dual-running is the permanent condition
The previous section established the deepest reason the two institutions run in parallel: the corpus is the foundation the interaction layer stands on, and a foundation does not get retired. But there is a second reason, and it operates on a faster clock, so a leader has to plan for it directly. It is the readers.
The old institution's readers are still there. Most still prefer the artifact-based experience for at least some of what they need. They are paying customers, they are often the most profitable segment, they are politically organized, and they cannot be ordered into a medium they did not choose. The new institution's readers are growing quickly but are not yet, in most enterprises, the majority. Force the old readers into the new experience before they are ready and you get the most familiar failure in the public record, the premature switchover that has to be loudly reversed. Close the old front office early and you lose readers who do not come back. Refuse to build the new one and you lose the readers who never arrive. Both errors are visible, repeatedly, in the data. The only stable posture is to run both, deliberately, and let readers cross at the pace they choose. So the enterprise runs two institutions for two reasons at once: the corpus must exist because the interaction layer is built on it, and the old front office must keep running because its readers have not all crossed. The first reason is permanent and architectural. The second is long but not unending. Together they put dual-running beyond any planning horizon a leader actually operates on.
This has consequences that the usual transformation language is not built to carry, and they are worth stating one at a time, because each is a decision a real leader has to make.
Capital is split between two institutions, not allocated to one program. The old institution generates most of today's revenue and has to be maintained to the standard its readers expect. The new institution will generate most of tomorrow's revenue and has to be built at a pace the leadership can defend to the people funding it out of the returns of the old. That is a portfolio decision between two institutions with different time horizons and different return profiles. It is not a budget line for a transformation initiative, and calling it one produces chronic underfunding of the new institution, because a budget line gets cut when this quarter is hard and a second institution does not.
The workforce has to be built for both. The old institution's staff are needed for as long as it has readers. The new institution's staff have to be developed from a different base of skill. And the movement of people between the two has to be planned, deliberately, because the two workforces are not interchangeable and the people crossing from one to the other are making a real transition that the enterprise either supports or fumbles. This is the honest center of the human cost, and it should not be smoothed over. Becoming AI-native moves people across a threshold from one kind of work to another. Some make the crossing into the new institution. Some remain, valuably, in the old one for as long as it runs. Some find that the work they did is now done differently and that the institution owes them a real answer about what comes next. A leader who pretends this is only upskilling is not being kind. They are postponing the moment of honesty and making it more brutal when it comes. The change-management craft the enterprise already has, the disciplined sequence of building awareness, then desire, then knowledge, then ability, is the right craft for this. It is simply being asked to do something heavier than it has done before: not move people to a new tool, but carry them across to a new institution.
The board has to be shown both. The old institution's metrics are the ones the board knows: revenue, margin, cost ratios, retention. The new institution's metrics are different in kind: interaction quality, trust earned, customers served better than the old institution could have served them, leading indicators of revenue that has not arrived yet. Report only the old metrics and the new institution looks like a cost center that should be cut. Report only the new ones and the leadership looks like it has abandoned the business that pays the bills. The frame that holds is the portfolio: two institutions, each reported against its own measure, with the leadership accountable for the whole.
Even the regulator has to be met twice. The old institution sits inside a regulatory perimeter built around the artifact: model risk rules for credit decisions, audit trails for transactions, content standards for what is published. The new institution operates in a regulatory environment still being written. The leader has to hold both compliance postures inside one organization at the same time. This is genuinely difficult. It is also simply the work, and the work does not get less real by being difficult.
VII. What the frame tells a leader to do on Monday
A frame earns its keep only if it makes the next decision clearer. The library frame does, and the guidance it gives is specific enough to act on this quarter. Six things follow.
Fund the spine before the catalogue. The new institution needs a foundation before it needs visible services: the layer that lets agents act, that holds identity for both people and machines, that carries the semantic data and its access controls, that records what was done and on whose authority, that governs what an agent is permitted to do under what conditions. This foundation is unglamorous and it produces no headline on its own, and so it is exactly what an enterprise chasing visible wins underbuilds. The result is the most common technical failure in the data: enterprises running large numbers of agents while almost none of them can govern those agents, because they built services on a foundation they never poured. Build the foundation first. The services are downstream of it. This foundation, and the operating system it amounts to, is large enough and important enough to be its own subject, and it is the subject of the next essay in this sequence. For this essay it is enough to say: it comes first, and it is permanent.
Start where the new medium is most obviously better. Serve first the readers whose need for an interaction is most concrete and whose value is easiest to measure. In most enterprises that means the back-office work where the return is well documented: the financial close, contract review, technology service management, high-volume customer service. Pair that with one or two customer-facing domains where the case for the new institution is visible to the outside world. The reverse order, attempting the deep customer-facing reimagination before any back-office win has established credibility, is one of the most reliable ways to lose the organization's confidence before the institution is real.
Reimagine the workflow from a blank sheet, and never measure it by adoption. Each domain the new institution takes on should be rebuilt by asking what the process would be if designed today, not how the existing process could be made faster. The accountable owner should be the business executive who owns the outcome, not the technology function. And the measure of success should be a business result, cycle time, throughput, error rate, a customer outcome, never a technology metric like seats filled or queries run. Counting licenses issued and weekly active users is the new institution's version of counting books on the shelf while the reading room sits empty.
Treat fluency as institutional investment, not remedial training. The workforce of the new institution has to be genuinely capable in the new medium, and that capability is built, not assumed. But it is not built by a training course bolted onto the side. The enterprises that have done this well, the ones whose programs ran into thousands of people and tens of thousands of genuine hours, treated fluency as a flagship investment in the institution's future capacity and reported it that way. The leading indicators are not course completions. They are depth of use, the production of reusable assets, the emergence of people fluent in both the domain and the new medium. Fluency is one leg of the institution. It is not the institution, and it is not a substitute for the structural work, but the structural work fails without it, because a workforce that is not fluent routes around the sanctioned institution and rebuilds the old one in the shadows.
Measure the new institution in readers, not artifacts. The metrics that matter are customers served better than the old institution could have served them, decisions made faster against a real counterfactual, errors avoided, trust earned where trust could have been lost. The enterprises that measure value honestly do it against a counterfactual baseline, a genuine comparison with what would have happened without the new institution. The enterprises that measure it dishonestly quote a headline percentage with no method behind it. By now that second kind of number should be easy to recognize. It is a projection wearing the costume of a measurement.
Stop running a program. Run a portfolio. This is the reframe that carries all the others. A leader running a transformation program has a target state and a closing date and a final report. A leader running a portfolio of two institutions has a permanent responsibility for both and is measured on whether the enterprise, a decade from now, is serving its customers well. The second is the truthful description. The board reporting, the executive incentives, the succession planning, the strategic plan, all of it should be built for the portfolio. The transformation program, as a category, should be retired. It describes a thing that is not happening.
A program has a closing date. An institution does not. The most important reframe a leader can make is from running a program to running a portfolio of two institutions.
VIII. What would make this frame wrong
A frame that cannot be wrong is not a frame, it is a comfort. The library frame makes claims that can fail, and a leader leaning on it should know where the failure points are.
• The medium change might not be the deepest change. I have argued that the move from artifact to interaction is the unit of analysis that matters most. It is possible that the deeper change is agentic autonomy specifically, the delegation of authority to machine principals, rather than interaction more broadly. If that is so, a frame built around delegated authority and machine accountability would serve a leader better than one built around the reader's experience. The current evidence supports the interaction framing, but this is the most credible challenger and it should be watched. It is also, not coincidentally, the subject the next essay takes up.
• The dual-running window might be shorter than the frame assumes. The whole portfolio posture rests on the old institution keeping a material population of readers for a long time. That has held so far. It might not hold. If a new generation of customers refuses the old institution outright, and refuses fast, the parallel-running window could collapse from decades to a few years, and a frame built for patient dual-running would leave a leader moving too slowly. The thing to watch is the rate of customer migration over the next three years. If it accelerates sharply, the frame needs revisiting.
• In-place transformation might turn out to be real. I have argued that the new institution must be built alongside the old, because the old institution's excellence bends any in-house renovation back into the old shape. If the record comes to show enterprises that genuinely became the new institution by internal evolution alone, with no parallel construction, then the dual-institution claim is too strong. So far the evidence does not show this; every credibly transformed incumbent in the public record built the new alongside the old. But it is a falsifiable claim, and the honest move is to say so and watch for the counter-example.
• The frame may be overfitted to large, regulated incumbents. The library frame is built for the leader of a substantial institution with an installed base, a regulated perimeter, and a balance sheet to protect. For a small enterprise, or a digital-native firm already partly built around interactions, or a sector with a weak regulatory perimeter, the dual-running constraint may be much looser than the frame implies, and a more aggressive single-institution build may be correct. The frame is a tool for a particular and common situation. It is not a law.
My honest assessment is that the first of these is the one most likely to matter, because it is less a flaw in the frame than a pointer to what the frame does not yet cover. The library frame describes the institution the enterprise is becoming. It does not fully describe the machinery that institution runs on. That machinery, the operating system of the new enterprise, the thing that holds a network of agents together into something that can actually be called an institution, is the unfinished business of this essay. It is where the argument goes next.
IX. The chief librarian
Let me end where the frame leaves the person actually carrying it. A leader who has accepted the library frame is no longer running a company and a technology program inside it. They are the chief librarian of two institutions: an old one that must be kept excellent for as long as it has readers, and a new one that must be brought into being alongside it and will outlast the leader's own tenure.
That is a heavier description of the job than the one most leaders signed up for, and I do not want to soften it. The work is not to bring AI into the library. The work is to found a second institution, of a different kind, serving the same readers through a different kind of experience, and to run both at once for as long as both have readers who prefer them. It has no closing date. It will not resolve into a tidy target state. It asks a leader to hold two definitions of quality, two workforces, two regulatory postures, and two measures of success in mind at the same time, and to be judged on the whole.
But I want to be equally clear that this is not a counsel of despair, because the same frame that makes the job sound heavier also makes it clearer than it was. The enterprises that are pulling ahead are not there because they bought a better model or hired a better vendor. The model is a commodity; that is what a substrate is. They are there because they understood what kind of change this is. They stopped renovating. They named the new institution as a new institution on the first day, and then they did the patient, unglamorous, well-built work of founding it: the foundation before the services, the blank-sheet workflow, the fluency treated as real investment, the honest metric, the portfolio held instead of the program run. None of that is a secret. None of it depends on privileged technology. It depends on seeing the situation correctly and then having the institutional courage to act on what you see.
And that is, in the end, the good news hiding inside the divergence. The barrier is not capability. The frontier models are available to everyone, the patterns are visible in the public record, the playbook is not hidden. The barrier is comprehension and courage, the willingness to see that the old institution, however excellent, is not the thing being upgraded, and the willingness to found the new one honestly while the old one still pays the bills. Comprehension and courage are hard. But unlike a frontier model or a rare technical team, they are not things a competitor can simply buy. They are available to any leader willing to look at the situation without flinching. The dissolution of the old structure is not in doubt. What an enterprise becomes on the other side of it is still, genuinely, a choice. This essay has been an argument about how to see the choice clearly. The making of it is the work, and the work is now.
A note on sources
This essay draws on the public research record on enterprise AI as of May 2026, including the Boston Consulting Group's multi-year research on the widening gap between AI leaders and the rest of the field, McKinsey's State of AI work and the second edition of Rewired, Deloitte's State of AI in the Enterprise survey of several thousand leaders across two dozen countries, the Stanford Human-Centered AI Index, and the World Economic Forum's 2026 work on organizational transformation. The destination-state description of the queryable, agent-addressable company draws on the Y Combinator AI-native material articulated in early 2026. The named enterprise cases, JPMorgan Chase, DBS Bank, Moderna, Walmart, Lloyds Banking Group, AT&T, and Vodafone, are drawn from public statements and case studies. The leader-and-laggard segmentation and the tiering of enterprises by depth of transformation come from leader self-report in industry surveys; they should be read as directional rather than audited, and they are used here only because several independent surveys, using different methods, point the same way. The library frame, the artifact-to-interaction argument, the reconstitution framing, and the conclusions are the author's own. The direction of travel is, in my view, hard to ignore. The pace, and the identity of the eventual winners, remain genuinely uncertain.