# One truth for the company. A different slice for every role. Company Brain. 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. - Scopes: working now - Roles and team isolation: prototype - Not a shared folder Canonical: https://unforgetter.com/company-brain ## A shared record of what applies, not a shared drive of everything. 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. - **Approved, not merely stored**: A decision enters the record through a proposal and a publisher. A document in a folder is just a document. - **Scoped, not just permissioned**: 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. - **Maintained, not curated by hand**: Session outcomes, corrections and proposals keep the record current. Nobody owns a wiki-gardening rota. - **Portable, not locked in**: The record is Markdown with provenance. It can be exported and read without Unforgetter. ## Company, project, client. 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 | ## Same working truth. Three different task bundles. 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. Founder (Claude, task: Prepare the investor update) receives: Company: Pricing is not public until the alpha closes (Company scope · decision 14 Aug); Project: Booking product: fee rule shipped, capacity split open (Project scope · compiled 26 Aug); Method: Updates state what is unfinished (Company writing rule); Withheld: Client margin notes (Client scope · not in this role's catalogue). Builder (Codex, task: Ship the cancellation fee change) receives: Project: Fee measures against the original booking date (Project scope · supersedes 22 July draft); Project: Capacity split unresolved (Do not implement around it); Method: Money in minor units, never floats (Engineering convention); Withheld: Investor material and pricing discussion (Company scope · not needed for this task). GTM agent (Grok Bot, task: Draft outreach for the private alpha) receives: Company: Customer copy never implies a price (Company policy · protected); Method: Plain sentences, no superlatives, no invented numbers (Writing method); Project: Alpha results are not final (Quote nothing as measured); Withheld: Repository decisions and code conventions (Project scope · irrelevant to outreach). > In build. Prototype. Server-enforced project scopes work now with one owner. Named roles, per-member permissions and team isolation are specified and in build; they are shown here so you can judge the model, not as a live feature. ## Ways of working travel with the record. 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. - **Writing · Plain sentences, no superlatives, say what is unfinished**: Applies to every customer-facing draft from any agent. - **Engineering · Money in minor units; never implement around an open thread**: Applies to every coding agent in the project scope. - **Research · Three independent sources minimum, each cited**: Applies to every research task, whichever agent runs it. ## Agents propose. The publisher decides. You can see both. 1. **An agent proposes.** A bounded change with actor, scope, evidence and the record it would supersede. 2. **The publisher governs.** Scope, protected targets, conflicts and taint are checked. Untrusted evidence raises scrutiny and can never lower it. 3. **The record updates.** The approved state is compiled. Every agent's next context request returns it. 4. **The audit remains.** Who proposed, who approved, what changed, when. Metadata and digests, not raw secrets. ## What Company Brain does not do yet. - **No team accounts** (In build): The alpha admits single-owner workspaces. Membership, invitations and roles are in build. - **No enterprise isolation claims** (In build): Tenant isolation is specified with adversarial tests as its gate. It is not claimed until that gate passes. - **No connectors marketplace** (Planned): Sources are allowlisted Markdown and structured proposals. Broad app connectors are not the wedge. - **No certifications** (Not claimed): Evidence is collected from day one. No badge is shown until an audit exists. ## Bring a workspace with more than one kind of work in it. If your agents work across projects or clients, Company Brain is the part of the alpha we most want to test with you. - [Discuss an alpha workspace](https://unforgetter.com/private-alpha) ## Next - [Security and ownership](https://unforgetter.com/security) - [Use cases](https://unforgetter.com/use-cases) - [MCP reference](https://unforgetter.com/docs/mcp) --- Status: Private alpha · guided setup. Contact: hello@unforgetter.com.