knowledge-lint

# Knowledge Lint > Substantive consistency checks on the compiled knowledge wiki. Produces `correspondence/internal-reviews/KNOWLEDGE-LINT-REPORT.md`. ## Output Path Per `rules/review-artefact-routing.md` (auto-loads in research projects (path-scoped to `paper-*/` and `paper/`)): - **Source slug:** `knowledge-lint` - **Write reports to:** `reviews/_project/knowledge-lint/YYYY-MM-DD-HHMM.md` inside the project. Path is relative to the research project root, not the Task-Management repo. - **Never** at project root (`./CRITIC-REPORT.md`-style filenames are forbidden — pre-rule layout). - **Idempotency:** if today's file exists, append a same-day descriptor (`{date}-revision.md`, `{date}-r2.md`, `{date}-pre-submission.md`) — never overwrite. - **Index update:** if `reviews/INDEX.md` exists, write a one-line entry under "Latest per source" pointing at the new file. Otherwise `review-recap` will rebuild the index next time it runs. - **Infrastructure repos** (Task-Management, atlas-workspace, etc.): this section does not apply — the path-scoped rule won't load there. ## When to Use - After running `compile-knowledge` to verify integrity - Before writing a paper section to check the knowledge base is solid - Periodically (monthly) to catch drift - When switching between projects to verify knowledge is current ## When NOT to Use - If no `knowledge/` directory exists — run `compile-knowledge` first - For structural project audits — use an installed research-project audit wor...