Two people examining company records and a question together

Company Brain · guided tour

How your Company Brain works.

A Company Brain connects your organization's knowledge, tools and people. It keeps records in shared memory and coordinates specialist AI agents to research, draft and act within defined permissions, with people making the decisions that need approval.

Explore the eleven parts below: from sources and existing tools to agent coordination, chat, email, web access, operations and ownership.

Example request · 0247

“Can I share this draft agreement with an external adviser?”

The Brain finds permitted evidence, checks the sharing rules and prepares a cited answer for the matter owner to review. This fictional workplace example illustrates the architecture.

Walkthrough progress · 1 of 11 stages explored

Act I · Stage 01

Keep evidence separate from assumptions

The Brain records what each source says, where it came from and what still needs a decision. Documents, descriptions of existing systems and connection requirements remain distinct.

What this makes possible

A reviewer can tell a quoted fact from an assumption before using an answer.

Explore the architecture. These controls change the view.

How the Brain records its inputs

Explore a reference proposal, its existing tools and the responsibilities behind each connection.

Reference source

Company Brain proposal

How we got it
A reference proposal for the walkthrough
How much we read
An example ten-page proposal
Fingerprint
A fingerprint identifies the source version

What the reference proposal describes

The company already has AI tools; this is not a fresh startPage 1 · engagement context
11 tools and pieces of infrastructure already in placePage 2 · component register
7 places to connect or hand off workPage 3 · connections
8 specialist agent stepsPage 3 · agent extensions
3 interfaces for people to use itPage 4 · user surfaces
A production setup and security basicsPage 4 · platform scope
Delivery and handover, signed off at each stepPages 6–9 · gates and risks

Evidence

Keep source versions and references

Tools

Record the tools involved

Ownership

Name the owner of each connection