Registry objects

Appendix

2 invoked

The book rests on a formal registry of theorems, lemmas and propositions. The registry justifies the book; it does not organize it. Listed here are only the objects a published chapter actually invokes, each with the wording that chapter uses. The full registry, and the verbatim statements, are reproduced in the print appendix.

THM-004

Once a deployment reaches scale, economic control requires a governing apparatus. Diligence from the people running the deployment is no longer enough.

First used in Chapter 2
THM-009

deployed AI is a resource-consuming operating activity, not merely software access

First used in Chapter 1

Continuity

Promises between chapters

14 open

A chapter that says a later chapter will do something has made a promise. Each is logged when the promising chapter locks and marked paid when the promised chapter locks.

Chapter 1 to Chapter 2 paid

This is the first chapter; problem sets begin reaching back to earlier chapters in Chapter 2.
Chapter 1 to Chapter 3 paid

Each of these subjects has its own purpose and literature, and Chapter 3 explains where each ends and AI Operations Management begins.
Chapter 1 to Chapter 4 open

Chapter 4 examines these instruments in detail.
Chapter 1 to Chapter 6 open

It returns in Chapter 6 as the book’s anchor case on realized value.
Chapter 1 to Chapter 14 open

Chapter 14 distinguishes the subject of this book from these neighboring disciplines.
Chapter 2 to Chapter 1 paid

4 Chapter 1 argued that a flat price relocates the meter to the provider rather than abolishing it.
Chapter 2 to Chapter 1 paid

Chapter 1 defined its basic unit: the consumption event, a single use of an AI system that consumes metered computing resources.
Chapter 2 to Chapter 1 paid

Chapter 1 described the problem as a category error, and Chapter 3 names the discipline that resolves it.
Chapter 2 to Chapter 1 paid

Chapter 1 established that the provider always holds a meter, because the provider must bill and must manage its own capacity.
Chapter 2 to Chapter 1 paid

Interleaving: question 4 and problem P2 require Chapter 1’s results.
Chapter 2 to Chapter 1 paid

Public reporting does not establish whether Uber made the category error described in Chapter 1 or understood the cost model but failed to carry that understanding into its forecast.
Chapter 2 to Chapter 1 paid

Uber’s experience makes the problem from Chapter 1 concrete.
Chapter 2 to Chapter 3 paid

As Chapter 3 explains, the theorem formalizes the economic consequence of the third flow’s asymmetry; it does not establish the taxonomy itself.
Chapter 2 to Chapter 3 paid

Chapter 1 described the problem as a category error, and Chapter 3 names the discipline that resolves it.
Chapter 2 to Chapter 8 open

Chapter 8 builds the record flow, and Chapter 10 turns that record into a budget.
Chapter 2 to Chapter 8 open

It returns in Chapter 8, which builds the record flow that organizations are structurally most likely to skip.
Chapter 2 to Chapter 10 open

Chapter 8 builds the record flow, and Chapter 10 turns that record into a budget.
Chapter 3 to Chapter 1 paid

Chapter 1 described the problem as a category error.
Chapter 3 to Chapter 1 paid

Chapter 1 stated the conditions under which deployed AI is a resource the organization consumes.
Chapter 3 to Chapter 1 paid

First, apply Chapter 1’s consumption-event inventory.
Chapter 3 to Chapter 1 paid

One might treat Chapter 1’s Cursor licenses as a fixed software expense and the other as metered consumption.
Chapter 3 to Chapter 2 paid

4 Chapter 2 diagnosed a deployment through its three flows.
Chapter 3 to Chapter 2 paid

Chapter 2 stated the conditions under which a scaled deployment cannot be controlled without a governing apparatus.
Chapter 3 to Chapter 2 paid

Second, apply Chapter 2’s three-flow mapping.
Chapter 3 to Chapter 2 paid

The second function is planning and budgeting, whose absence proved costly in Chapter 2’s opening case.
Chapter 3 to Chapter 2 paid

The third function, metering and attribution, builds what Chapter 2 called the record flow.
Chapter 3 to Chapter 6 open

The case returns in Chapter 6.
Chapter 3 to Chapter 7 open

“Are you paying for capability you do not need, or starving work that needs more?” This is the sourcing question, answered in Chapter 7.
Chapter 3 to Chapter 10 open

“What do you expect the AI flow to consume next period, and how will you know when it deviates?” This is the planning and budgeting question, answered in Chapter 10.
Chapter 3 to Chapter 11 open

“When capacity is constrained, who decides what runs first, and by what rule?” This is the allocation question, answered in Chapter 11.
Chapter 3 to Chapter 12 open

“Where, exactly, does this AI flow pay for itself, and who is on the hook for knowing?” This is the value boundary question, answered in Chapter 12.
Chapter 3 to Chapter 14 open

Chapter 14 explains how FinOps and that practice divide the work.
Chapter 3 to Chapter 14 open

Chapter 14 explains how the two divide the work.
Chapter 3 to Chapter 1 paid

3.3 Where the discipline ends Chapter 1 set aside three related subjects: how models work, prompt engineering, and finding uses for AI.
Chapter 3 to Chapter 1 paid

Chapter 1’s Cursor licenses show this check in practice.
Chapter 3 to Chapter 1 paid

Chapter 1’s result does not say that every use of AI is consumption.
Chapter 3 to Chapter 1 paid

It builds on Part I’s two earlier methods: Chapter 1’s consumption-event inventory lists what a deployment consumes, and Chapter 2’s three-flow mapping shows which flows are managed.
Chapter 3 to Chapter 1 paid

[truell-2025-pricing] The Cursor post describing the plan change of June 16, 2025, as cited in Chapter 1.
Chapter 3 to Chapter 2 paid

Chapter 2’s panel, THM-004, shows what such a result settles and what it leaves open.
Chapter 3 to Chapter 2 paid

Interleaving: question 4 requires Chapter 2’s three flows, problems P1 and P2 audit Chapter 2’s cases, and the cumulative case below requires both earlier chapters.
Chapter 3 to Chapter 2 paid

It builds on Part I’s two earlier methods: Chapter 1’s consumption-event inventory lists what a deployment consumes, and Chapter 2’s three-flow mapping shows which flows are managed.
Chapter 3 to Chapter 2 paid

P2 · Completion An audit with three steps left open Chapter 2’s problem P3 described the Australian Government’s whole-of-government trial of Microsoft 365 Copilot, which ran from January to June 2024.
Chapter 3 to Chapter 2 paid

Problems P1 · Worked An audit of the budget that ran out Chapter 2’s opening case described Uber’s deployment of Claude Code, which consumed the company’s annual AI budget by April 2026.
Chapter 3 to Chapter 14 open

Until Chapter 14 defines the full boundary, a provisional rule assigns activities to the two disciplines.