Current Task

Create

AI_DEVELOPMENT_SYSTEM.md

This is NOT an implementation task.

No PHP code shall be written.

No source code shall be modified.

This document defines the official AI-assisted software development methodology used by the Inveetaire project.

It is intended to become a permanent governance document.

---

Mandatory References

Review completely:

- AI.md v1.1
- PROJECT.md
- WORKFLOW.md
- IMPLEMENTATION_ROADMAP.md
- DESIGN_REVISION_PACK_v2.0
- MASTER_IMPLEMENTATION_BACKLOG_v1.1
- DBP_v1.1
- SPRINT0_ARCHITECTURE_REVIEW.md

Review the repository structure.

Review the complete Sprint 0 implementation workflow.

Review all implementation memories.

Review all implementation responses.

---

Objective

Document the AI Development System established during Sprint 0.

This is NOT specific to Sprint 0.

This document defines the long-term operating model for AI-assisted development.

The document should be reusable for future projects.

---

Output

Create:

docs/04-governance/

AI_DEVELOPMENT_SYSTEM.md

---

Include the following sections.

# 1

Purpose

Describe why the project adopts an AI-assisted development workflow.

---

# 2

Development Philosophy

Documentation First

Architecture First

One Source of Truth

Implementation follows documentation.

---

# 3

AI Roles

Define responsibilities.

Examples:

Architecture Lead

Implementation Agent

Documentation Reviewer

Quality Reviewer

Human Approver

Clearly separate responsibilities.

---

# 4

Development Lifecycle

Document the complete lifecycle.

Example:

Business Idea

↓

Architecture

↓

Documentation

↓

Planning

↓

Prompt

↓

Implementation

↓

Review

↓

Approval

↓

Git

↓

Next Task

---

# 5

Prompt Lifecycle

Describe:

Prompt

↓

Implementation

↓

Implementation Report

↓

Architecture Review

↓

Approval

↓

Git

↓

Memory

↓

Next Prompt

---

# 6

Memory System

Describe:

.ai/memory

Purpose

Naming convention

When memories are created

When they are frozen

---

# 7

Response Archive

Describe:

.ai/responses

Purpose

Naming convention

Relationship with Memory

---

# 8

Prompt Library

Describe:

.ai/prompts

Purpose

Naming

Versioning

Reusability

---

# 9

Documentation Hierarchy

Use the approved hierarchy.

AI.md

↓

ADR

↓

MIB

↓

Sprint Plan

↓

Prompt

↓

Implementation

Include the conflict protocol.

STOP

↓

Report

↓

Wait

---

# 10

Implementation Rules

Summarize:

One task per session

No undocumented files

Files Expected governs scope

No Git execution

Implementation report mandatory

Approval required

---

# 11

Git Workflow

Document:

Implementation

↓

Review

↓

Approval

↓

Commit

↓

Push

↓

Tag

State clearly that AI never performs Git operations unless explicitly instructed.

---

# 12

Account Rotation Strategy

Document the workflow established during Sprint 0.

Include:

Multiple AI accounts

Quota rotation

Session resume

Context continuity

Repository as source of truth

Memory files

Response files

Explain why the system remains deterministic despite account rotation.

---

# 13

Quality Gates

Before implementation

Before approval

Before commit

Before sprint close

---

# 14

Documentation Synchronization

Explain:

Design Revision Pack

↓

AI.md

↓

MIB

↓

DBP

↓

Architecture Review

↓

Next Sprint

---

# 15

Lessons Learned

Summarize the most important discoveries from Sprint 0.

Include:

Examples are NOT Deliverables

Implicit prerequisites

Architecture freezes

Dependency order

Validation tasks

Documentation conflicts

---

# 16

Scalability

Explain how this methodology scales to:

Large repositories

Multiple AI agents

Multiple developers

Long-running projects

---

# 17

Future Evolution

Describe how the AI Development System itself may evolve.

Require future revisions to use Design Revision Packs.

---

# 18

Final Statement

State that this document defines the official AI Development System for the Inveetaire project and shall govern future AI-assisted development unless superseded by an approved revision.

---

Rules

Do NOT modify any existing documentation.

Do NOT redesign the architecture.

Do NOT change the implementation workflow already established.

Document only practices that were actually used or formally approved during Sprint 0.

Do not invent capabilities.

Maintain the same writing style as AI.md, DBP, and WORKFLOW.md.

This document should be suitable as a permanent governance document.

Return only the completed markdown document.