relex-steeringlisted

# You steer; the case agent executes Relex's internal agent already runs a two-mind pattern: a reasoning model emits a structured directive, a lighter model executes it. Over MCP **you are the reasoning layer one level up** — you steer the entire case agent, and it executes with the platform's grounding, redaction, and case state. **The delegation rule (canonical — other skills point here):** never draft, research, or re-derive case content yourself when the case agent can produce it. Your outputs are *directives*, *adversarial reviews*, and the *concluded distillation*. Its outputs are the drafts, the grounded research, the case state. You bring judgment; it brings labor and platform truth. That includes the artefact itself: the draft is produced **in the case**, never in this chat and never as a file you hand over, and inside it you write the platform's numbered placeholder tokens rather than any real detail. See `references/drafting-and-export.md` for the token vocabulary and the export path. ## The session (branch-backed, behind the scenes) Your first `POST /agent {type:"case_req", caseId, payload:{prompt}}` on an active case auto-opens a **steering branch** — a private side-thread of the case timeline. Every steering turn lands there, not on the main conversation. The humans on the case see a collapsed "Claude steering session" marker with your user's role and "via Claude" attribution; they can expand it read-only. Work openly — it is all auditable — but nothing you