Skip to main content
BEN STONE

Architecture

CompanyOS

Institutional intelligence + company control plane

A company needs one natural-language interface that resolves knowledge, work, ownership, approvals, execution, and verification with permissions, provenance, and receipts.

Status
Architecture / Spec
Role
Sole architect
System Type
Company control-plane architecture (V6 spec)

Capabilities

  • Five authority layers (Principles/Canon → Execution/Orchestration)
  • Permissions, provenance, conflicts, receipts
  • White-label / tenant-neutral design
  • Cato + Genesis as first-party execution components
  • Proof gateway for material actions

Problem

Organizations accumulate tools, chats, and “AI copilots” that do not share authority. The hard problem is a control plane that can answer what the company knows and is doing — with provenance — without becoming a second shadow ERP.

What I Built

CompanyOS V6 is a build-ready architecture specification for tenant-neutral institutional intelligence: one NL interface resolving knowledge, work, ownership, approvals, execution, and verification under explicit authority layers.

It is not a RAG chatbot. SwarmSync components (Cato, Genesis, proof products) remain first-party core in the execution and trust story.

How It Works

Authority is layered: Principles/Canon, Epistemic Knowledge, Company Control Plane, Live Domain Systems, and Execution/Orchestration. Domain OSes (e.g. finance patterns) plug in as live systems; Cato orchestrates; Genesis supplies specialists; proofs gate material outcomes.

Why It Matters

Without a control plane, agent work has no durable company memory and no shared notion of approval. Spec-first architecture makes the boundary clear before runtime sprawl.

Technical Depth

The public-safe surface is the white-label V6 specification. Tenant estate inventories and employer control-plane dumps stay out of this portfolio.

Status

Architecture / Spec — build-ready specification. Related control-plane components exist separately; this card represents the institutional design, not a shipping multi-tenant SaaS UI.

Evidence

Architecture boundaries and authority layers are documented on this page. No public product URL exists for CompanyOS as a consumer site.