slipway-codebase-mappinglisted

# Codebase Mapping ## Purpose Map repository architecture, dependency graphs, key abstractions, and module boundaries before planning. This technique produces durable context for research, scope confirmation, and plan audit; it does not own a governed route. ## When This Runs Advisory hint during discovery or governed spec bundling within `S1_PLAN`. This is a technique skill — it does not produce governance evidence and missing output does not block any gate. ## Durable Output Contract Resolve the canonical map paths from `slipway codebase-map --json` — read `codebase_map_dir`, `codebase_map_docs`, `status`, and `doc_states`. (During standalone discovery `slipway next --json` returns `no_active_change`; only *inside* an active change can you instead read `input_context.codebase_map_dir`/`input_context.codebase_map_docs` from `slipway next --json`.) The path fields are: - `codebase_map_dir` - `codebase_map_docs` Write a durable brownfield map under `artifacts/codebase/` using this fixed document set: - `STACK.md` - `INTEGRATIONS.md` - `ARCHITECTURE.md` - `STRUCTURE.md` - `CONVENTIONS.md` - `TESTING.md` - `CONCERNS.md` These documents are advisory but canonical. Downstream skills consume them by path instead of relying on transient chat context. Before authoring each doc, read its authoring contract with `slipway instructions <doc> --json` (e.g. `slipway instructions architecture --json`; both the key `architecture` and the file name `ARCHITECTURE.md` resolve). It returns