repo-wayfinder

# Repo Wayfinder Treat documentation as a **wayfinder**, not proof. A wayfinder earns its place by helping a task reach the source that owns the answer. Current behavior usually belongs to code, types, schemas, configuration, or another executable contract. Tests and driven probes verify that owner; they do not become a second owner. Default to a read-only diagnosis. Enter the apply branch only when the user explicitly asks to change files. ## 1. Pin the observation Read every applicable instruction file before judging the repository. Record: - repository root, branch, exact commit, and dirty paths; - the user-selected scope; - package or service boundaries; - the instruction chain that applies to each scoped directory. Preserve unrelated work. Treat an uncommitted tree as observable state, not as a reason to clean it. **Complete when:** the audit names the exact state and scope it is describing. ## 2. Inventory authority Use fast repository-native discovery such as `rg --files` and `git ls-files`. Include root and nested instruction files, READMEs, `docs/`, runbooks, protocol documents, decisions, proposals, measurements, generated references, and issue templates in scope. Assign every discovered document a primary role: - routing or agent instruction; - current contract; - operational runbook; - measurement or evidence; - decision or history; - proposal or bet; - generated reference; - unclassified. For each document, identify its **owning question**, audience, ...