drift-check

# Drift Check Audit a set of project documents — specs, planning docs, READMEs, rules files, system prompts, task trackers — for two failures: **contradiction** (the docs disagree with each other) and **drift** (the docs have wandered from the mission they claim to serve). The output the user needs is an honest map of where their materials actually stand, not reassurance. ## Core principle: clean alignment is a smell The dangerous failure mode here is the opposite of harsh — it's being agreeable. A document set that audits to "98% aligned, all green" is not evidence of health; it's usually evidence that nobody looked hard. Real document sets that evolved over time accumulate contradictions, stale references, and quiet redefinitions. If your audit comes back glowing, you didn't dig — go back and find the contradiction the rosy summary is papering over. Two things in particular masquerade as alignment: - **Identical claims are not corroboration.** When the same metric (`>95% accuracy`, `<2 seconds`) or the same sentence appears verbatim across five documents, that is copy-paste, not five independent validations. It tells you the number propagated, not that it's right or achievable. - **Unfalsifiable promises aren't aligned, they're just vague.** "Perfect memory", "seamless orchestration", ">95% accuracy" with no measurement defined — these agree across docs only because none of them mean anything checkable yet. ## Workflow ### 1. Anchor the north star Find the stated mis...