00-framework-navigation

---

AI Engineering Framework

This repository follows the Agentic Engineering Methodology.

The repository is the shared working memory for humans and AI agents.

Repository documentation is the primary source of truth.

Chat history is temporary context and must not be treated as persistent project knowledge.

---

Engineering Lifecycle

Every project follows the same lifecycle:

Project Discovery
        ↓
Roadmap Creation
        ↓
Architecture Design
        ↓
Engineering Design
        ↓
Repository Initialization
        ↓
Plan Creation
        ↓
Plan Review
        ↓
Plan Implementation
        ↓
Code Review
        ↓
Progress Update

Each stage has:

• an engineering role;
• a reusable skill;
• one or more repository artifacts.

---

Read-First Order

Before starting any work, read the repository documentation in the following order when available:

1. AGENTS.md
2. REPOSITORY_MAP.md
3. METHODOLOGY.md
4. KNOWLEDGE_MODEL.md
5. docs/project/PROJECT.md
6. docs/project/ROADMAP.md
7. docs/project/ARCHITECTURE.md
8. docs/project/ENGINEERING.md
9. Relevant ADRs in docs/project/adr/
10. Active plans in docs/project/plans/active/
11. docs/project/PROGRESS.md

If a document does not exist, continue with the next available document.

---

Repository Philosophy

The repository is organized around durable engineering knowledge rather than source code.

Documentation defines:

• project intent;
• implementation strategy;
• system architecture;
• engineering decisions;
• implementation scope;
• engineering history.

Implementation follows documentation.

Documentation does not follow implementation.

---

Documentation Precedence

When information conflicts, use the following priority:

1. docs/project/PROJECT.md
2. docs/project/ARCHITECTURE.md
3. docs/project/ENGINEERING.md
4. Relevant ADRs
5. Active implementation plans
6. docs/project/PROGRESS.md
7. Chat context

Repository documentation always overrides conversational context.