changes saved in my editor

AGENTS.md

@@ -23,9 +23,13 @@ All code written for, with or as part as mize (except for the small core) is wri
 
 To understand the main components of the architecture you can refer to `docs/architecture.md`.
 
-## Require clarification and plan approval before making code changes
+Any proc macros should go into `./macros`.
+the core mize library is in `./core`
+any mize parts are in `./parts` or in their own repositories.
 
-Before making any code changes other than the changelog, you must follow this two-step process:
+## Require clarification and plan approval before making architectural code changes
+
+Before making any code changes which could be considered to influence the architekture of the application, you must follow this two-step process:
 
 ### Step 1: Ask Clarifying Questions
 
@@ -34,6 +38,7 @@ Before making any code changes other than the changelog, you must follow this tw
 - Clarify any ambiguous requirements or edge cases
 - Ask about preferred approaches if multiple solutions exist
 - Confirm the expected behavior and user experience
+- Ask the clarifying questions by numbering them, so the user can number their replies.
 
 ### Step 2: Present Implementation Plan
 
@@ -45,6 +50,11 @@ Before making any code changes other than the changelog, you must follow this tw
 - Estimate the complexity and scope of changes
 - **Wait for explicit user approval** before proceeding with any code changes
 
+### What are considered architectural changes
+TODO: add better examples.
+
+eg: adding a seccond line displaying a different value from the DB is not considered architectural. as it was achievable by only modifying the existing function and rsx! code.
+
 ### Approval Requirements
 
 - User must explicitly approve the plan with words like "yes", "approved", "proceed", "go ahead", or similar