# ODD + Canon + Evidence β€” Orientation Map > A one-page mental model for the ODD system. ## Description This orientation map provides a single-page mental model of how Intent flows through ODD Manifesto to Canon to Decisions to Evidence to Outcomes. ODD is organized as a three-tier conceptual hierarchy: ODD contains universal principles (timeless), Canon contains program-level constraints (shared rules), and Docs contains implementation details (how this instance works). Maturity moves from Exploration through Validation to Commitment. The map explicitly rejects "if it compiles, it's done" and "governance replaces judgment." ## Content > This is not a workflow. It is a mental model. --- ## 🎯 The Core Idea ``` Intent | v ODD Manifesto | v Canon (Constraints & Rules) | v Decisions | v Evidence | v Outcomes ``` --- ## πŸ“– How to Read This Map β€’ ODD explains why and what we care about β€’ Canon explains how decisions tend to be shaped β€’ Decisions are local, contextual, and human β€’ Evidence grounds claims in reality β€’ Outcomes are the only thing that matters long-term Nothing here enforces anything. Everything here informs something. **Canon may reference Docs. Docs must never redefine Canon.** --- ## πŸ—οΈ The Three-Tier Hierarchy ODD is a conceptual hierarchy, not a monolithic philosophy: | Tier | Contains | Decay Rate | |------|----------|------------| | **ODD** | Universal principles (timeless, product-agnostic) | Almost never | | **Canon** | Program-level constraints (shared rules across products) | Carefully | | **Docs** | Implementation details (how this instance works) | Freely | **The litmus test:** 1. Would this still be true in 10 years? β†’ **ODD** 2. Should all products in this program obey it? β†’ **Canon** 3. Is this about how *we* do it *here*? β†’ **Docs** This separation allows ODD to outgrow any single repository. See [D0001: Three-Tier Conceptual Hierarchy](/odd/decisions/D0001-three-tier-conceptual-hierarchy.md). --- ## πŸ“Š Where Maturity Lives (Not Gates) ``` Exploration ──────→ Validation ──────→ Commitment (PoC) (Pilot) (Production) ``` Rigor increases β†’ Evidence expectations increase β†’ Governance tightens β†’ β€’ Early: bias toward learning β€’ Middle: bias toward validation β€’ Later: bias toward trust and durability No sharp lines. No ceremony required. --- ## 🚫 What This Map Explicitly Rejects β€’ β€œIf it compiles, it’s done.” β€’ β€œTrust the explanation.” β€’ β€œOne true workflow.” β€’ β€œGovernance replaces judgment.” --- ## πŸ’‘ Why This Map Exists β€’ To explain the system in under 60 seconds β€’ To anchor conversations without debate β€’ To keep humans oriented while tools change --- ## βœ… Why These Two Artifacts Are Enough for Now β€’ They surface risk without prescribing control β€’ They encode wisdom without freezing behavior β€’ They respect maturity without formalizing it This keeps you aligned with: β€’ KISS β€’ Antifragility β€’ Prompt over code β€’ Convention over configuration And most importantly: They make misuse discussable instead of shameful. --- ## See Also - [Cognitive Partitioning](/odd/cognitive-partitioning.md) β€” Why reasoning systems must divide under pressure - [ODD Misuse Patterns](/odd/misuse-patterns.md) β€” Common failure modes and how ODD gets misapplied