ark-place

/ark-place — Where does this code go?

Contener · Guiar · Ordenar. In plain words: contain the write, guide the next step, order leftover mess. This door is Contener: write the new file in the right house. Skills never enforce — CLI / hooks / CI do.

When: you are adding a new file or artifact and need the layer, folder, and name. Not when: session 0 / config is missing or lying (/ark-adopt) or an existing violation cluster (/ark-autopilot).

Steps

1. CLI-first: if the local CLI already resolved the root, skip waiting on MCP. Identity is optional then.
2. Place with filePath required (ark_place or read ark.config.json + .ark/golden-pattern.json). Fail-closed without a path — never invent components/*.tsx or default to Presentation.
3. Write it there. Then arkgate-check.

Checklist

• filePath is known before the call. Description alone is not a path.
• Host write gate: prefer the installed pre-hook. MCP ark_prepare_write is fallback when that hook is missing or fail-open. Skills never enforce.
• Golden pattern is load-bearing when present. Adopt generates it.
• An included file that matches no layer is not a pass. The write gate denies it (CONFIG_UNCLASSIFIED_FILES). Place it in a layer folder, or send include/layer drift to /ark-adopt. Do not write into a loose include gap.
• Do not default a repository to Presentation.
• When doctor JSON has noDomainFrontend, the new file is a Domain rule — not another UI helper. Soft. Silent when Domain already has files or there is no frontend. No /ark-domain.
• When doctor JSON has prototypeShortcuts, the new file is a Persistence adapter or a Domain / auth-tag policy — not another SQLite / JSON-file store or admin literal in the page. Soft. Silent when those houses are absent or the shortcut is already in the right house. No /ark-prototype.
• When doctor JSON crossWallDuplication (status details, --doctor --all) lists a family, its destination is where the one shared copy goes: the declared shared root, the universe common folder, or the lower layer both sides may import. Write it there and import it from both sides — never a third copy, never a new allowedCrossSlice to reach across the wall. ask-place means pick a home both sides may import. Advisory. No /ark-dedupe.
• When the matched layer has layers[].description, print that caption next to the layer name and globs. Omit when absent — do not invent a caption or /ark-describe.
• When the matched layer has layers[].trustBoundary, print trust: <tag> next to the layer name and globs. Omit when absent — do not invent a tag or /ark-trust.
• When the matched layer has layers[].owners, print owner: @handle next to the layer name and globs. Omit when absent — do not invent a person or /ark-owners. When requireLayerOwners is on and the house has no owners, send that gap to /ark-adopt before writing.
• When ark_place / ark_prepare_write returns entrypoints or targetEntrypoints, import allowed layers through their listed public entrypoints (barrels/facades) rather than deep internal paths. When ark_prepare_write returns judgmentBrief.blueprint, use that TypeScript Port/valve/entrypoint skeleton to satisfy the boundary before writing.
• When arkRun is on: scaffold through the kernel (no new of managed types; declare uses / reactsTo / raises / sends; factory only in arkRun.kernelRoots, compositionRoots alias). Extra off → do not introduce the kernel. Enable it via /ark-adopt. Skills never enforce.
• When arkOrder is on: factory only in arkOrder.planeRoots; Domain stays plane-free; first freeze ξ with release(); later ξ is proposeRelease then apply. Extra off → do not introduce the plane. Enable it via /ark-adopt. Skills never enforce.