ark-explainlisted

# /ark-explain — Understand this project's architecture **Contener · Guiar · Ordenar.** In plain words: contain the write, guide the next step, order leftover mess. This door is **Guiar**: teach the path in plain language. Skills never enforce — CLI / hooks / CI do. **Not a first-run door.** Teach / HTML tour only. Session 0 → **`/ark-adopt`**. Map → **`/ark-explore`**. Apply → **`/ark-autopilot`**. Wire ArkRun → **`/ark-runtime`**. Wire ArkOrder → **`/ark-order`**. The user wants to understand the architecture, a specific rule, or why the gate blocked them. ## Improvement compass (process preflight) When doctor is available, read `doctor.improvementCompass` (or the human **Improvement compass** section). Name 1–3 **residual** lenses in plain language before skill-shopping. Always `notAScore` — never invent 0–10 scores or Excellent/Good ranks. **What the user should feel next:** fewer blocked AI writes, clearer folders, safer domain — then jargon. **Anti false-done:** empty plan A + residual lenses / design-weak → **Incomplete? yes**. Green edges alone are not “architecture finished.” **AI-easy architecture:** ports over concrete I/O in domain; one concern per module; golden pattern for new files; place before write (`/ark-place` / prepare-write). **Out of scope (honest):** scalability/performance, full app-security tooling (SAST), and full resilience patterns are **out-of-scope** lenses — say so; do not invent Ark enforcement for them. **Tour by lenses** (teach, no