ark-explore

/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. Use catalog names when present. Soft. Silent when that doc is absent or Domain has no status vocabulary. No /ark-states. Do not invent states.
• When doctor JSON has noDomainFrontend, Domain is empty and the UI holds the rules. Next: one Domain file (/ark-place) then one small refactor (/ark-autopilot). Soft. Silent when there is no frontend or Domain already has files. No /ark-domain. Do not invent a Domain house.
• When doctor JSON has prototypeShortcuts, SQLite / a JSON-file store is standing in for Persistence, or admin / god-mode literals sit outside Domain (or an auth tag). Next: one Persistence adapter or Domain policy file (/ark-place) then one small refactor (/ark-autopilot). Soft. Silent when those houses are absent, the shortcut is already in the right house, or there are no such markers. No /ark-prototype. Do not invent a Persistence house.
• When the tree is adopted and doctor JSON has invariantTestsPath (or the check names INVARIANT_TESTS_PATH_MISSING), the next step is coverage.testGlobs or coverage.coverageRoots on a real tests folder. Fail-closed. Silent when not adopted, the catalog is empty, or every invariant sets coverage.test false. Handoff /ark-adopt to write the path. No new skill.
• When any invariant is enforced and doctor JSON has invariantCoverageRoots (or the check names INVARIANT_COVERAGE_ROOTS_MISSING), the next step is coverage.coverageRoots on the folder the test runner uses. Fail-closed. testGlobs alone is not enough. Silent when no invariant is enforced. Handoff /ark-adopt to write the roots. No new skill.
• When an invariant declares coverage.symbol, read the witness path (symbolEvidenceFile) and the discard line on doctor and --rules-inventory, including when the run is green. A declaration in a non-test file is not “the tests pass” — ArkGate never runs tests. Depth and byte caps stay internal; the counts are what you read.
• When doctor JSON has orphanModules with files listed, map them: nothing imports each file and no entry point covers it. Read certainty — maybe-dynamic and maybe-unresolved may still be loaded (open what the evidence names). A partial section is never a complete list. --doctor --all adds exports nothing imports by name. Map only; deleting is /ark-fix, one file at a time. A framework or loader ArkGate does not know goes in .ark/entry-points.json with a reason. Never say "dead code". No new skill.
• A doctor green / Healthy line must name a file, config key, or test. Uncited green is a lie — treat it as unfinished. No /ark-cite.
• Distinguish missing skills vs stale catalog. Installed ≠ stale.
• Hook green is not tree green (scripted edits bypass PreToolUse).
• Bug / false green / false red / missing doc / improvable behavior in ArkGate itself → draft one upstream GitHub issue (pedroknigge/arkgate or the installed package repository.url), ask the human to confirm send, then gh issue create. Never auto-file. Never file ArkGate defects on the consumer product repo.