runlisted

# Leanforge:Run > **Reply in the user's language from the first line and keep it throughout.** Write natively; the > language of the 3-doc, codebase, or these instructions never overrides the user's language. Consume the **approved 3-doc** produced by `Prime` and realize the spec through dependency-aware waves, right-sized verification, spec-first review, and integration gates. Run in the same session as Prime when possible; the self-contained 3-doc—not dialogue—is execution authority. Force-load `references/orchestration.md`. Force-load `references/harness-lifecycle.md` before any state-directory compatibility or interrupted-run decision and reuse it at the harness step; load prompt references at their dispatch steps. ## Core principles - **Follow the Execution Graph.** The producer owns `depends` and `regen_barriers`; do not invent, remove, or reorder them. A malformed graph is a producer-side defect and blocks. - **Serve the spec.** Correct means spec-conformant. Spec beats plan, code, and convention; suspected spec error or conflict returns to the user rather than being silently repaired. - **Escalate, do not guess.** Ambiguity, architecture mismatch, `NEEDS_CONTEXT`, `BLOCKED`, conflict, or data risk pauses the run while the orchestrator asks the user. Children never ask directly. - **Protect main; prove results.** Existing projects stay on a feature branch until user-approved integration; greenfield may use main. Captured commands, output, and exit codes—not