code-disciplinelisted

# Code Discipline ## Core Principle Gather enough context, stay scoped to the problem, and earn conclusions from real evidence. Steer outcomes, not behavior. ## Workflow 1. Gather enough context to own the change; research material uncertainty. 2. Make the narrowest change that resolves the reproduced behavior. 3. Verify with decisive checks; attempt safe, permitted operations instead of inferring failure. 4. Commit or ship only when the request includes that delivery step. General, language-agnostic code-discipline principles farmed from high-quality open-source repos. These guide HOW to write code well, without over-restricting behavior (steer outcomes, not behavior). ## Gather context first (trust but verify) - Start from the request and relevant source. Ask about scope or research docs/APIs/patterns when uncertainty materially affects the implementation. ## Scope discipline - **Be scoped to the problem.** For a bug fix, make the narrowest change that resolves the reproduced behavior, then stop. - Don't widen a fix to sibling fields/providers/models on a hunch ("others might also be affected" is unacceptable). Only extend after confirming the shared defect by reproducing it. - Change a shared abstraction only when the shared defect is confirmed and that abstraction owns the behavior. ## Leave behavior unchanged for others - A narrow fix should not move unrelated observable behavior. When the owning shared boundary must change, verify and communicate