delegate-to-preserve-context
Delegate to Sub-Agents to Preserve Main-Session Context
Section titled “Delegate to Sub-Agents to Preserve Main-Session Context”Default posture: delegate, unless the work needs the accumulated conversation. Inline is for the five named cases below; everything else routes through a sub-agent (narrowest specialist: docs/orchestration-rules.md § “Task-Type → Agent Routing”). Holds at ANY context level. Decide BEFORE the first tool call, not after N inline edits: name the specialist, or which exception applies.
Availability clause (stated ONCE, here): assumes Agent/Task; features.agentFanOut: false or a disabled tool makes this advisory — say so in the FIRST response of the turn. orchestration-rules.md and parallelize-batch-work.md cite this clause.
Standing authorization. Adopting this rule IS the operator’s standing request to use Agent/Task; do not ask per task or read a missing ask as a reason to stay inline. Deleting the rule is the opt-out. Scope: Agent/Task only, not Workflows or deep-research (explicit-request-only).
Keep inline
Section titled “Keep inline”The five named inline cases:
- Architecture / design judgment that needs the full accumulated context.
- Synthesis of sub-agent results.
- A sequential chain where step N needs step N-1’s full output.
- A patch under ~20 lines.
- A scoping read before fan-out: at most 2 files, or the plan README alone.
You decide at the margin. Claiming an exception names WHICH one AND why delegating would have lost necessary context; the label alone is not a justification. delegation-floor-gate.cjs is an advisory nudge: it names a specialist past a threshold, never blocks a call, and T1K_INLINE_OK=1 mutes it.
Full details
Section titled “Full details”docs/delegate-to-preserve-context.md. Silent under MR_SPAWNED=1, which is why this rule stays always-loaded: the only statement of the default a routed hop ever sees.