Your docs, decisions, and processes in a knowledge base that answers questions and keeps itself current.



Docs, decisions, processes, and the context that never made it out of someone's head — collected into a single workspace your team can actually search.
Ask in plain language and get a direct answer with its sources attached, so you can check where it came from before you act on it.
Agents watch the tools you already use, fold in what changed, and flag anything that has gone stale instead of quietly going out of date.
Knowledge bases rot because keeping them current is nobody's job. Here it is three agents' whole job.
The one your team talks to. Reads across the whole knowledge base and answers with citations back to the source document.
Turns meeting notes, threads, and uploads into clean, structured entries filed where they belong.
Runs on a schedule to find duplicates, contradictions, and pages nobody has touched in a year, then flags them for review.
Every agent, instruction, skill, and starter file is open to inspect before you create a workspace.
# Workspace This workspace is the company brain. The pages under /brain/ are the knowledge; the tables are the machinery that keeps them honest. - /brain/SETUP.md — table schema and the one-time setup checklist. - /brain/CONVENTIONS.md — page anatomy and the contract every agent follows. - /brain/TAXONOMY.md — the areas knowledge is filed under. Expect to edit this often. - /brain/INTAKE.md — how material gets in. Rewritten by setup with real ids. ## The operating rule An answer is a claim, its source, and its age. No source, no answer — the question becomes a logged gap instead. A confident stale answer is the one failure that costs more than saying nothing, because the person who receives it
Point it at what you already have and let it start answering.