# Documentation ## Everything You Need to Build Better Software with AI The AI Orchestrated Development (AOD) Standard is fully documented and freely available. Whether you're learning the methodology, starting your first project, or integrating AOD into your organization, every document is designed to provide a clear, structured understanding of the engineering process. --- # Documentation Library The AOD documentation is organized into six major areas. --- # Manifest The Manifest defines the philosophy and purpose of AI Orchestrated Development. It establishes the guiding beliefs behind the methodology and serves as the foundation for every AOD project. Documents include: • Manifest --- # Core The Core documents define the responsibilities and operating principles that govern every AOD project. Documents include: • Core Principles • AI Responsibilities • Human Responsibilities --- # Workflows The Workflow documents describe every phase of the AOD lifecycle. Each workflow explains the objective of the phase, expected deliverables, participant responsibilities, and approval criteria. Documents include: • Discovery • Governance • Architecture • Planning • Implementation • Validation • Evolution --- # Artifact Specifications Artifact Specifications define every governance artifact produced during an AOD project. These specifications ensure every project creates consistent, high-quality engineering documentation. Artifact Specifications include: • Source of Truth • Product Bible • Product Vocabulary • Product Requirements • Data Dictionary • Information Architecture • UI/UX Bible • Build Master Plan • Decision Log --- # Reference Reference documentation provides supporting guidance for applying the methodology. Documents include: • Project Lifecycle • Governance Artifact Guide • Document Relationships • Roles and Responsibilities • Best Practices --- # Getting Started New users should begin here. These documents explain how to initialize an AOD project and begin collaborating with AI. Documents include: • Quick Start Guide • Frequently Asked Questions • AI Compatibility Guide --- # Examples Example projects demonstrate the methodology in practice. Each example follows the AOD lifecycle and illustrates how the methodology adapts to different types of software projects. Examples include: • Founder Example • SaaS Example • Enterprise Modernization Example --- # Versioned Documentation Every document within the AOD Standard is versioned. As the methodology evolves, previous versions remain available to preserve compatibility and historical reference. --- # Open Standard The AOD Standard is designed to evolve through practical experience. New guidance, examples, governance artifacts, and supporting documentation will continue to expand while preserving the core principles established by Version 1.0. --- # Where Should You Start? If you're new to AOD, the recommended reading order is: 1. Quick Start Guide 2. Manifest 3. Core Principles 4. Project Lifecycle 5. Initialization Prompt 6. Begin Your First Project Following this sequence provides a complete understanding of the methodology before beginning implementation.