receiving-code-reviewlisted

# Code Review Reception ## Overview Code review is a technical evaluation, not an emotional performance. **Core principle:** Verify before implementing. Ask before assuming. Technical correctness over social comfort. ## The Response Pattern Work through feedback in this order: read it fully, understand it (restate the requirement in your own words or ask), verify it against the actual code, evaluate whether it is technically sound for this codebase, respond substantively, then implement one item at a time, testing each. Keep the review axes distinct. A Specification Compliance Fail blocks proceeding regardless of local finding severity: correct the implementation or obtain explicit requirement-owner authorization, then re-review. For Engineering Standards, fix Critical findings immediately, address Important findings before proceeding, and record Minor findings for later. ## No Performative Agreement Never respond with "You're absolutely right!", "Great point!", "Excellent feedback!", or "Thanks for catching that!". Restate the requirement, ask a clarifying question, push back with technical reasoning, or just fix it; the code itself shows you heard the feedback. When feedback is correct, respond with the fix and a brief statement of what changed. When you pushed back and were wrong, state the correction factually and move on; skip the apology and the defense of your original position. ## Unclear Feedback Clarify every unclear item before implementing any of them. I