AI.md v1.1 — Synchronization Complete
Changes Made
All original rules preserved verbatim. Three targeted additions only.

1. Version header updated
Version : 1.0  →  Version : 1.1
Change history block added below the header listing both versions.

2. Section 25 — File Creation Boundaries
Two new subsections appended within Section 25 (no renumbering of existing sections):

25a. Examples Are Not Deliverables — Documentation examples are illustrative only. Only "Files Expected" defines scope. Examples must never be created automatically. (REV-016, DRP v2.0 Lesson 5)

25b. Implicit Prerequisites — If a task requires any artifact not listed in "Files Expected" and not already in the codebase: STOP → Explain → Wait for approval. Silent creation is a scope violation. (REV-016, DRP v2.0 Lesson 6)

3. Section 27 — Automatic Stop Conditions
Stop condition 8 added:

A documentation conflict is detected between any two documents at different levels of the authority hierarchy (see Section 28)

4. Section 28 — Implementation Authority Hierarchy (new)
Complete new section formalizing REV-023:

Six-level priority chain: AI.md → ADR → MIB → Sprint Execution Plan → Implementation Prompt → Implementation
Conflict Protocol: 5-step stop-identify-state-report-wait sequence
Implementation Prompts are execution instructions only — they do not override AI.md, ADR, MIB, or Sprint Execution Plan
Architecture decisions may not be inferred — if documentation leaves multiple valid implementations, STOP and present options
CLI Validation Test Scaffold — ob_start() → Bootstrap::init() → ob_end_clean() rule formalized (REV-022)
5. Section 3 — Document Authority
A cross-reference line added pointing to Section 28 for the implementation-time hierarchy. The Section 3 product/architecture hierarchy (PRD → SAD → ... → AI.md) is unchanged.

Proposed commit message (do NOT execute — awaiting your instruction):

docs: synchronize AI.md to v1.1 — DRP v2.0 governance improvements