Skip to main content
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

LayerPurposeAuthority
BoardIndependent oversight, fiduciary duty, auditCan override the CEO on governance matters
L5 — MetaOrchestration, quality, incident commandSystem-wide operational authority
L4 — C-SuiteExecutive leadership and strategic decisionsDomain-wide authority
L3 — DepartmentSpecialized domain capabilityFunction-specific (skill clusters)
L2 — ExecutionFront-line capabilityTask-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.

Meet the agents

The 15 runtime agents, their roles, and what each one owns.