## 🛡️ Vibe Project Documentation Protocol (VPDP)
**[CRITICAL INSTRUCTION]** You are strictly bound by the following documentation lifecycle rules for this project. These rules supersede standard file creation behaviors.
### 1. The “Core Four” Documents
You are the custodian of the following four mandatory documents. You must maintain their integrity at all times:
* **`INDEX.md`**: A real-time map of the project structure. Must describe *what* each file does and *how* they relate to each other.
* **`README.md`**: The project’s “Front Page”. Contains high-level objectives, setup, usage, and current feature status.
* **`CHANGELOG.md`**: A granular log of modifications. Format: `[Date] [Type: Feat/Fix/Refactor] - Description`.
* **`FORFUTURE.md`**: The “Context Handoff” file. Designed for a *future* AI instance that has ZERO context of this chat session. It explains the “Why”, “Current Thinking”, “Hidden Gotchas”, and “Immediate Next Steps”.
### 2. Lifecycle Triggers & Update Rules
#### 🟢 Trigger: Task/Feature Completion
**WHEN** you complete a coding task, fix a bug, or finish a logical step:
**ACTION**: You MUST update the following three documents *immediately* before waiting for user input:
1. **`INDEX.md`**: Reflect any file additions/deletions.
2. **`README.md`**: Update feature status or usage instructions if changed.
3. **`CHANGELOG.md`**: Log the specific changes made in this turn.
#### 🔴 Trigger: Session Exit / “Stop”
**WHEN** the user types “exit”, “quit”, “finish”, “wrap up”, or explicitly asks to prepare for the next session:
**ACTION**: You MUST update:
1. **`FORFUTURE.md`**: Write a high-fidelity state snapshot. Assume the next AI knows nothing. Summarize the mental stack, pending logic, and potential pitfalls.
### 3. Anti-Bloat Constraint (File Control)
* **STRICT PROHIBITION**: Do NOT create any new documentation files, note files, or temporary text files outside of the “Core Four” unless:
1. The user explicitly instructs you to.
2. The code architecture *functionally requires* it (e.g., a new config file, a required asset).
* All project knowledge must be consolidated into the “Core Four”.