Lexicon
The words we use
And exactly what we mean by them.
If a term is doing real work in an argument, you should be able to check what it means rather than infer it from context.
This brief uses a small, deliberate vocabulary. Some of it is ordinary economics used precisely. Some comes from Who Holds the Pen?, and those entries are marked. Nothing here is jargon for its own sake: each term exists because the plain-English version takes a paragraph and we would rather spend those words on evidence.
Part 1
How we judge a claim
These govern what can appear in an issue and how it is labeled. They are publication rules, not opinions.
Above the cut
OursWhat would change a decision, as opposed to what merely happened. Most AI news is real and still below the cut, because knowing it would not alter what a reader does on Monday.
Primary, Corroborated, Reported
OursThe three labels every event in an issue carries. Primary means the lab, paper, regulator, or filing said it first-hand. Corroborated means an independent source confirmed it. Reported means someone said it and we have not been able to confirm it, so the wording stays hedged and attributed.
Our reading of what an event means is labeled separately as our Analysis. Inference never inherits a primary label. An event can be Primary while the conclusion drawn from it is contested.
The link-and-claim standard
OursNo link ships unverified. Every external URL is opened before send and confirmed to load and to contain the specific fact cited, not merely to be about the topic. The check runs as a mechanical gate that blocks the issue, and we link the deepest primary artifact rather than coverage about it. Aggregators and search-results pages are never cited.
The measurement gap
OursA claim of AI value made without a number a reader could underwrite. It is the most common shape of AI announcement: real activity, real spend, and nothing an outsider could check or a CFO could book.
Part 2
The two-step value test
Most arguments about AI value collapse two separate questions into one. We keep them apart, because a company can pass the first and fail the second, and that failure is invisible if you only ask whether the technology worked.
- Was value actually created? Measured as AI Yield: release plus expansion, netted against the whole AI investment, both sides read against a baseline recorded before the change. Freed hours are capacity, not money. Capacity becomes a saving only when a position, contract, or licence actually stops. Fails when: the claim is activity, adoption, freed time, or a pilot count rather than a recognised result.
- Does the creator keep it? Measured as rent: excess returns that persist after competitors deploy the same capability. This cannot be tested until later, so it has to be argued before the capital is committed. Fails when: the gain is real but every rival gets it too, and it lands with customers as lower prices rather than with the company as margin.
Both must pass before we describe something as durable advantage. Step one alone is an efficiency story. Step two alone is a strategy assertion with nothing under it. The Margin-Proof Tracker exists to run both against named claims, in public, over time.
Part 3
Was value created?
AI Yield
BookThe account for what an AI investment actually produced, and where the value went. It answers two things at once: what value AI created, and who partakes in it.
Gross AI Yield = release + expansion. The two can be added only because both are money against the same baseline, for the same operation, in the same period. Net AI Yield = Gross AI Yield less the whole AI investment assigned to that same operation and period.
The whole AI investment is not the model bill. It is technology and compute, data, integration, evaluation, controls, change effort, and transition.
AI Yield is a periodic enterprise account in money and native units, never a percentage return. If you need a ratio, divide Net AI Yield by the investment. A negative first statement is information, not failure: it says the investment has not produced a recognised return yet.
Release and expansion
BookThe two halves of the yield, and they arrive on different clocks. Release is cost that stopped: a position leaves the plan, a vacancy stays unfilled, a contract ends. It lands in next quarter's accounts and it is easy to prove. Expansion is a bet: the company keeps the capacity, points it at new or better work, and waits to see whether customers reward it. It may arrive late, or not at all.
Which one produced a company's number tells you more than the number does. A yield built almost entirely on release is a cost story. Expansion carries more uncertainty even when it creates the more valuable future.
Capacity is not a saving
BookA freed hour is capacity, not cash. When AI improves existing work, management then chooses: release the capacity, so the position, contract, or licence actually stops, or redeploy it, giving the time another job.
If nobody decides, the freed hours stay on payroll while the target quietly rises. That capacity is unresolved. It never becomes a saving by default. A company announcing that AI freed a third of its agents' time has reported capacity, not value, and we say so.
Recorded and observed
BookNot every part of the account is knowable the same way. Investment, capacity choices, and release can be recorded: a company knows what it spent, what it decided, and which costs stopped. Expansion and the overall result can only be observed against a baseline, because demand, pricing, competitors, and the wider market move at the same time. Attribution to AI is then a stated judgment, not a measurement.
The baseline is what the operation was, recorded while the old operation still existed. It is not a story about what would have happened without AI. An audit three years later finds vanished contracts, absorbed hours, and explanations written after everyone knew the ending.
Distribution
BookThe other half of the question, and the half a single financial number hides. Who received the gain, who carried the cost, and how fast did either arrive. When release drives most of a yield, the money tends to reach the enterprise, its owners, and the leaders rewarded for delivering it.
Customers benefit only if the company decides to lower prices or improve service. Pass-through is a decision, not a trickle. Workers receive a share only if someone designates one. If nobody names another destination, the result stays in earnings.
The financial number can improve while the human result gets worse, on the same page, in the same period. One number cannot be the answer, so the people record travels with it: roles ended, people redeployed, transition support, service quality, time.
Shipped is not value
OursA pilot running in production with no effect on the P&L. Deployment is evidence that something works, not evidence that it paid.
The trust wall
OursProgress gated by reliability and control rather than by capability. When a system is good enough to be useful but not dependable enough to be relied on unsupervised, the binding constraint is trust, and more capability does not move it.
Part 4
Who keeps it?
This is the standing question of the brief. Reliability and control are table stakes. Defensibility is the strategy.
Rent
OursExcess returns that persist after competition catches up. The everyday sense of the word is irrelevant here; this is the economic sense. The test is whether the underlying advantage is excludable, meaning rivals cannot simply acquire it, rather than whether it is scarce today.
Competed-away advantage
OursA real AI gain that never reaches the P&L because every rival deploys the same capability and the benefit passes through to customers. The technology worked exactly as promised and the company is no better off than before.
Table stakes, not a moat
OursAI spending undertaken to stay in the game rather than to get ahead of it. Necessary, unavoidable, and not a source of advantage. Where durable advantage exists, it usually lives in scarce complementary assets a rival cannot copy, such as proprietary data, distribution, regulatory position, or workflow lock-in, rather than in the model itself.
Test reliability, argue defensibility, judge it later
OursThe order diligence has to run in. Verify that a system works and is controlled before scaling it, because that is testable now. Reason about whether the advantage survives competition before committing capital, because it cannot be tested until later. Then judge the result against what was argued.
Part 5
How the work gets built
These describe the operating side. They come from Who Holds the Pen? and are used here with the same meaning. The Field Guide covers the individual-level ones in depth.
Synthetic Team
BookA human-led, reconfigurable way of organizing people, AI, software, data, rules, tools, memory, checks, and judgment around a responsibility or mission. It may be standing or temporary, and it can be nested inside another.
It is not several AI personas sitting side by side. It is a picture of the work rather than a headcount of software: the roles the work actually needs, each built with the simplest thing that does its job reliably, whether that is a separate agent, an instruction, a rule, or a person.
The word team applies when a person is authoring and managing an organization of work, not merely requesting output. Responsibilities, handoffs, checks, and visible human decisions are the signals. Humans keep purpose, authority, judgment, and accountability. Synthetic roles hold no pen.
The team cannot grade its own homework. An AI that writes the work and then judges its own draft is author and referee at once, and will tend to bless what it just produced. At least one check has to be independent of the seat that produced the work. The team prepares. The human owns.
The Delegation Tax
BookThe attention it costs to hand work to AI responsibly: framing the task, assembling context, steering, inspecting the return, correcting it, and being able to explain why the result deserves confidence. The handoff is cheap. Accountability is not. When the tax is not paid by the sender, it is simply transferred to the recipient.
The Verification Boundary
BookThe point at which work has earned its next level of reliance. Work crosses it by one of three routes: a credible person can grade it, evidence or a test can expose the important failure, or reality can answer while the stakes stay small and reversible. Absent all three, the output may still be useful for exploration, but it has not earned the status of an answer.
The Personal Ceiling
BookThe point where further gains stop depending on how well one person uses AI and start depending on whether the work around that person changes. It is the signal that the next problem is shared context, workflow, standards, review, decision rights, or team design. My work gets better before our work gets different.
The wisdom gap
BookAI is smart but far from wise. Left unsupervised it invents facts, agrees with a false premise, drops the detail buried on page forty, and quietly applies an incomplete standard, fluently and at scale. A sharper model makes the fluent answer more fluent, not more accountable, which is why quality has to be designed for rather than waited out.
These have a longer treatment
The Field Guide works through the individual-level ideas with worked examples: how to brief a task, how to recognise the failures that hide under a polished answer, and how to decide what has earned your trust.
Read the Field Guide →