AIOS
A Collective AI Brain

AIOS

A Collective AI Brain for Teams, Companies, Organizations, and Cities

Open Source MIT Licensed 2026
01The problem

Your organization already has a brain. You just can't access it.

It's scattered across Slack threads, stale docs, meeting notes, and the person who left six months ago.

The question isn't whether your team has collective intelligence. It's whether you can access it.

AIOS is the missing layer that makes collective intelligence queryable, actionable, and alive.

02Motivation

Why now?

  • 01The unit of intelligent action is shifting from individual humans to human-agent ensembles.
  • 02Our institutions were designed for individual human actors, not hybrid teams of people and agents.
  • 03Most AI tools are personal productivity. Nobody has built the coordination layer.
  • 04The coordination tax is crushing organizations: repeated meetings, lost decisions, repeated mistakes.
Teams Companies Organizations Cities
03Principles

Built on four principles

P1

Modular

Each organ system is independently deployable. Adopt what you need.

P2

Open Source

MIT licensed, community governed. The standard, not a product.

P3

Permissioned

Every action is policy-governed. Organizations define what's autonomous and what requires human approval.

P4

Privacy by architecture

Individual agent data is personal by default. The collective brain receives only what members choose to share.

04Architecture

How it works

INDIVIDUAL AGENTS COLLECTIVE BRAIN SURFACES ACTIONS Agent AAgent BAgent C DATA STREAMS Slack · NotionLinear · GitHub Collective Brain Knowledge · MemoryReasoning · Policy daily updates ingestion Kanban board Agent-claimable tasks KPI dashboard Published metrics Query interface Ask the brain anything Spawn agents Research, outreach, drafting Execute tasks Pull from kanban autonomously self-improves with every use

Agent spawning is permissioned by organizational policy.

05Use cases

What this unlocks

01

Coordination without meetings

Query the AI instead of scheduling a sync. Get a coherent answer about what any team is working on, instantly.

02

Chief of staff AI

The global brain as a new kind of team member. Feedback at individual and collective levels: what we do well, where we drift, whether to reconsider our target.

03

Progressive offloading

Permissioned agents take on more of the actual work over time. Humans focus on judgment; agents handle execution.

04

Institutional memory

Onboard a new person in minutes. Every decision, rationale, and failed experiment. Nothing is lost when someone leaves.

Goal10x–100x output per person
06Anatomy

The 8 organ systems

01

Knowledge repository

Queryable shared brain; everything the org knows, structured and retrievable.

02

Ingestion layer

Pipes from Slack, Drive, Notion, Linear, GitHub, meeting notes.

03

Context management

Decides what surfaces and what stays quiet; prioritizes signal over noise so the brain informs without overwhelming.

04

Action layer

Policy-governed agents that act in the world on behalf of the collective.

05

Identity & membership

Who belongs, with what role and permissions; the root of everything.

06

Policy engine

The constitutional layer; what's autonomous, what needs approval, who decides.

07

Audit log

Immutable record of every action, query, and ingestion event; the trust layer.

08

Feedback loop

Closes the loop; the brain learns from outcomes over time.

07Commercial layer

Proprietary

M1

Agent workstations

A pre-configured NemoClaw setup for each individual agent. Every member starts with a tuned, ready workstation, not a blank slate.

M2

Human onboarding know-how

The playbook for getting people and their agents productive fast. Codified practice, not tribal knowledge.

M3

Industry presets

Pre-configured setups for specific industries (legal, and beyond). Domain policies, sources, and workflows out of the box.

Appendix

Extra

The hard problems, and what comes next.

08Honesty

The hard problems

01

Context overload

Too many signals, too much noise. Attention and prioritization is the hardest design challenge. A brain that pages you about everything is worse than no brain at all.

02

Contribution incentives

The system is only as good as what people post. Social design matters as much as technical design.

03

Governance

Building a coordination system requires coordinating the builders. Early decisions set the cultural tone permanently.

04

Trust in autonomous agents

Earned incrementally. Start narrow, demonstrate reliability, expand scope.

05

The schema problem

What is the unit of knowledge? How information is represented decides whether the whole thing is queryable or just a fancier search index.

09What comes next
1

Find pilot teams

10–50 person companies that are AI-native, already running internal agents, feeling the coordination pain.

2

Define MVP scope

Ingestion from 2–3 sources, a queryable knowledge layer, and a basic policy engine.

3

Open source governance

Establish the project charter, contribution model, and decision process before there are contributors.

Every institution that exists today was designed for human actors. We are building the infrastructure for what comes next.

01 / 09
navigate · F fullscreen