Your company already wrote the runbook.Brain compiles it.
Brain reads the Slack threads, pull requests and tickets where your team’s real procedures live — and distills them into provenance-backed Skills your AI agents can run. Any agent. Any model. Served over MCP.
7
Source connectors at launch
5
Extractors working every cluster in parallel
9
Pipeline stages, raw event to skill
0
Agents locked in — any MCP client
The knowledge exists. It just sank.
The procedures that actually run your company were never written down as procedures. They happened — in threads, reviews and tickets — and then the scroll swallowed them.
Slack · six months ago
The OOM fix is in a thread from December.
Someone solved it, someone thanked them, and it sank. The next incident starts from zero.
Tribal knowledge
The deploy checklist lives in one engineer’s head.
The real procedure is whatever the last person who ran it remembers. When they’re on holiday, so is the process.
Agents today
Your agent confidently invents a process.
Agents are trained on the internet, not on your company. Without your history they guess — fluently, plausibly, wrong.
Onboarding
Every new hire re-derives everything.
Months of asking around to reconstruct knowledge the organization already paid to learn once.
Connect. Distill. Serve.
Read-only ingestion in, portable skills out. Click a stage — the instrument follows.
Same agent. Same question. One has your history.
payments-service is OOMing in prod — what do I do?
Here are some general steps you can try:
- Check the application logs for errors.
- Restart the affected pods.
- Consider increasing the memory limits.
- Review recent deployments for changes.
- Monitor the service after restarting.
If the issue persists, consult your team’s documentation.
payments-service is OOMing in prod — what do I do?
Running your team’s runbook for this exact failure:
- Check the processor status page first — upstream degradation causes the retry pile-up.
- Drain the retry queue: payments-cli queue drain --older-than 1h
- Scale to 6 pods while the queue clears.
- If memory isn’t stable in 15 min, escalate to the payments on-call lead.
Nothing ships without its sources.
Every Skill carries the event IDs it was distilled from, a confidence score and an extraction timestamp — so a reviewer, an auditor, or the agent itself can walk any instruction back to the conversation it came from.
- 1Check the processor status page first.
- 2Drain the retry queue, oldest hour first.
- 3Scale to 6 pods while the queue clears.
- 4Not stable in 15 min → escalate to on-call lead.
Hover a step — its source events light up.
Plugged into where work happens.
Seven sources at launch, more behind one interface: a connector is a single contract — list resources, fetch events. Adding yours is an afternoon, not an integration project.
Three front doors. One brain.
On-call that remembers every incident you ever resolved.
payments-oom-runbook
The fix that worked, as a procedure: drain the retry queue, scale, escalate — with the thresholds your team actually used.
31 eventsdeploy-checklist
The real order of operations, including the migration gate nobody ever wrote down.
24 eventscode-review-norms
What your senior reviewers actually enforce, distilled from a year of review comments.
41 eventsConnectors — GitHub · Jira · Slack · PagerDuty
Policy answers that cite the policy — and the exception thread.
refund-escalation-policy
Thresholds, who approves above them, and the carve-outs agreed in DMs that never reached the wiki.
18 eventssev1-comms-template
Who to page, what to say, and when — the way your best incident manager runs it.
15 eventsmacro-tone-rules
House style for hard messages, learned from the replies that de-escalated.
9 eventsConnectors — Zendesk · Intercom · Slack · Gmail
Every client’s playbook, on tap for every account team.
client-onboarding-flow
Kickoff to first post: the sequence, the owners, the assets — per client, not in someone’s head.
12 eventsbrand-voice-rules
The words each brand never uses, distilled from every approval round you’ve survived.
9 eventscampaign-approval-chain
Who signs off, in what order, and what unblocks a stall — per account.
7 eventsConnectors — ClickUp · Notion · Slack · Gmail
Glean helps your people find answers.Brain teaches your agents how your company works.
Where Brain sits
Give your agents a memory.
Early tenants get white-glove connector setup and a distilled skill library from their first six months of history.