Docs
Documentation generated from the graph — always in sync with the code it describes.
The docs source contains documentation generated from the graph — not from the source files directly, but from the typed structure the graph has already verified.
What it contains
- Module docs — generated descriptions of modules, their exports, and their responsibilities.
- Symbol docs — generated descriptions of functions, classes, and interfaces, including their call paths and dependencies.
- Architecture docs — higher-level descriptions of how modules relate, which services depend on which, and where the system boundaries are.
How it stays in sync
Documentation is regenerated when the graph changes. Because it is derived from the graph rather than authored by hand, it cannot drift from the code. If a function is renamed, the docs reflect the new name on the next sync.
Why not just read the code?
Code answers "what does this do?" line by line. Graph-generated docs answer "what is this module's role in the system?" and "what depends on this?" — questions that require cross-file, cross-source context a single file cannot provide.
Searching the docs source is useful when the question is conceptual rather than structural: "how does authentication work in this project?" returns generated docs that summarize the auth module's role, rather than individual symbols.
Next: Company docs.