runtime data

AGENTS.md

@@ -49,6 +49,9 @@ The exec safety guard blocks commands without an explicit workspace path (e.g. `
   - Longer / non-trivial script -> Python.
 - Override: if the user explicitly specifies a language or location, their instruction always takes precedence.
 
+### Git clones
+- Always clone repos into `workspace/src/<repo-name>`, not directly into workspace root.
+
 ### Temporary files
 - All temporary files go to `tmp/` directory.
 - Clean up after tests and one-off operations.
@@ -63,3 +66,22 @@ something, that is a request for information only. Report your findings, then
 ask whether I want them carried out — never treat learning about a problem as a
 request to fix it. When in doubt, ask first.
 
+## Behavioral Guidelines
+
+1. Don't assume. Don't hide confusion. Surface tradeoffs.
+   - If an instruction is ambiguous, stop and ask for clarification before acting.
+   - Do not make assumptions about user intent, data formats, or scope.
+   - Explicitly surface tradeoffs when multiple implementation paths exist.
+
+2. Minimum code that solves the problem. Nothing speculative.
+   - Implement only the logic requested. Avoid premature abstraction, design patterns (like Strategy or Factory), or future-proofing that is not explicitly required.
+   - If a simple solution exists, prefer it over complex, generalized ones.
+
+3. Touch only what you must. Clean up only your own mess.
+   - Changes must be surgical. Do not reformat files, update type hints, or rewrite existing code unless it is strictly required to fulfill the specific task.
+   - If your changes introduce orphans (e.g., unused imports, dead variables), clean them up. Otherwise, leave existing code untouched.
+
+4. Define success criteria. Loop until verified.
+   - Before coding, define clear success criteria or a verification plan.
+   - Iterate and self-correct until the verification tests pass. Ensure each step of the implementation is verified against the goal.
+