What Knowledge does
Reads a repository — even one no one fully understands — and models its entities, operations and dependencies.
Maps your APIs and databases into a clear model, so integrations and changes start from understanding.
Writes the architecture, decisions and APIs down — and keeps them in step as the software evolves.
Captures why things are the way they are, so context survives when people move on.
Ask “how does billing work?” and get an answer grounded in your actual code, not a stale wiki.
Sees how your systems change over time, so the picture is never out of date.
Knowledge that stays true
Point it at your codebase
See it understand and document software you already have.