Audit Your Docs Against The Decision-System Framework

Audit Your Docs Against the Decision-System Framework Most documentation fails not because something is missing, but because it answers the wrong question. We've built encyclopedias when people need guides. We've cataloged every possible path when what readers actually need is someone to say: start here, this way works. The result is what I call the library paradox. All the information exists, users just can't find their way to the answer that matters for their specific situation at this specific moment. The problem isn't missing information. The problem is missing navigation. doc-audit is a CLI tool that operationalizes this. It scans your markdown files, classifies each one by decision phase, scores how well it guides a reader toward action, and gives you a prioritized list of what to fix. This post walks through how to use it and how to think about what it's telling you. The framework Every person who arrives at your documentation is standing at a crossroads. They're not asking "wha