Stale documents
The wiki was true in March. Nobody has opened it since. Keeping a knowledge base honest is everyone's job, which means it is nobody's, so the answers quietly rot and people stop trusting them.
Answered by Dreaming
SOLUTION · COMPANY BRAIN
Company Brain.
Your org already knows the answer. You just can't share it with anyone. Company Brain captures it, keeps it current, and hands it to whoever needs it next.
Built for
· live across ~100 engineers
· live across ~100 engineers
Why brains fail
Every company that tries this hits the same four walls. Everything below is built to answer them, in order.
Missing data
The decision that actually governs the work happened in a 1:1, a huddle or one engineer's Claude session. It never reached Jira or Confluence, so no search tool on the market can find it.
Answered by Notetaker
Permissions and privacy
Board decks, salaries and exec 1:1s cannot sit in one shared index that any engineer's agent can query. This is the objection that kills most rollouts, and it is a fair one.
Answered by Policy and JIT access
Your data ends up in their index
Most brains work by copying your systems into a vendor’s index. You inherit their permission model instead of your own, the sensitive half of the company stays out, and everything built on top has to be built by them.
Answered by pointers, not copies
How it grows
We never roll out a company-wide brain on day one. It earns its way up, the same way trust does. Pick a stage.
Starts with one engineer: their own commits, docs, tickets and decisions, turned into a brain only they use. Small enough to prove value in days, not quarters.
How the brain answers them
Three mechanisms, one for each failure we answer here.
DREAMING answers 01 · stale documents
It repairs itself overnight
Wikis rot because keeping them true is somebody's least favorite job. Company Brain runs that job as a nightly pass instead.
Overnight it de-duplicates pages, repairs broken citations, flags contradictions between sources, and re-weights what proved useful from the day's thumbs up and thumbs down. You wake up to a brain that is more correct than when you left it.
You sleep. It does the boring part.
...FIXED.
POLICY & JIT ACCESS answers 03 · permissions and privacy
Access granted the moment it is needed
The objection is correct: an agent with standing access to everything is a breach waiting to happen. So nothing here is standing.
When a request needs something outside what that person can already see, the team that owns it is asked, in the moment, by name, for that one request. Approve it and the access exists for that request and then expires.
Nobody files a ticket, and nobody gets handed the keys to the whole company so that one question can be answered.
The team that owns it decides, in the moment.
APPROVED.
NOTHING IS COPIED answers 04 · your data ends up in their index
Pointers, not copies
Company Brain stores pointers into your systems, not a duplicate of them, and resolves each one live against the permissions that person already has. The raw data never moves.
That is also why things can be built on top of it. Rooms, Notetaker and the ROI tool are three of ours; your own agents reach the same context over API, SDK or MCP.
Nothing is copied. Anything can be built on it.
What it did at Toka
- 50%more tickets shipped
- 37%fewer production bugs
Having a unified, permission-aware context layer was our missing pillar for AI enablement.
Moty Zaltsman CTO · Toka
Want this for your org?
One working session tells you whether Company Brain fits, and where you would start: individual, team, or company.