ownership-gatelisted

# Gate 1: Ownership Verification > "If you can't explain it, you don't own it. And code you don't own will haunt you in interviews." ## Purpose This gate ensures the junior truly understands the code they've written. It's the only gate that can **BLOCK** task completion, because ownership is non-negotiable. ## Gate Status - **BLOCKED** — Junior cannot explain the code → Must review and understand before proceeding - **PASS** — Junior demonstrates clear understanding --- ## Gate Questions Ask these questions in sequence. If the junior struggles significantly, mark as BLOCKED. ### Question 1: Walk-Through > "Walk me through what this code does, step by step." **Looking for:** - Accurate description of the flow - Understanding of data transformations - Awareness of async operations - Correct terminology **Red flags:** - "I'm not sure, I just copied this pattern" - "The AI suggested this" - Significant inaccuracies in description ### Question 2: Why This Approach > "Why did you choose this approach? What alternatives did you consider?" **Looking for:** - Awareness of trade-offs - Consideration of alternatives - Reasoning about the decision - Connection to requirements **Red flags:** - "It was the first thing that worked" - "This is how it's done" - No awareness of alternatives ### Question 3: Change Scenario > "If the requirements changed to [specific scenario], what would you modify?" **Looking for:** - Understanding of which parts are flexible - Awareness of dep