Your company brain will leak secrets: how we stopped it for big banks — Tanmai Gopal, PromptQL

Tanmai Gopal plotted the daily edits to his own company brain expecting the usual shape, a burst of enthusiasm followed by neglect. The line kept climbing instead, and it surprised him. His reading is that a system people trust gets taught more, not less: teach it to query the data, then to interpret the result, then to act on it, and each skill adds its own steady rate of correction on top. A rising edit count is what health looks like. Gopal cofounded PromptQL and before that built the Hasura GraphQL engine, and his team spent a year deploying an early company brain across 15 to 20 organizations, from AI native startups to Fortune 100 banks. Their own brain runs to about 5,000 interconnected pages. The obstacle is that a shared brain leaks. He dismisses two common answers before offering his. Nobody writes shared skills in GitHub for a colleague they have never met, and a team brain that saves its own memory is just a fresh silo, the same trap as per channel memory. His third option puts everything in one companywide wiki of linked markdown files, scopes read and write access per file, and refuses to let the agent write on its own. The agent proposes the facts and the scopes; a person accepts, and their name goes on the change so a leak has an owner. For the multiplayer case, where several people debug an incident together and the argument itself produces the best knowledge, credentials never sit in the sandbox. They are injected per user at the HTTP and SQL layers. Timestamps: 0:00 - Why company brains leak, and what holds deployment back 1:06 - From the Hasura GraphQL engine to PromptQL 2:03 - Three kinds of customer, from startups to banks 3:14 - Modeling the brain, and 5,000 linked pages 3:41 - A poll: what does a healthy edit curve look like 5:16 - The line that kept climbing 6:37 - Two use cases, personal recall and shared work 9:50 - Grow one, do not build one 11:09 - A security questionnaire answered end to end 12:33 - Why nobody writes shared skills in GitHub 13:52 - Why a team brain is just another silo 14:59 - One wiki, scoped files, and no silent writes 18:45 - Every change carries a human name 20:06 - The multiplayer case, where the argument is the knowledge 23:17 - Privilege escalation, and credentials outside the sandbox