Reading Map¶
This reading path helps new readers move from premise to vocabulary to practical patterns.
1. Start With The Position¶
Read Doctrine first. It states the stable Drift Doctrine.
2. Read The Manifesto¶
Read Manifesto next. It states the architectural argument behind Because Drift Happens.
3. Learn The Operating Principles¶
Read Principles next. These principles explain the assumptions that guide the framework.
4. Establish The Vocabulary¶
Read Glossary before going deeper. The framework depends on consistent use of terms such as drift, coherence, control plane, intervention, and runtime governance.
5. Understand The Core Concepts¶
Read these in order:
6. Move To Distributed Autonomy¶
Read Federation and Control Planes to understand why multi-agent and distributed systems need governance above individual execution paths.
7. Study Failure And Design Patterns¶
Read Failure Patterns and Architecture Patterns. These documents translate the doctrine into recurring operational problems and design responses.
8. Review Examples And RFCs¶
Use Examples for simple conceptual scenarios. Use RFCs to understand scope decisions and propose changes to the framework.