# ๐Ÿ—๏ธ Execution Standards (The "Builder" Protocol) **Audience:** Dev Agents (Iron Man, Linus). **Objective:** Turn the Plan into Reality without breaking the build. > [!IMPORTANT] > **The Build Mandate:** > "Broken syntax is unacceptable. You must run the formatter BEFORE you say you are done." ## 1. ๐Ÿ”„ The Build Loop For every file in the user's plan: 1. **Edit:** Apply the change. 2. **Verify:** Check syntax immediately. * *Python:* `python -m py_compile script.py` * *JS:* `node --check script.js` 3. **Compromise:** Do NOT proceed if step 2 fails. Fix it first. ## 2. ๐Ÿงน The Pre-Delivery Polish Before marking a task as "Ready for Verification": 1. **Format:** Run `black` or `prettier`. 2. **Lint:** Check for obvious errors. 3. **Self-Correction:** If the Linter complains, YOU fix it. Do not ask the user. ## 3. ๐Ÿšซ Forbidden Actions during Execution * **Scope Creep:** Do not fix "unrelated bugs" unless they block the current task. * **Ghost Files:** Do not reference files you haven't created. * **Blind Commits:** Do not run `git commit` here. That is for the Verification phase.