The abstract the series exists to prove
Organizations are adopting AI faster than they can govern it. The result in most firms is forty people in forty chat windows, data pasted into browsers, and no record of any of it, beside a written policy nobody can enforce.
Our thesis is that the fix is not a better model and not a stricter memo. It is software that can be told what to do, held to what it may do, and made to account for what it did. When software has those three properties, a person can state an outcome, grant bounded authority, and follow the result. The work still gets done. The people stop being the ones typing it, and start being the ones who approve it and answer for it.
The series shows how an organization gets there, one question at a time. Each paper is a chapter: it takes one question a buyer actually asks, answers it from the thesis, shows what it looks like in a firm like theirs, and ends with what to do first. Read in order they build the argument; read alone each one stands.
The through-line, in four questions
Every chapter answers the same four questions about a capability, because that is the method under every C2 product:
| Question | What it means for a leader | Where the series answers it |
|---|---|---|
| What does it mean? | The work is described in business terms people and software both read | Chapters 4 and 5 |
| What does it require? | Its inputs, rules and systems are declared before it runs | Chapters 3 and 5 |
| Who may use it? | Authority is explicit, bounded and recorded; a refusal is a valid outcome | Chapters 1 and 2 |
| What happened when it ran? | A record an auditor can be shown: this version, this run, this approver | Chapters 1, 2 and 3 |
The chapters
| # | Title | Reader | The question it answers | Figures |
|---|---|---|---|---|
| 1 | Every organization has an AI policy. Almost none has a way to make people follow it. | CEO, managing partner | Why does our policy not work, and what would? | Forty windows vs one governed place; policy as document vs governance as mechanism |
| 2 | Authority must remain explicit | Compliance, risk, head of IT | How can AI act in our operations without acting on its own authority? | Interpretation vs permission matrix; the approval gate in a run; what the record holds |
| 3 | Pay for AI when the work is designed, not every time it runs | CFO and CTO | Why do AI bills grow with volume, and how do we stop that? | Cost against volume: per-call vs designed-once (illustrative); where the model is called; the measured filing (112 s against 10–20 min) |
| 4 | The cost of repeated translation | COO, CFO | Where does the time actually go? | The hand-offs in one process, each a translation; the same process with meaning kept outside code |
| 5 | Typed, checked AI calls for .NET | .NET architects | How do we put a model in a business application without breaking the pipeline? | The checked call: intent, shape, rules, retry with findings, typed result; what changes with a save vs a release |
| 6 | A Tuesday, before and after | Operations leaders | What changes for the people who do the work? | The filing clerk’s day as a timeline, before and after; the supervisor’s queue |
| 7 | Websites other software can use | Founders, product leaders | Where does this lead between organizations? | The purchasing request across two companies’ governed interfaces |