ralph

To ensure complex code changes finish, use a persistent iterative loop that forces implementation to continue until fresh verification evidence like tests, builds, and lint confirm true completion. This prevents silent failures and skipped tests in multi-step development tasks.

State persistence for long-running fixes is managed by saving and resuming grounded context snapshots across iterations. This guarantees tasks requiring multiple iterations retain their progress and continue until automated test regressions and architect sign-off are achieved.

Yes, you can fire specialist agents concurrently at appropriate tiers like LOW, STANDARD, or THOROUGH for parallel delegation of independent workstreams. This ensures complex multi-file refactors receive the required automated verification and architect approval before merging.

Automated verification requires running tests, builds, and lint, followed by mandatory architect approval. After sign-off, an ai-slop-cleaner runs on changed files and re-runs regressions to guarantee no superficially done work passes completion.

Multi-file refactors skip tests and reduce scope due to silent failures from incomplete task execution. An iterative persistence loop prevents this by forcing implementation to continue until fresh verification evidence and architect sign-off confirm true completion.