Swarm Pi Discover

---
name: swarm-pi-discover
description: Investigate unknown requirements or unresolved technical claims through Pi's fixed research, experiment, and convergence sequence. Use when reproducible evidence and Human Decision gates are required; route one answer to ask and evidence-ready design to plan.
compatibility: Requires Node.js 22.19+, local shell command execution, and first-run npm registry access with a writable plugin directory; mutation workflows also require Git.
---

# Discover With Pi

Follow the [Skill Control Loop](../../references/skill-control-loop.md) and read
the [Discovery Addendum](../../references/host-protocol-discovery.md). Load
[Resource-Aware Execution](../../references/resource-aware-execution.md) before
the experiment's expensive or recursive commands.

1. Write a self-contained discovery brief with unknowns, constraints, evidence
   acceptance criteria, freshness, user gates, and a sequential experiment
   plan.
2. Run `$RUNNER discover --host "$HOST" --role analyst --prompt-file "$PROMPT_FILE" --execution-mode supervised --approval-mode "$APPROVAL_MODE" --json`.
3. Continue every approval, gate, Host Assistance request, or timeout through the
   control loop. Host-first review stays inside the snapshotted scope and exact
   receipt ceiling.
4. Require all three schema gates: research Evidence Plan; experiment micro-SDLC;
   definition and convergence. The experiment contract includes hypothesis,
   control, locked dependencies, fixture, seed or data hash, exact sequential
   commands, metrics, tolerance, evidence, tests, cleanup, and reported clean
   replay.
5. Complete only when the result is `supported`, `refuted`, or `inconclusive`
   and includes all three stage reports plus a final gate decision. Every
   experiment artifact remains `deliverable: false`; an approved result may
   enter plan through `--discovery-from <job-id>`.

Every stage inherits the immutable Job policy. Research, convergence, and Advisor
use fresh read-only stage Sandboxes; the isolated experimenter child owns and
disposes its Sandbox through the shared Adaptive network authorizer. The parent
holds no writer lease.