Reading Map

Start with the Drift Doctrine, then choose the path closest to your work. The doctrine applies across businesses, teams, processes, and technology. The technical framework is one application of it.

Business and Organizational Drift

1. Read the Doctrine for the six-line premise and its governance response.
2. Read Drift for changes in assumptions, incentives, policies, and operating conditions.
3. Read Coherence for keeping intent, actions, feedback, and accountability connected.
4. Work through the Business Commitment Example: a delivery forecast changes while the customer promise stays the same.
5. Practise with the Guided Exercise: assess a delivery risk, choose a response, and compare your reasoning.
6. Continue with By Inches in the Vault for an essay on how small deviations accumulate.

The practical questions are: what was intended, what changed, what evidence supports the signal, and who has authority to respond? A changed plan is not automatically a failure; the response may be to correct execution or explicitly agree on a new commitment.

Technical Systems and AI Governance

1. Start With The Position

Read Doctrine first. Its broad premise also applies to autonomous and semi-autonomous software.

2. Read The Manifesto

Read Manifesto for the architectural argument behind the technical framework.

3. Learn The Operating Principles

Read Principles as working interpretations for governable autonomous operations.

4. Establish The Vocabulary

Use the Glossary for drift, coherence, control planes, intervention, and runtime governance.

5. Understand The Core Concepts

Read Drift, Coherence, Governance, Observability, and Intervention.

6. Move To Distributed Autonomy

Read Federation and Control Planes for governance across agents, workflows, and organizational boundaries.

7. Study Failure And Design Patterns

Read Failure Patterns and Architecture Patterns. These are developing reference patterns, not validated production designs.

8. Review Examples And RFCs

Use Examples for illustrative scenarios and RFCs for recorded scope decisions. Continue with the Vault’s Governing Intelligent Systems guide for related essays and field notes.

Practise Applying the Ideas

After either path, complete the Guided Exercise: Recognize and Respond to Drift. Allow 15–20 minutes to assess a hypothetical report-delivery problem, write a response plan, and compare it with a suggested response. A changed-assumption challenge and a technical extension help you apply the ideas beyond the initial scenario.

Content Maturity

Each page identifies its status:

• Stable doctrine: the six-line core is the framework’s reference wording. This is a statement of its role here, not a claim of scientific proof or completeness.
• Working interpretation: concepts, vocabulary, principles, patterns, and visual interpretations remain open to refinement and evidence.
• Illustrative example: a hypothetical scenario for reasoning about drift; not a client case study or production design.
• Planned work: a backlog item that has not been completed.
• Accepted scope: a recorded framework decision; not evidence that every described capability has been implemented.
• Reading guide: navigation and context for the body of work, without a separate claim of doctrinal authority.

Published illustrations can remain working interpretations. Their appearance on the site does not make every visual choice canonical. The doctrine wording remains the reference.