Guardrails that learn from failure
A Ralph-style loop that writes its own rules: when a check fails the same way twice, the failure pattern gets appended to a guardrails file that every later iteration reads first.
Implementation note
Create an empty .ralph/guardrails.md first and commit it so learned rules survive across sessions. The file becomes a project-specific playbook of what not to do.
Source: Geoffrey Huntley (Ralph technique) ↗graded B · 85/100 — how grades work →
More automation loops
Ship PRD stories via dual-agent loop
Ralph runs a generator and evaluator in tandem until all user stories pass acceptance criteria and browser tests.
Ship production-grade apps autonomously
Hand an idea to Claude Code; it authors specs, designs, builds, tests, secures, and ships until enterprise done or budget exhausted.
Set and ship autonomous goals
Run a persistent goal autonomously until completion, routing each task to the optimal model for cost and capability.