Documentation is a promise. A docstring says: "This function takes these inputs, does this thing, and returns this." The problem is that promises are easy to break — and nobody enforces them. I've been on teams where the docs were accurate on day one and completely wrong six months later. Not because engineers are careless. Just because there's no system that notices when code and docs diverge. I built Wright AI to fix this. It does two things: Generate docstrings automatically, for your whole codebase Detect drift — flag the docs that have become lies Here's how both work. The generation side Most docstring generators just describe the function body. Wright reads the call graph first. It uses Tree-sitter to parse your AST, then builds a NetworkX dependency graph weighted by PageRank. When generating a docstring for processPayment() , it doesn't just read that function — it reads what calls it, what it calls, and what those callees do.…