ralph

# /ouroboros:ralph MCP-owned Ralph loop around background `evolve_step` jobs. "The boulder never stops." ## Usage ``` ooo ralph --lineage-id <lineage_id> /ouroboros:ralph --lineage-id <lineage_id> # For a plain natural-language request, run `ooo interview` + `ooo seed` first, # then call the MCP tool with a fresh lineage_id and the validated Seed YAML. ``` **Trigger keywords:** "ralph", "don't stop", "must complete", "until it works", "keep going" ## How It Works Ralph is owned by the `ouroboros_ralph` MCP tool. In non-plugin runtimes, the tool starts one background Ralph job, runs repeated `evolve_step` generations inside that job, and stops only when QA passes, convergence is reached, a terminal evolution action occurs, cancellation is requested, or `max_generations` is reached. In OpenCode plugin mode, the MCP tool returns a `delegated_to_plugin` envelope with `job_id=None`; the bridge plugin dispatches a child Task session that owns the loop instead of creating a local JobManager job. The client skill should not reimplement the loop. Deterministic frontmatter dispatch is limited to the router's named `--lineage-id` option so raw trailing text is never treated as lineage identity. Raw natural-language `ooo ralph "<request>"` input must flow through the validated Seed path before any mutating Ralph loop starts. Until a lineage id and optional Seed YAML are prepared, `ouroboros_ralph` returns structured input guidance instead of starting a job. Once the inputs are pr...