knowledge

# The knowledge base `kb` is on your PATH. It reads a folder of markdown notes — `knowledge/` in the workspace unless `$KB_FOLDER` says otherwise — where every note is a **thing** and every link is a **connection between things**. ```sh kb find "ada" # search names, header facts and prose kb read "Ada Lovelace" # the note, its facts, and its links both ways kb list --type decision # everything of one kind kb find --linked-to Intentic # everything connected to one thing kb links "Ada Lovelace" # just the connections kb graph Intentic --depth 2 # the neighbourhood, as a map kb check # broken links, orphans, vocabulary drift kb vocab # the kinds and relationships this knowledge base has adopted ``` Add `--json` to any of them. Exit 0 found something, 1 found nothing, 2 could not run. ## When to read it **Before answering a question about the owner's world.** Who someone is, what a project is, what an internal word means, what was decided about something and why, how two things relate. One `kb find` costs a second and is the difference between an answer grounded in what this owner actually told you and a plausible invention. Start with `kb find <the words in the question>`. If it lands on a note, `kb read` it and follow the links that matter — the connections are the point, and the neighbouring note is usually where the answer actually is. **Not f...