Skip to main content
openboa is a Business as Agent (BOA) system. It keeps the business as the durable operating subject and treats agents as an evolvable workforce.
The product stack is Agent -> Chat -> Work -> Observe. Agent is the worker runtime, Chat is shared coordination, Work is business execution, and Observe is governance and evidence.
The current first believable wedge is Chat. openboa is being built as a chat-first company runtime, while Work and Observe remain first-class product surfaces that are still earlier in implementation maturity.
The current code reality is uneven by design. Agent is already a real session-first runtime, Chat already has real shared truth and projections, and Work plus Observe currently exist mainly as shared model types and shell scaffolding.
No. Chat is the current wedge, but openboa is not “just chat.” It is trying to become a business operating system where coordination, execution, and evidence remain durable across changing workers and tools.
Builders who want agent-based execution without giving up policy control, memory continuity, auditability, and explicit business ownership.
Yes. Humans still set direction, approval boundaries, quality bar, and final signoff. openboa is not pursuing a no-operator fully autonomous model.
Stable canon docs keep product meaning, architectural boundaries, design taste, and quality expectations aligned before autonomous implementation complexity grows.
Contributors should assume that surface boundaries matter more than temporary implementation convenience. Agent, Chat, Work, and Observe should stay conceptually distinct even when some layers are still scaffolded.
Start with Introduction, then Business as Agent, Core Doctrine, and Architecture. After that, read the surface docs in order: Agent, Chat, Work, and Observe.

​
Start Reading

Introduction

The shortest path to what openboa is, why it exists, and the current maturity split.

Business as Agent

Core BOA model and building blocks.

Architecture

Surface-first architecture, code reality, and truth boundaries.

Agent / Chat / Work / Observe

The top-level product surfaces and how they relate.

Development

Local workflow, contribution loop, and validation commands.