audit-doctrine — Is the rule right, not merely enforced?

Degree of freedom: MIXED.

• Reference-practice comparison and remedy judgment (Phases 1–2): HIGH freedom — weigh each rule against how top products actually build.
• Governance-contract checks (Phases 3–4): LOW freedom — the contract's clauses are pass/fail; check each exactly.

Read-only. audit-gate-logic asks "can this gate be bypassed or gamed?" — it assumes the rule is correct. This asks the harder question: is the rule right on the merits? A ratchet that flawlessly enforces bad doctrine is worse than no ratchet, because greenness certifies the mistake and the developer, given only a codemod list, restyles legitimate work to appease a regex instead of fixing a real problem. An unexplained lint rejection erodes trust at that decision point until people "adopt their own truth." This audit finds the rules that are measuring taste, not correctness.