The Problem
Documentation diverges from code the moment it's written. Not eventually — immediately. There's no trigger anywhere in a typical stack that says "this code changed, go check if the doc describing it is still true."
Six months later, that doc isn't just outdated. It's actively misleading, and nobody's the wiser until someone follows it and gets burned.
Architecture: Docs as First-Class Graph Nodes
The fix isn't "write better docs" or "review docs more often" — that doesn't scale and everyone already knows it. The fix is architectural: treat documentation as nodes in the same graph as your code, connected by real edges.
