crewlisted

# Crew `/crew <run-dir>` runs the tickets of the run directory `/route` staged, unattended, and hands back an integration branch to review. Typing it is the run's whole sign-off: the wave table the driver validates from each ticket's `## Routing` section is the sole routing authority ([ADR-0003](../../docs/adr/0003-script-composed-first-turns-wave-table-authority.md)). Your work is judgment: rule on what a child asks, and on what the driver's rule table has no row for. The driver runs the rest — preflight, dispatch, receipts, settlement, merges, tracker closes, advancement, the report — as a background task of this session, costing you no turn while it works ([ADR-0010](../../docs/adr/0010-the-driver-runs-the-run-the-coordinator-rules.md)). ## Contract **Reversibility is the authority boundary.** You may approve any reversible action, including production, remote, deployment and external-service changes, and must record an action's exact undo inside the ruling that approves it. An action with no credible undo is **parked** for the human. The red-line hook blocks known destructive command shapes; this rule stands where the hook misses. **You rule from what a message shows you.** The run's files — the wave table, the machine log, a child's diff, a worktree — stay closed, and nothing puts them in front of you. A message lacking what a ruling needs is answered by asking its sender for exactly what it lacks. **Product code belongs to a child**, merge-conflict resolution incl