The codebase explains itself on the way out

The new hire reads the codebase through hoody-files URLs, like everyone. Hers explain themselves.

A hook on the files service catches reads of source files. It fetches the file, asks a model through the AI gateway for a short header: what this module does, what calls it, what to be careful of: prepends it as a comment block, and caches the annotation. The first read of a file takes a beat longer; every later read is instant.

The repo on disk is untouched; git sees nothing. The explanation is generated from the code as it is today, not the wiki page from two refactors ago.

The documentation isn't in the repo; it's in the read path.