Why

Read the pstack-t3 runtime before spawning workers, choosing models, scheduling, or isolating work. It maps those steps onto T3's orchestrator tools.

Investigate the motivation and intent behind code. The companion how skill answers what the code does and how it works. why answers what forces led to its shape.

Each spawn below names a role. Resolve its seat per the runtime's Roles section and spawn with delegate_task. Omit target for an inherit seat. If T3 rejects a target, fall back per the runtime and say which seat changed. Pass the seat the role this step names, per the Subagents section of the poteto-mode skill.

The runtime's Modes section sets the mode lines of every brief this skill writes and how its spawns run in light mode.

Every spawn is delegate_task with role: "research" and a read-only brief that says "Do not edit files, commit, or push." Do not lower the child's runtime mode to strip tools. The MCP-backed investigators and the synthesizer's citation spot-checks need their MCP tools, so the brief carries the read-only constraint.

Operating Posture

Operate as a careful, cautious, and precise investigator. Be honest about what you know vs what you're inferring. Read references/epistemics.md for the full confidence framework and phrasing guide. The synthesizer must follow it.

Step 1. Understand the Target and the Question

The target is usually a chunk of code, a pattern, a feature, or a named design decision. The question is usually a design rationale, a tradeoff, a motivating edge case, an external constraint, dead code, or a broad history sweep.