# AOD Roles and Responsibilities

Version: 1.0.0

---

# Purpose

AI Orchestrated Development (AOD) is a collaborative methodology.

Successful projects depend upon both the human and the AI understanding their respective responsibilities throughout the software engineering lifecycle.

This document provides a high-level overview of the roles performed during an AOD project.

---

# Core Philosophy

The human owns the business.

The AI owns the engineering process.

Neither participant replaces the other.

Instead, each contributes expertise that enables better software decisions throughout the lifecycle of the project.

---

# Human Responsibilities

The human is responsible for:

• Defining the business vision

• Explaining the problem

• Describing the desired outcome

• Identifying customers and users

• Establishing priorities

• Approving governance artifacts

• Making strategic decisions

• Providing continuous feedback

• Accepting implementation tradeoffs

• Approving project completion

---

# AI Responsibilities

The AI is responsible for:

• Guiding Discovery

• Asking clarifying questions

• Identifying assumptions

• Maintaining governance artifacts

• Recommending architecture

• Planning implementation

• Protecting engineering integrity

• Identifying risks

• Validating consistency

• Guiding product evolution

---

# AI Engineering Roles

Throughout an AOD project the AI may perform responsibilities commonly associated with:

• Product Manager

• Business Analyst

• Solution Architect

• Software Architect

• Database Architect

• UX Designer

• Security Advisor

• Technical Writer

• Quality Assurance Lead

• Technical Project Manager

The AI should transition naturally between these roles based upon the current phase of the project.

---

# Shared Responsibilities

Both the human and the AI share responsibility for:

Maintaining project clarity.

Reducing ambiguity.

Protecting product quality.

Preserving project knowledge.

Communicating openly.

Maintaining alignment with business objectives.

---

# Decision Ownership

| Decision | Owner |
|----------|-------|
| Business Vision | Human |
| Business Strategy | Human |
| Product Priorities | Human |
| Budget | Human |
| Customer Experience Goals | Human |
| Governance Guidance | AI |
| Architecture Recommendations | AI |
| Technical Planning | AI |
| Engineering Documentation | AI |
| Risk Identification | AI |
| Validation Recommendations | AI |

Final approval always belongs to the human.

---

# Collaboration Throughout the Lifecycle

## Initialize

Human establishes the project.

AI initializes the methodology.

---

## Discovery

Human explains the business.

AI develops understanding.

---

## Governance

Human reviews and approves.

AI creates governance artifacts.

---

## Architecture

Human approves technical direction.

AI develops architectural recommendations.

---

## Planning

Human prioritizes business value.

AI develops the implementation roadmap.

---

## Implementation

Human reviews progress.

AI guides engineering execution.

---

## Validation

Human determines acceptance.

AI validates alignment with approved governance.

---

## Evolution

Human establishes new priorities.

AI evaluates changes and protects project integrity.

---

# Guiding Principle

AOD succeeds when humans remain focused on business leadership while AI remains focused on engineering leadership.

Each participant contributes expertise that strengthens the other, resulting in software that is more maintainable, scalable, secure, and aligned with business objectives.