Context Audit

Treat this as an attention audit, not a line-count diet. Splitting a lean file into unreachable indirection is a regression.

Target shape

Judge against this default: always-loaded files form a minimal skeleton — the project's general rules plus a routing table — and every other truth lives in exactly one on-demand owner the project has earned, not a template file list. The environment (code, config, directory layout, --help output) owns what it can show; a doc restating it is a cache. Slim never at the cost of reach: a mandatory rule keeps a deterministic path into context. A repo that deviates deliberately wins — flag the deviation once and audit within its convention.

Process

Two phases. Phase 1 ends in a verdict the user can accept or redirect in one reading; phase 2 runs only after the user has chosen a direction.