The Team Brain

When nodes connect into a mesh · for IT Pros · BAs · architects · testers · DBAs · support · tech writers.

// T01 of the Team Brain track · this page is the canonical entry point. Originally shipped as Module 02 of the Second Brain series — same content, now anchored to its dedicated track. See all five Team Brain modules →

Your Personal Knowledge Database keeps your AI primed on your work. But your teammate has their own node. Every cross-team conversation starts from zero because nobody is reading anyone else's context.

A Team Brain is the shared layer. Four files. One folder. Lives where your team already works — a Git repo, Drive, SharePoint, Notion, or a shared Project. Every teammate loads it alongside their own node, and their AI knows what the team knows. Runs three ways:

On a shared drive — files in Git or a synced folder; each teammate's filesystem agent reads them locally. Best for: Claude Code, Cursor, Windsurf, Copilot Agent.
In a shared Project — provider's team-Project feature; files persist for everyone with access. Best for: Claude Team, ChatGPT Team Projects, NotebookLM, M365 Copilot.
In any chat with a shared link — files in Drive/Notion/SharePoint; each person attaches the relevant subset to their session. No team plan required.

10-minute onboarding for new hires. 15-minute Friday sync to keep it current.