Reading · The Canon
Six short books on how organizations run, and how to put AI to work inside them.
Volume I is the argument; Volume II is how an engagement works; Volumes III to V are how Bedrock is organized and what it builds; Volume VI is what we do not know yet. If you run a company, start with the first two chapters of Volume I; they are short. Every volume is dated and will be revised as the field teaches us more. These are written in our working vocabulary, for readers who want the whole framework.
I · The Manifesto
Why organizations stall
First Edition · July 2026 · 62 pages
Intelligence has become a commodity, so the binding constraint has moved to organizations’ capacity to absorb it. That capacity lives in an undocumented operating model that beats any tool bolted onto it. The asset that distinguishes firms — organizational intelligence — can now be engineered as enterprise cognition: six functions around a core of memory, machines holding the middle, people holding the ends. Twelve principles make this enforceable.
Chapters
- The Constraint Has Moved
- The Operating Model Is Already There
- Organizational Intelligence
- Enterprise Cognition
- The Rate of Learning
- The Flywheel
- Principles
- The Long View
The AI era is not constrained by intelligence. It is constrained by deployment.
Every workaround is an unfiled bug report against the official process.
In the era of abundant intelligence, the rate of organizational learning is the only durable advantage.
Institutions that intend to last do not begin with the facade. They begin by finding bedrock, and building down to it.
II · The Method
How an engagement runs
First Edition · July 2026 · 38 pages
An organization becomes AI-native by having its real operating model recovered, redesigned, and left learning, through five movements run in order and then run again: observe, map, design, deploy, learn. A solution is a hypothesis about a system not yet observed; decisions, not processes, are the unit of observation; the map is drawn from the exceptions outward; memory is designed before automation; deployment is an experiment.
Chapters
- Observation Before Intervention
- Mapping Organizational Intelligence
- Designing the Operating Model
- Deployment
- The Learning Loop
Processes are what organizations draw; decisions are what they do.
We do not map the process. We map the judgment.
We do not design software. We design where decisions live, what they remember, and what they leave behind.
Decide nothing; record everything.
III · The Operating System
How Bedrock is organized
First Edition · July 2026 · 19 pages
A firm that teaches organizations to become learning systems must be built as one. Bedrock is framed as an instrument for producing observations, judged by their fidelity and rate: pods, knowledge capture, doctrine earned by recurrence and refutation, platform as the hardened residue of doctrine, and research as the second purpose of every deployment.
Chapters
- Pods
- Knowledge Capture
- Doctrine
- Platform
- Research
Completion is defined by capture, not by delivery.
Doctrine is earned, never invented.
The platform exists to serve the Method. The Method does not exist to justify the platform.
The discipline begins at home.
IV · Industry Playbooks
Why no industry playbook
First Edition · July 2026 · 19 pages
Not a book of playbooks — an account of why none is needed. The Method is the questions; the operating model is the answers. Every organization is built from the same organs; industries are combinations of a small set of decision architectures, not kinds. The variable layer is most of the work and must be recovered, never imported.
Chapters
- The Same Hidden Structure
- Industry Ontologies
- Recurring Decision Architectures
- What Changes
- What Never Changes
The Method is the questions. The operating model is the answers.
The incumbent knows the vocabulary and assumes the grammar. Bedrock knows the grammar and learns the vocabulary.
Recover it; never import it.
One discipline. Many expressions.
V · The Platform
What gets built
First Edition · July 2026 · 20 pages
The platform is not the product; it is the machinery that lets the Method operate repeatedly, and every layer is a forced consequence of doctrine: memory, ontology, enterprise cognition, workflow, evaluation, modularity. Written backward from the usual engineering account — requirement first, software second.
Chapters
- Memory
- Ontology
- Enterprise Cognition
- Workflow
- Evaluation
- Modularity
Technology follows doctrine, never the reverse.
Faculties, not modules.
Human judgment is a participant, not a part — it holds the ends.
Build the machinery the doctrine requires; replace it as technology allows; keep the doctrine.
VI · The Research Agenda
What we do not know yet
First Edition · July 2026 · 20 pages
The Canon’s deliberate inversion. Where the first five volumes state what Bedrock knows, this one states, as plainly as it can, what is not known: twenty-eight open questions and six open problems, left open on purpose. It does not teach. It asks.
Chapters
- Organizational Intelligence
- Enterprise Cognition
- Evaluation
- Platform
- The Discipline
- Open Problems
Doctrine ends here. Research begins.
Naming a thing is not understanding it.
A proxy is not a measure.
A discipline without unanswered questions is not complete; it is an ideology.
Colophon
Each volume is revised as understanding improves; the edition number is a version number. The mark — six points joined through a centre — is the picture of an organization’s six working functions around a shared memory, described in Volume I.