Skip to early access
Architecture · The floor plan, in detail

The model is the engine. This is the harness.

OCTOPUS is neurosymbolic: frontier language models reason over a typed, linked context graph that serves as the system of record, under one governance and trust plane, inside your tenant boundary. Here is what each part does, and how one piece of work moves through it.

Data up. Work down.

Last updated · Machine-readable: llms.txt · capabilities.json

Neurosymbolic

Two kinds of intelligence. One stack.

It is not a chatbot, a single model, or a thin wrapper around one.

Neural: the reasoning

Frontier models plan, draft, deliberate and orchestrate, but only over governed, validated context. OCTOPUS does not replace your model; it makes it trustworthy at enterprise scale.

Symbolic: the record

A typed, linked knowledge graph and a semantic entity model hold what the organization knows. It is the system of record, and it accrues.

The plane: the rules

A governance and trust plane spans every part of the stack: coherence checks, shape validation, the audit record, policy and approvals, tenant isolation and grounding guards.

The stack

Data flows up. Work flows down.

Data flows up from your systems into structured knowledge. Work flows back down through a governance plane that gates every consequential action. All of it inside an isolated tenant boundary.

PartWhat it does
SurfacesWhere the work shows up: briefings, decisions and approvals, agents and workflows, a console, open APIs and an MCP endpoint.
ReasoningFrontier models plan, draft, deliberate and orchestrate, over governed, validated context only.
ContextThe right facts assembled for each task, schema-validated, and retrieved with relationships intact.
KnowledgeThe durable, symbolic system of record: a typed, linked knowledge graph and a semantic entity model.
IntegrationHow data gets in: connectors and an open protocol (MCP), automatic entity extraction, signal capture.
SourcesEverything the enterprise already produces: documents, conversations and meetings, email and comms, live signals.
Governance and trust planeSpans every part: it gates consequential actions, validates shapes, keeps the audit record and enforces tenant isolation.
One task, end to end

Follow one task through the stack.

Each step below is a published behavior, in the order a piece of work meets it.

  1. It arrives with a definition of done.

    Work enters the fleet as a defined task with a goal and acceptance criteria.

  2. The right arm claims it.

    Agents claim by capability, specialists first and capable fallback after. The lane it runs in has an explicit scope and its own level of autonomy.

  3. Context is assembled and checked.

    The facts the task needs come from the context graph with relationships intact, and are shape-checked against an explicit schema before they reach a model.

  4. The model reasons over it.

    Frontier models plan and draft over that governed context, grounded in validated knowledge before they generate.

  5. Consequential moves pass the gate.

    A coherence check runs before anything consequential executes. A decision that belongs to a person goes to the Desk, sorted by reversibility: reversible moves run at once with a short undo window; irreversible ones need a deliberate confirmation.

  6. It closes on proof.

    The task closes on evidence that the effect landed, not on the agent's report. A miss becomes a record with a measured cause and a tracked fix.

  7. The record stays.

    The decision, who made it, the sources and the reasoning stay on the audit record. New entities and signals the work surfaces come back as reviewable proposals, and a person confirms before anything durable is written.

How work moves in the fleet
Integration surfaces

Built to be connected to.

Connection to the platform is authenticated and scoped to a customer's tenant. The public concierge on this site is a separate surface that answers from public material; there is no open, unauthenticated endpoint to customer knowledge.

An open protocol (MCP)

AI clients and agents work with the platform through a standard interface.

Open APIs

Programmatic access to the knowledge, context, signals and content surfaces.

Connectors

For enterprise tools, data sources and conversation surfaces. The full connector list is not published here.

External-model counsel

A governed lane to a second opinion from outside models, redaction-checked and IP-gated.

Cross-organization federation

Share governed knowledge across estates without collapsing tenant boundaries.

The public concierge

https://octo.ad/mcp (one tool, ask_octopus) and POST https://octo.ad/api/ask answer questions about OCTOPUS from public material, with no account. They expose no customer data and no internal graph.

Public MCP versus the tenant API
Early access

Ready to look closer?

We're onboarding a small group of teams that need agents they can depend on. Leave your work email. We'll remember it.

No spam. Your data is never sold. We only write about access.