> ## Documentation Index
> Fetch the complete documentation index at: https://docs.operark.com/llms.txt
> Use this file to discover all available pages before exploring further.

# The AI Corporate Operating System

> How Operark is organized — layers, runtime agents, and skill clusters.

Operark is not a chatbot and not an "AI assistant." It is a **virtual AI
company**: a layered organization of agents that mirrors how a real company is
structured, with governance built into every layer.

## The five layers

| Layer               | Purpose                                      | Authority                                  |
| ------------------- | -------------------------------------------- | ------------------------------------------ |
| **Board**           | Independent oversight, fiduciary duty, audit | Can override the CEO on governance matters |
| **L5 — Meta**       | Orchestration, quality, incident command     | System-wide operational authority          |
| **L4 — C-Suite**    | Executive leadership and strategic decisions | Domain-wide authority                      |
| **L3 — Department** | Specialized domain capability                | Function-specific (skill clusters)         |
| **L2 — Execution**  | Front-line capability                        | Task-level (skill clusters)                |

The Board, L5 Meta, and C-Suite are **15 named runtime agents**. The L3 and L2
roles are **skill clusters** that run inside their parent C-Suite agent — keeping
routing fast while preserving the full org-chart model and named-accountable-role
mapping that compliance frameworks expect.

## How work flows

A request is classified, routed to the right C-Suite agent, executed (drawing on
the relevant skill clusters), and the result flows back up the chain — with every
step logged.

```
Request
  → orchestration (classify + route)
    → C-Suite agent (owns the domain)
      → skill clusters (department / execution capability)
  → result flows back up, fully audited
```

Cross-domain work (for example, "launch a new pricing tier") is owned by a
primary C-Suite agent that requests input from supporting domains through
orchestration — never by bypassing the hierarchy.

## Multi-tenancy

Every organization is fully isolated. Tenant identity is always derived from
your authenticated credential, never from a URL or request body. Background jobs,
real-time streams, and the audit trail are all tenant-scoped.

## Tiers

Capability scales with your plan. Direct invocation of the full C-Suite is broadly
available; Board and certain L5 Meta agents are gated to higher tiers. See your
dashboard for the exact entitlements on your plan.

<Card title="Meet the agents" icon="users" href="/concepts/agents">
  The 15 runtime agents, their roles, and what each one owns.
</Card>