# Exploitation Stage — Execution

## Per-unit baton (`attack-strategist → exploit-developer → exploit-reviewer → attack-operator → verifier`)

This stage uses the architecture §3.5 pattern: plan-do-verify front loop, then an adversarial-execution step, then a terminal verify. Each unit walks the chain in order; the baton is the unit's accumulated body content:

1. **`attack-strategist` (plan):** chooses the targeted vulnerability on this attack surface, picks the lowest-blast-radius technique that demonstrates impact, defines the success criterion as a concrete observable, and confirms scope. Hands off with `## Attack Plan`.
2. **`exploit-developer` (do):** builds the controlled PoC against a surrogate environment, adds safety constraints (kill switch, rate limit, payload-size cap, cleanup procedure), defines pre-flight checks. Hands off with `## Proof-of-Concept`.
3. **`exploit-reviewer` (verify):** body-only review — PoC matches the plan, scope adherence is explicit, safety constraints are concrete, surrogate test ran, decisions are honored. Advances on pass, rejects on fail.
4. **`attack-operator` (adversarial-do):** runs the pre-flight, executes the PoC against the authorized target step-by-step with timestamps, watches for unintended side effects, captures evidence, confirms cleanup. Aborts on any unexpected condition.
5. **`verifier` (adversarial-verify):** terminal validator — scope was respected, evidence was captured, no destruction occurred, methodology is reproducible.

## After execute completes

When every unit's hat chain has terminal-advanced:

1. **Spec review** — universal hard gate.
2. **Quality review** — the stage's `scope-compliance` review agent fires (strict interpretation). Scope-compliance findings are always highest-priority — they shift engagement liability.
3. **Fix loop** — `[classifier, exploit-developer, feedback-assessor]` dispatches per finding. `exploit-developer` is the implementer because most findings ask for safer PoCs, tighter pre-flights, or missing rollbacks.
4. **Gate** — `ask`. A human MUST sign off before any exploit attempt against a real target.
