The thesis
AI accelerates individuals and fragments organisations.
The acceleration is real and per-person. The fragmentation is silent and collective — and it happens because every AI reads from a shared pile and writes into a private void.
The evidence
Everyone got faster. The organisation did not.
This is not a vendor argument. It is what the published research already says about what happens when AI meets work that is not fresh.
Developers with an AI pair-programmer finished a fresh task faster. The gain is real, and it is not in dispute.
Peng et al., 2023
The same tools, experienced developers, real issues in code they had known for years — while they believed they had been made 20% faster.
METR, 2025
For every 25% rise in AI adoption, teams reported feeling more productive while delivery throughput fell 1.5% and stability fell 7.2%.
DORA, 2024
Why it happens
AI moves the bottleneck. It doesn't remove it.
Most teams adopting AI get a burst, then a plateau. The limit is not the model's speed. It is trust: every AI output still has to be checked by the person accountable for it, and that person can only hold so much in their head at once. So AI makes individuals faster and teams no faster at all — the bottleneck moves from doing the work to reviewing it and remembering it. That plateau is where most AI programmes quietly stall.
What breaks the plateau
Make the output trustworthy by construction.
Two things have always capped what one person can do: what they can remember, and what they can personally re-check. Both move out of the individual’s head and into infrastructure the whole team relies on.
Cornerstone
What you no longer have to remember
Every decision, rule and rationale the organisation holds, distilled and cited back to source. The AI and the human both query current, provenanced truth instead of re-deriving it or guessing.
Coordinator
What you no longer have to re-check
Work is claimed, tracked and verified as it happens, so “done” is provable and parallel agents do not step on each other. The accountable person directs the work instead of re-verifying all of it.
In our own production use
One builder. Three commercial codebases. In parallel.
That is not reachable by typing faster. It is reachable only by not having to hold or re-verify everything personally. When the output can be trusted, the verification bottleneck goes, and the ceiling on how much one person can direct rises. The tools do not make people faster at the keyboard. They raise the ceiling on how much a single trusted operator can direct — which is the only lever that actually scales an AI-augmented organisation.
The missing half
The industry built the feed and never built the return.
Every time someone works with an AI, they hand it the organisation’s understanding of itself — what a customer means here, which of four systems called billing is real, why the migration stopped in 2023. Almost all of it comes out of their own head, because that is where it lives.
Then the session ends, and that understanding is destroyed. The next person rebuilds it from scratch. The colleague two desks away never had it.
Three years have gone into optimising the reading half — more context, bigger windows, better retrieval. The return path was never built. It is half a loop, shipped as though it were whole.
The consequence
Two colleagues, each with an AI, diverge inside a week into two versions of the same company — and neither can tell.
That is a silo: private knowledge, invisible to peers, lost when the holder leaves. With one new property. It assembles in an afternoon.
The scaling wall
Scaling AI hits a wall. This is why.
You deployed AI to do more with the same team, or the same with a smaller one. It worked on the first hundred documents. Then you pointed it at your company's files and knowledge — twenty years of documents, four systems called billing, the decision nobody wrote down — and cost climbed, accuracy dropped, and the productivity you planned for never arrived. That is the scaling wall, and it has two causes.
Cause one
Your knowledge was never built for AI to work from
SharePoint, file shares, wikis, email — built for people to file and find, not for a model to reason from. So the AI reads the whole archive, still drops the qualifier that mattered, and answers with the same confidence either way.
Cause two
Tokens are not getting cheaper fast enough
AI infrastructure costs are rising, and the hardware that brings the cost per token down at scale is years away. Every question drags more text through the model, so your token budget — not your ambition — sets the ceiling on how much your people can ask.
What follows
The gains have to come from the software
Waiting for cheaper compute is not a plan. A platform built for AI to work from gets the model to the right fact with a fraction of the tokens, and tells it when there is no fact to find. That is what Cornerstone is.
At enterprise scale
Finding the right document is not the same as being right.
This is the failure that does not show up in a demo, and the one that decides whether you can put AI in front of a regulated process. Both answers below came from the same question and the same documents.
One question, asked two ways
“Do we need in-region key management for the new analytics service we are standing up in the US?”
An AI reading your files
158,023 tokensYes. Your encryption policy requires customer data to be encrypted at rest with keys held in the same region as the data, rotated every 90 days. You will need in-region key management in place for the US deployment before it can go live.
Confidently wrong
It found the right document. The in-region key requirement is scoped to EU regions only — a qualifier further down the same policy than the clause it quoted. Nothing in the answer tells you an EU rule has just been applied to a US service.
Cornerstone
1,288 tokensNo. In-region key management applies to EU regions only. For US regions the standing requirement is encryption at rest with 90-day rotation, and no in-region key management is needed.
Why it holds
The scope is part of the fact, not a sentence buried near it. A rule that applies to the EU cannot come back as though it applied everywhere — along with who set it and when, so you can check.
123×
fewer tokens for the same question
100%
of required documents retrieved by file search
3 of 8
tasks it still got wrong
Measured across 2,201 public documents, plus a separate set of eight realistic briefs with deliberate traps in them. The failure shown is the one the run recorded: file search was handed the encryption policy in full and still applied an EU-only rule to a US service. No method in that run fabricated a citation — the reliability problem is not invented sources, it is confident answers with the qualifier dropped.
What we do about it
Build the return path.
What any AI learns about the business becomes structured, attributable knowledge the whole organisation owns — cited to what the company actually wrote, versioned as it changes. Every session repays what it borrowed.
Measured, not asserted
Seven methods. Same documents. Same model.
How much less you spend for each answer you can actually use. Query tokens only — the one-off cost of building the index is excluded, because on your own model it is not billed per token. Each bar is what that method costs you that Cornerstone does not.
- Cornerstone vs File searchReading whole documents99.7%
- Cornerstone vs Vector RAGSearching by meaning20.2%
- Cornerstone vs Hybrid + rerankKeywords + meaning, re-sorted18.2%
- Cornerstone vs Hybrid RAGKeywords + meaning · best alternative13.8%
Not on this measure: GraphRAG. A knowledge graph answers from its own graph rather than by handing back a source document, so “did it find the right document?” has no answer in these terms — and without that there is nothing to divide the spend by. It is on the other three measures, and on the trap corpus it captured 7 of 10 planted facts against Cornerstone’s 10.
13.8% cheaper per correct answer than the best alternative, 20.2% cheaper than searching by meaning, and 99.7% cheaper than reading whole documents.
How it wins
Per question these methods look level — Cornerstone is 1.5% cheaper than vector search and nobody should buy anything on that. The gap opens once you count only the questions that were actually answered. Vector search finds the right document 78.3% of the time, so a fifth of what it spends buys nothing; Cornerstone finds it 96.7% of the time. Same spend, more of it landing: 2,421 tokens per correct answer against 2,810 for the best alternative, 3,033 for vector search, and 861,225 for handing the AI whole documents to read. Measured directly rather than derived, the three-method report puts the vector gap wider still, at 26.0%.
Why it matters to you
This is the number that behaves like a bill. You are not buying questions, you are buying answers somebody can act on, and a method that is fractionally cheaper per question while missing one in five is charging you for the misses twice over — once in tokens, and again in the time it takes somebody to work out the answer was never there. One caveat stated plainly: building the index is a real one-off cost, and on a hosted model it is a real token bill. Run your own model, as Foundry customers do, and it is an overnight job on a GPU you already own — 3.8 hours for 2,201 documents — with no per-token charge at all. That is why it is excluded here, and it is the only thing excluded.
Knows when there is no answer — 41 of 49
Every other method scored no — and not narrowly. A search always has a closest match, even when nothing in your documents answers the question at all. So it hands back its best guesses, and the AI writes them up with exactly the same confidence it would use if the answer were really there. Nothing in what you read tells you which just happened.
The defining property is compounding.
Today each session is a write-off and tomorrow’s begins at zero. It does not have to. Each session can leave the next one better — across people, across time.