ralph-loop-yylo
Execute one assigned task in the Ralph loop
Read references/implement.md completely and follow it.
Stay within the assigned task. Do not select unrelated work, edit tasks.md, auto-tag releases, push, deploy, mutate production, or broaden scope because another issue is noticed. Record a bounded related Kanban follow-up when necessary.
Keep durable instructions concise and evidence-backed. Status belongs in the task response and runtime receipts, not AGENTS.md.
Controller checkpoints are best-effort local durability warnings after terminal metadata is durable. They never gate yy pi, yy task, yy merge, product commits, candidates, or releases.
User-facing Record results
After creation, update, discovery, or handoff, report the Record kind/profile, actual immutable Record ID, and actual Ledger slug from the returned Record or a native get readback. Never invent a slug from the title or confuse it with the ID. If the selected API omits a field, say it is unavailable rather than fabricate it. IDs remain authoritative for relations and lifecycle operations; slugs aid discovery.