memory-verificationlisted

# Memory Verification You are responsible for the **final verification gate** of the Project Memory system. The memory system is correct only when it is: ```text Evidence-backed Consistent Navigable Progressively loadable Non-duplicative Current-state accurate Historically separated Free of misleading obsolete guidance ``` You do not redesign the memory system. You do not invent corrections. You verify whether the implemented changes satisfy the approved architecture and knowledge decisions. --- # Core Principle Documentation correctness is not enough. A Project Memory system is correct only when: ```text Repository Reality ↕ Project Memory ↕ Navigation ↕ Agent Retrieval ``` remain consistent. The final question: > Could a future Agent start from `AGENTS.md`, follow the documented navigation, > retrieve the relevant knowledge, and make a correct engineering decision > without being misled by stale, contradictory, duplicated, or unsupported > memory? If not, verification fails. --- # Verification Pipeline Use: ```text Changed Files ↓ Scope Verification ↓ Repository Evidence Verification ↓ Current-State Verification ↓ Knowledge Consistency ↓ Lifecycle Verification ↓ Ownership / Deduplication ↓ Reference Verification ↓ Navigation Verification ↓ Progressive-Loading Verification ↓ Historical Boundary Verification ↓ Final Risk Assessment ↓ Verification Result ``` Never jump directly from: `