map-codebaselisted

# Map Codebase ## Purpose and authority Use compact repository knowledge to locate ownership, constraints, and impacts; verify every conclusion in current source. Never preload maps or all symbol shards. Medium confidence is not verified ownership, and missing or stale knowledge never blocks direct source inspection. Implicit invocation is read-only. Do not build, refresh, record analytics, modify repository knowledge guidance, or generate workflows without explicit write authority. ## Start Resolve `skill-root` to this directory and choose an external run directory: ```bash python /absolute/skill-root/scripts/cli.py --repo-root /absolute/repo \ --run-dir /absolute/run --input task="locate authentication ownership" \ --format json doctor ``` Run the returned `next_command.argv` with its returned `cwd`. Read only `required_reads`, verify their named source targets, and stop on every `blocking_reason`. ## Next-step loop 1. Resolve ownership first; stop when the owner and source contract are verified. 2. Run `next` only when the response names an unresolved constraint trigger. 3. Expand to impacts only when the constraints response names an impact trigger. 4. After an authorized coherent change set, refresh and validate knowledge. Use [Knowledge Contract](references/knowledge-contract.md) for freshness, scope, write authority, agent-document, and workflow rules. Use [Resolver Design](references/resolver-design.md) only for ranking or phase diagnosis, [Worked Resolv