refactoring

Structured approach to technical debt remediation. Improve code structure while maintaining behavior through incremental, safe changes.

| Guardrail Violations | Functions >50 lines, files >300 lines | | Complexity Threshold | Cyclomatic complexity >10 | | Code Duplication | Same logic in 3+ places | | Quarterly Review | Regular technical debt assessment | | Pre-Feature | Before adding features to messy code | | Post-Incident | After bugs caused by confusing code |

| Long Method | >50 lines, multiple responsibilities | High | | Large Class | >300 lines, low cohesion | High | | Feature Envy | Method uses other class more than own | Medium | | Data Clumps | Same group of variables together | Medium | | Primitive Obsession | Overuse of primitives vs objects | Medium | | Switch Statements | Large switch blocks | Low |