§ Open source framework

CellOS

The missing infrastructure layer for human-AI coordination. Define how humans and AI agents work together with formal roles, scope boundaries, and accountability chains.

§ 00 — The unit

One cell. Five roles.
Five humans, flat.

Every CellOS deployment reduces to this structure: five steward roles, each owned by a human, in a flat hierarchy. No boss node. Each steward runs AI agents beneath them, scoped to sub-functions - and an agent team can mirror the same five roles, one level down. The structure is fractal.

Hover a steward to read its mandate. Resomnium itself runs as cells of this shape.

CLARITYEXECUTIONNARRATIVEACCESSINTEGRITYFIVE HUMANS · FLAT
THE CELL · five human stewards in a flat hierarchy. Each runs agents beneath them - and an agent team can mirror the same five roles, one level down.
§ 01 — The gap

The problem.

Organizations are deploying AI agents without coordination infrastructure. There are no standards for how agents interact with humans, no formal boundaries for what agents can and cannot do, and no audit trails for accountability.

Existing agent frameworks (LangChain, CrewAI, AutoGen) handle execution but not governance. They tell agents what to do, but not what they're allowed to do, who's accountable, or when to escalate to a human.

01

No scope enforcement

AI agents act without boundaries. No formal definition of what they can and cannot do.

02

No accountability chains

When an agent makes a bad decision, there's no trail showing who was responsible or how to escalate.

03

No coordination protocol

Handoffs between humans and AI are ad hoc. No formal structure for when AI should defer to human judgment.

§ 02 — Architecture

Three layers of coordination.

CellOS provides the governance layer that sits on top of any agent framework, defining who can do what, who's accountable, and what happens when things go wrong.

01
Schema

Cell Schema

JSON Schema specification for defining organizational cells. Roles, participants, scope boundaries, escalation rules, and handoff protocols — all in a machine-readable format.

YAML/JSON cell definitions
5 steward roles (Clarity, Execution, Narrative, Access, Governance)
Scope definitions with allowed/forbidden actions
02
Engine

Coordination Engine

Python runtime that enforces cell definitions. Scope checking before every action, automatic task routing, escalation when agents hit boundaries, and a complete audit trail.

Runtime scope enforcement
Automatic task routing by capability
Cross-cell coordination & handoffs
03
Diagnostic

Diagnostic Toolkit

Assessment engine that analyzes cell definitions for completeness, safety gaps, and coordination risks. Scores your organization's AI readiness and provides actionable recommendations.

Completeness scoring (0-100)
Safety gap detection
Prioritized recommendations
§ 03 — How it works

Three steps to governance.

01

Define your cell

Write a YAML file describing your team: who's in it, what roles they play, what each role is allowed to do, and what happens when something goes wrong.

02

Enforce at runtime

Before any agent takes action, CellOS checks it against the scope boundaries. Forbidden actions are blocked. Actions requiring approval get routed to the right person.

03

Audit everything

Every action, escalation, and handoff is logged. Know exactly who did what, when, and whether it was within bounds.

example.py
from cellos import (
    load_cell_from_yaml,
    CellRuntime,
    Coordinator,
)

# Load your cell definition
cell = load_cell_from_yaml("team.yaml")

# Create a runtime
runtime = CellRuntime(cell)

# Check scope before any action
check = runtime.check_scope(
    "ai-agent-1",
    "send_email to client"
)

if not check.allowed:
    print(f"Blocked: {check.reason}")
    # -> "Action 'send_email' is
    #     forbidden for role 'Analyst'"

# Create and route tasks
task = runtime.create_task(
    "Analyze Q1 revenue data"
)
routed = runtime.route_task(task.id)
# -> Automatically assigned to the
#    best-fit participant

# Full audit trail
print(runtime.audit.summary(cell.id))
§ 04 — Compatibility

Works with your stack.

CellOS is the governance layer, not a replacement for your agent framework. It sits on top of whatever you already use.

Google A2A

Agent-to-agent protocol

LangChain

Agent orchestration

CrewAI

Multi-agent systems

AutoGen

Conversational agents

§ 05 — Origin

Built from real operations.

CellOS isn't theory. It's derived from the Cell Framework that Resomnium uses to run its own operations — a 5-person cell structure with five steward roles (Clarity, Execution, Narrative, Access, Governance) where humans and AI agents coordinate daily.

The framework has been tested in production. CellOS makes it open-source and machine-readable so any organization can adopt it.

Learn about the Cell Framework
Cell Framework architecture — five steward roles coordinating human and AI participants
§ 06 — The framework

The Cell Framework.

The Cell Framework is the organizational design model behind CellOS. It defines how small, autonomous teams of humans and AI agents coordinate through formal roles, clear scope boundaries, and structured accountability. CellOS is the software implementation that makes the Cell Framework machine-readable and enforceable.

Five steward roles

Every cell operates with five distinct steward roles, each with defined responsibilities and scope boundaries:

01

ClaritySets direction, owns final decisions

02

ExecutionCoordinates tasks, manages delivery

03

NarrativeHandles communication and distribution

04

AccessManages relationships and partnerships

05

IntegrityEnsures quality, compliance, and accountability

Flexible cell structures

The framework scales from solo operators to full teams, with each configuration balancing human judgment and AI capability differently:

01

Single PlayerOne human, multiple AI agents

02

Cell of 3Small team with shared stewardship

03

Cell of 5Full cell with dedicated steward roles

04

Startup CellAdapted for early-stage teams

05

Legacy UpgradeTransitioning existing organizations

§ 07 — Status

Where we are.

Current v0.1
Cell Schema specification (JSON Schema + YAML loader)
Coordination Engine with scope enforcement
Task routing and escalation logic
Full audit trail with violation tracking
Diagnostic analyzer with scoring
CLI for cell validation and analysis
Google A2A protocol integration example
88 passing tests
Roadmap
Persistent storage backend (SQLite/PostgreSQL)
Real-time event-driven coordination
Web dashboard for cell monitoring
LangChain / CrewAI adapter packages
Academic validation with research partners
Multi-cell orchestration patterns
Compliance reporting templates
§ Get involved

Want to use CellOS in your organization?

We're looking for early adopters and research partners. Whether you want to contribute to the framework or pilot it in your team, let's talk.

Get in touch Open source · Apache 2.0