ralph-workflow

Observable progress in an automated loop workflow is enforced by requiring a valid ---RALPH_STATUS--- block after each invocation. This contract prevents silent or regressive work by gating advancement until valid status is reported.

Gating advancement and tracking completion in a loop harness is managed by tripping a circuit breaker on no-progress loops. It exits safely when EXIT_SIGNAL is true and adequate completion indicators are met.

The RALPH_STATUS block ensures safe loop termination by emitting a properly structured status report that tracks completion indicators and evaluates the EXIT_SIGNAL. This prevents partial execution from ending the loop prematurely.

QA checks in a per-loop execution contract are triggered when the loop reaches an epic boundary. The workflow reads fix_plan.md, reports task completion, and decides if the epic boundary QA is needed for loop hygiene.

Loop workflow advancement fails when the per-loop execution contract is not satisfied. The harness requires a compliant ---RALPH_STATUS--- block to report completion and verify progress before picking the next unchecked task.

Yes, you can automate reading fix_plan.md and reporting completion by invoking the Ralph workflow at the start of every loop. It picks the first unchecked task and outputs a compliant ---RALPH_STATUS--- block.