Approved, not merely stored
A decision enters the record through a proposal and a publisher. A document in a folder is just a document.
Company Brain is the same working truth, scoped. Company-level decisions, project state and client material live in one governed record, and each agent, in each role, receives only the part its task is allowed to use.
The difference
Teams already share documents. What they do not share is a maintained answer to: what is decided, what is open, what was rejected, and how we work. Company Brain keeps that answer current and gives each agent the scoped part.
A decision enters the record through a proposal and a publisher. A document in a folder is just a document.
Scopes shape what gets compiled into a task, not only what a user can open. The GTM agent never sees code conventions because they are irrelevant, not because they are secret.
Session outcomes, corrections and proposals keep the record current. Nobody owns a wiki-gardening rota.
The record is Markdown with provenance. It can be exported and read without Unforgetter.
Three scopes
Scopes nest. Company-wide policies and preferences apply everywhere. Project scopes hold decisions and open threads for one piece of work. Client scopes hold material that must never cross into another client's task.
| Scope | Holds | Who typically receives it | Enforcement |
|---|---|---|---|
| Company | Policies, writing rules, positioning decisions, protected goals | Every role, every agent | Compiled into all bundles; protected targets cannot be changed by agents |
| Project | Decisions, open threads, rejected proposals, conventions for one piece of work | The roles working on that project | Token catalogue lists allowed projects; selection cannot widen authority |
| Client | Briefs, agreed methods, open questions for one client | Only tasks for that client | Designed to be unlistable and unretrievable from other scopes; continuous cross-tenant tests are an alpha gate |
Three roles, one record
Pick a role. The record does not change; the slice that reaches the agent does. Withheld items are shown so the boundary is visible, not silent.
Shared methods
Methods are instruction-only skills: how you write, how you review, what a research standard is. They are versioned in the same record, scoped like everything else, and compiled into any agent's bundle when the task calls for them.
Applies to every customer-facing draft from any agent.
Applies to every coding agent in the project scope.
Applies to every research task, whichever agent runs it.
Proposals, review, audit
A bounded change with actor, scope, evidence and the record it would supersede.
Scope, protected targets, conflicts and taint are checked. Untrusted evidence raises scrutiny and can never lower it.
The approved state is compiled. Every agent's next context request returns it.
Who proposed, who approved, what changed, when. Metadata and digests, not raw secrets.
Boundaries
The alpha admits single-owner workspaces. Membership, invitations and roles are in build.
Tenant isolation is specified with adversarial tests as its gate. It is not claimed until that gate passes.
Sources are allowlisted Markdown and structured proposals. Broad app connectors are not the wedge.
Evidence is collected from day one. No badge is shown until an audit exists.
If your agents work across projects or clients, Company Brain is the part of the alpha we most want to test with you.