brooks-audit

1# Brooks-Lint — Architecture Audit
2 
3## Setup
4 
5Read in order:
6 
71. `../_shared/common.md` — Iron Law, Project Config, Report Template, Health Score
82. `../_shared/source-coverage.md` — book coverage, exceptions, tradeoffs
93. `../_shared/decay-risks.md` — symptom definitions and source attributions
104. `architecture-guide.md` (this directory) — the audit framework
11 
12## Process
13 
14**Onboarding mode:** If the user asks for an onboarding report, codebase tour, or
15"explain this codebase to a new developer", read `onboarding-guide.md` from this
16directory and follow it instead of `architecture-guide.md`. This mode explains rather
17than diagnoses — no Health Score, no Iron Law findings.
18 
19**Scope:** if the user did not specify files or a directory, apply Auto Scope Detection
20(`../_shared/common.md`) first.
21 
221. Gather codebase context and draw the module dependency graph as Mermaid (Steps 0–1 of the guide)
232. Scan for each decay risk in the order specified (Steps 2–4 of the guide)
243. Assign node colors in the Mermaid diagram based on findings (red/yellow/green) — after Step 4
254. Run the Testability Seam Assessment (Step 5 of the guide)
265. Run the Conway's Law check (Step 6 of the guide)
276. Output using the Report Template from common.md — Mermaid graph FIRST, then Findings
28 
29**Mode line in report:** `Architecture Audit`