ark-explorelisted

# /ark-explore — Recon the real project (map only) **Contener · Guiar · Ordenar.** In plain words: contain the write, guide the next step, order leftover mess. This door is **Guiar**: map leftover design so you can order a messy tree. Do not apply. Skills never enforce — CLI / hooks / CI do. **When:** you need a map, leftover design work remains after imports look green, or one bounded decision needs 2–3 enforceable options. **Not when:** the user wants edits applied (`/ark-autopilot`) or session 0 (`/ark-adopt`). ## Steps 1. Read `arkgate-check --doctor`. 2. Open the real tree (≥12 files across ≥4 dirs). CLI JSON alone is incomplete. 3. Rank leftover work. Hand off to `/ark-autopilot` to apply one refactor. Do not write config or product code here. ## Checklist - Doctor #1: if ENFORCE + empty plan A and gates are already installed → **Shape** (`/ark-explore` then `/ark-autopilot`). Do not say install-agent-gates. - When `--require-gates` / adopted-strict is on and doctor JSON has `adrPresence`, the next step is a short note under `docs/adr/` (or `docs/decisions/`). Soft. Not every change. Off when require-gates is off. No `/ark-adr`. When `policyDelta` needs `--policy-ack` (weaken, new layer, or new allow edge), the ack must name that note as `adrPath` — a reason alone is not enough. - When doctor JSON has `statesTransitions` or `statusTransitionCatalog`, the next step is a short states → transitions table (or one link) on the domain doc already in play. Us