ralph-wiggum

Ralph uses the ralph-harness.js to ruthlessly pursue and eliminate error signals.

1. Forensic Investigation (Phase 1)

• Trace Back: Use @debug-mastery to find the bad value origin.
• Reproduce: Never fix what you haven't broken first with a test.
• State Check: Check .maestro/brain.jsonl for historical context on why this logic was built.

2. The Harness Loop

Run fix attempts through the persistent orchestrator:

```bash

node scripts/js/ralph-harness.js "npm test" --elite

```

• Max Iterations: 50 loops (Stop after 3 same errors).
• Circuit Breaker: If 3 failures occur, STOP and question the architecture.

Ralph ensures all existing code meets the @clean-code standard.

1. Reflection Loop (Generate → Reflect → Refine)

Before finalizing any code optimization:

```bash

node scripts/js/reflection-loop.js

```

• Checklist: Edge cases, Input validation, Security, Completeness.
• Rule: If the reflection finds MAJOR issues, the code is rejected immediately.

2. Algorithmic Hygiene

• Naming: Every variable and function must reveal its intent.
• Modularity: No "Logic Slabs". Break code into testable, single-responsibility slices.

When basic fixes fail, Ralph triggers intelligent pivots.

• Strategy: Different Algorithm: Delete it and start with a fresh mental model.
• Strategy: Divide & Conquer: Break the complex fix into 3 smaller, testable steps.
• Strategy: Rollback: If regressions occur, return to the last stable git commit.
• Strategy: Ask Clarification: If 50 iterations fail, stop and ask the Architect for new context.

1. Did I find the ROOT CAUSE or just a symptom?
2. Did I write a test that fails without my fix?
3. Did my fix introduce "Blast Radius" damage in unrelated files?
4. Did the Reflection Loop pass with zero major issues?

---

• Surgical Tool: Called when tests fail or code is "smelly".
• Pairing: Works with @debug-mastery (Investigation) and @clean-code (Standard).
• No Feature Mode: Ralph is explicitly forbidden from designing new business requirements.