# Frequently Asked Questions Version: 1.0.0 --- # Frequently Asked Questions ## What is AI Orchestrated Development (AOD)? AI Orchestrated Development (AOD) is a structured software engineering methodology that transforms AI from a coding assistant into a complete software engineering organization. Rather than immediately generating code, AOD guides projects through Discovery, Governance, Architecture, Planning, Implementation, Validation, and Evolution. --- ## Is AOD a software product? No. AOD is a methodology. It provides a structured process for collaborating with AI to design, build, validate, and evolve software. --- ## Does AOD replace software developers? No. AOD improves the software engineering process. It can be used by founders, software developers, consultants, engineering teams, and organizations to improve project quality and consistency. --- ## Can non-technical founders use AOD? Yes. AOD was specifically designed so that non-technical founders can communicate business objectives while allowing AI to guide the engineering process. Technical expertise is helpful but not required. --- ## Which AI platforms support AOD? AOD is platform independent. Any AI capable of maintaining context, reasoning through complex problems, following structured workflows, and generating documentation can participate in the AOD methodology. --- ## Why doesn't AOD begin with coding? Because software quality depends on understanding. The methodology intentionally focuses on Discovery and Governance before implementation to reduce technical debt, eliminate ambiguity, and improve long-term maintainability. --- ## Why does AOD ask so many questions? The quality of the solution depends on the quality of understanding. Discovery is designed to ensure the AI understands your business before recommending technical solutions. --- ## Can I skip phases? No. Each phase builds upon the previous phase. Skipping phases increases the likelihood of misunderstandings, architectural drift, technical debt, and costly rework. --- ## How long does Discovery usually take? Discovery varies based on project complexity. Simple products may require less than an hour. Enterprise platforms may require multiple sessions. Discovery continues until both the human and AI agree that the business is sufficiently understood. --- ## What happens after Discovery? After Discovery has been approved, the AI begins creating the governance artifacts that establish the engineering foundation for the project. Only after Governance has been approved does the project advance to Architecture. --- ## Why are governance artifacts important? Governance artifacts preserve the knowledge, decisions, terminology, business rules, and architecture that define the project. They become the foundation for every future engineering decision. --- ## Can AOD be used with an existing application? Yes. AOD supports both new product development and the continued evolution of existing applications. Existing products typically begin with Discovery to establish an accurate understanding of the current system before moving through the remaining phases. --- ## What happens when requirements change? Requirements naturally evolve. AOD evaluates each proposed change and determines whether the project should revisit an earlier phase before implementation continues. This protects the integrity of the engineering process while allowing the product to evolve. --- ## Is AOD only for software? No. Although AOD was created for software engineering, the methodology can also be applied to product planning, automation initiatives, AI integrations, digital transformation projects, and other structured problem-solving efforts. --- ## How do I know when a project is complete? A project is complete when the Validation phase confirms that: Business objectives have been achieved. Success criteria have been satisfied. Governance artifacts accurately represent the solution. The human approves the completed project. --- ## Does AOD end after deployment? No. Deployment marks the transition into the Evolution phase. Every future enhancement, feature request, or architectural change follows the same disciplined methodology to ensure the product continues improving without sacrificing quality. --- ## Where should I begin? Begin with the Quick Start Guide. Then copy the AOD Initialization Prompt into a new AI conversation and allow the methodology to guide you through the Discovery phase.