Issue #3 Task #3, basic structure

AI Docs/01-AI-GUIDE.md

@@ -22,4 +22,18 @@ When prompting an AI about this project, include:
 - Flag any Godot 3 vs 4 API differences (e.g., `move_and_slide()` behavior, signal typing).
 - If a request needs multiple scenes, describe the scene hierarchy before showing code.
 
-Read `ARCHITECTURE.md` for system boundaries and data flow expectations.
+
+## Handling Ambiguity & Assumptions (Crucial!)
+
+When a request is ambiguous, incomplete, or requires knowledge outside the scope of the provided documents:
+1. **DO NOT guess.** Do not write code based on assumptions you cannot validate.
+2. **Acknowledge the Gap:** Explicitly state what information is missing or unclear (e.g., "The current architecture does not specify how \`WaveRunner\` handles player death.").
+3. **Propose Assumptions:** If a concrete implementation path *must* be shown, list all assumptions made clearly before writing code. Use a dedicated section like:
+
+\`\`\`markdown
+**[ASSUMPTIONS MADE]**
+1. We assume that the \`PlayerStats\` Resource is accessible from the global scope.
+2. We are assuming the signal for enemy death will be named \`mob_killed\`.
+\`\`\`
+
+This ensures that the final code provided by AI can be reviewed against project reality before integration.