OzBrain for Teams
One brain behind every teammate's AI.
Share the company's decisions, plans, and research once. Keep them current. Push every agent to do more of the work, then write that work back so the next teammate has a record to trace.
Sharing is included on every plan. Teammates bring the AI they already use.
The current version is wherever someone last saved it.
Copies of the same plan sit in Drive, on laptops, in Downloads, in email. OzBrain puts the current article in front so every agent decides from the same file.
q3-plan.md
v1
Drive
q3-plan-old.md
v1
USB
q3-notes.md
v1
Notion export
q3-plan-copy.md
v1
Desktop
q3-plan-v1_1.md
v1.1
laptop
q3-plan (1).md
v1.1
Downloads
q3-plan-v2.md
v2
Downloads
q3-plan-FINAL.md
v2
Drive
q3-plan-FINAL-v2.md
v2
Slack
q3-plan-reviewed.md
v2
laptop
q3-plan-v2-draft.md
v2-draft
Q3_PLAN_v3.md
v3
iCloud
q3-plan.md
v1
Drive
q3-plan-old.md
v1
USB
q3-notes.md
v1
Notion export
q3-plan-copy.md
v1
Desktop
q3-plan-v1_1.md
v1.1
laptop
q3-plan (1).md
v1.1
Downloads
q3-plan-v2.md
v2
Downloads
q3-plan-FINAL.md
v2
Drive
q3-plan-FINAL-v2.md
v2
Slack
q3-plan-reviewed.md
v2
laptop
q3-plan-v2-draft.md
v2-draft
Q3_PLAN_v3.md
v3
iCloud
plans/q3
current
company brain
Company knowledge is locked inside each person's chats.
The engineer, the CEO, and the new hire each hold a private copy of the company. Plans go stale in folders. Work vanishes when the chat ends.
One brain every teammate's AI reads.
Without a shared brain
With OzBrain
Each teammate's AI holds a private copy of the company
Every teammate's AI reads the same company context
Plans go stale in Drive, Slack, and last week's doc
Freshness checks keep the current plan marked current
Ideas and facts sit in different folders
Linked articles hold one version of each fact
Agent work disappears when the chat ends
Staged writes leave a record the team can trace
New hires ask senior people for the same context
New hires ask their agent from the company brain
Knowledge leaves with tools and people
Company knowledge stays portable and owned
The jobs every team already has.
One shared context
Decisions, plans, and research live in the company brain. Each teammate's Claude, ChatGPT, or Cursor starts from that, not from whoever last explained it.
The live plan
Freshness checks mark what still holds. Yesterday's deck in a folder is not tomorrow's instruction.
A written trail
Agents do more of the work, then write it back. The next person can see what happened.
New hire
Why do we deploy this way?
The answer comes from the team's runbook and decision history, not an interruption.
How a team starts.
- 01fig. 1
Compile what the team already knows
Have an agent gather the decisions, research, playbooks, and context sitting in chats and folders, then write them into the company brain.
Routes toStaged write
Compile the team's decisions, plans, and research.
company-brain
routing index · current canon
- 02fig. 2
Invite with a role
Viewer reads. Commenter leaves notes. Editor proposes through staged writes. The owner controls membership.
company-brain · membership
- Viewerread
- Commenternotes
- Editorstaged writes
- 03fig. 3
Connect the AI each person already uses
Each teammate keeps Claude, ChatGPT, Cursor, or the surface they prefer. Their agents read the same brain. Writes follow the assigned role.
- Claude
- ChatGPT
- Cursor
company brain
Each person keeps their own AI
- 04fig. 4
Make agents write the work back
Every useful run leaves a versioned record. Freshness checks, conflict detection, and refactoring keep that record shaped for the next agent.
projects/q3-launch · history
- v14claude-code16:02
- v13chatgpt15:41
- v12cursor14:08
The brain improves as the team works.
A static wiki is most accurate on the day it is written. OzBrain keeps knowledge split so agents read only what they need, flags what went stale, and treats continuous maintenance as the designed behavior as agents update the brain.
- 01fig. 5a
Organizes for you
New knowledge finds the right article. You do not design a filing system; the brain routes each write where it belongs.
Routes toStaged write
Meridian scope closed. New retainer starts Monday.
clients/meridian
scope, current terms, contacts
- 02fig. 5b
Stays coherent
When a write disagrees with what the brain already holds, the write pauses and the conflict surfaces. Scheduled checks flag what went stale so agents know what to recheck.
decisions/pricing
PauseStaged write says $49/mo. Canon holds $29/mo.
Conflict surfaced · canon untouched
- 03fig. 5c
Shows who changed what
Every version records which agent wrote it and when. When agents run on their own, you can see what moved and catch what went off the rails.
projects/q3-launch · history
- v14claude-code16:02
- v13chatgpt15:41
- v12cursor14:08
- 04fig. 5d
Refactors as it grows
When an article gets too large for an agent to use well, the brain splits and reshapes it: refactoring, restructuring for clarity without changing what it says. More smaller articles means agents pull only what the task needs.
Splits intoarchitecture
~56k tokens · 221 KB
architecture/overview
stack, tenants, boundaries
architecture/deploy
envs, rollouts, rollback
Shared truth, not a shared dump.
Relevant context
Agents route to the articles the task needs, not a company-sized dump.
A trail on every change
Shared knowledge is versioned and attributed. Editors propose through staged writes, so one teammate cannot silently replace canon.
Your stack and your files stay yours
OzBrain sits behind the tools the team already uses. Articles remain markdown, portable when you leave.
What sharing compounds
Work written back is usable by every teammate's agent.
When an agent finishes a decision, a plan, or a piece of research, it writes that into the brain. The next teammate starts from that record. The trail stays attached.
Questions with real answers.
Why not use ChatGPT memory or Claude Projects?
Memory and Projects keep a partial picture inside one product. A teammate on Cursor never sees it. OzBrain sits under every agent, so the same company context shows up wherever the work happens. Read OzBrain vs ChatGPT Memory and OzBrain vs Claude Projects.
Does everyone need to use the same AI?
No. Each person connects the surface they already use. The brain is shared. The tools stay theirs.
What happens to personal notes?
Personal brains and the company brain sit side by side. Company context lives in the shared brain. Personal notes stay in the personal brain.
Can a teammate overwrite company knowledge?
Editors propose changes through staged writes. Shared knowledge is versioned and attributed, so one teammate cannot silently replace canon.
Do we have to move everything out of Notion, Drive, Slack, or GitHub?
No. OzBrain sits behind the tools you already use. Agents and the routines you already run can write what matters into the brain. Compare OzBrain vs Notion.
What can Viewers, Commenters, and Editors do?
Viewer reads. Commenter reads and leaves notes. Editor proposes changes through staged writes. The owner controls membership.
How does OzBrain keep shared knowledge fresh?
Articles carry freshness state. Automatic maintenance finds stale, duplicated, or contradictory material, and automatic refactoring keeps articles sized for agents. The team stops answering from last quarter's dump.
What happens when an article becomes too large for an agent's context window?
OzBrain splits oversized or mixed-subject articles into focused, linked articles. Agents retrieve the slice the task needs instead of a company-sized document.
How is sharing priced?
Sharing is included on every plan. Tiers differentiate on article count, not on who you invite. See pricing.