Verifying Modules

It scans your directory structure and flags missing documentation, runs automatically after you create new modules, and treats docs as delivery blockers, not nice-to-haves. The philosophy is straightforward: if another developer can't understand your module independently, it's not done. It distinguishes between user-facing README (what and how) and maintainer-facing DESIGN (why and tradeoffs), with exemptions for generated code and config-only modules. The "later" excuse doesn't fly here. You either document your decisions now or you don't merge.