ark-adoptlisted

# /ark-adopt — Mark the path (session 0) **Contener · Guiar · Ordenar.** In plain words: contain the write, guide the next step, order leftover mess. This door is **Contener**: write the path so the tree has honest houses. Skills never enforce — CLI / hooks / CI do. **When:** empty tree, or the rules file does not match the real folders (session 0). **Not when:** a single new file (`/ark-place`) or leftover design after the path is honest (`/ark-explore` then `/ark-autopilot`). ## Steps 1. Read `arkgate-check --doctor` (one light, one next action). 2. Write `ark.config.json` (and a baseline only for genuine debt) in this turn. 3. Re-run doctor. Day-to-day new files: `/ark-place`. ## Checklist - Existing tree: propose **SharedKernel** (types/constants) + **CompositionRoot** (wiring) + `src/**/domain/**`. Never dump bare `src/lib/**` into Application. - Generate `.ark/golden-pattern.json` (load-bearing for `/ark-place`). - Future houses: mark unused layer globs `reserved` / `allowEmpty` so `--strict-config` does not fail. - When the product map or glossary names a house, write `layers[].description` as app-context copy (what this folder is *in the product*). Compact starter may omit. Do not invent captions. Do not invent `/ark-describe`. - CLI-first: if `arkgate-check` already resolved the root, do not wait on MCP. - Do not add `arkRun` or `arkOrder` unless the user wants that extra. When they do, write **advisory** extra in this turn (`arkRun` schema `1.2+`; `arkOr