oracle-debug

# Oracle Debug Random fixes waste time and create new bugs. Quick patches mask underlying issues. **Core principle:** find root cause before attempting any fix. Symptom fixes are failure. **Violating the letter of this process is violating the spirit of debugging.** ## The Iron Law ``` NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST ``` If you haven't completed Phase 1, you cannot propose fixes. ## When to Use Use for any technical issue: - Test failures - Bugs in production - Unexpected behavior - Performance regressions - Build or integration failures - Intermittent failures **Use this especially when:** - Under time pressure - "Just one quick fix" seems obvious - You've already tried multiple fixes - The previous fix didn't work - You don't fully understand the issue ## The Four Phases You must complete each phase before proceeding to the next. --- ## Phase 1 — Root Cause Investigation **Before attempting any fix:** Use the project's domain glossary and ADRs to build a clear mental model of the relevant modules before tracing. 1. **Read error messages carefully.** Read the full stack trace, line numbers, file paths, and error codes. Don't skip warnings. 2. **Build a fast feedback loop.** If you don't have a fast, deterministic, pass/fail signal for the bug, no amount of code-reading will save you. Spend disproportionate effort here. Try these in order: - Failing test at the seam that reaches the bug - Curl / HTTP script against a running dev ser...