Sovereign control, layer by layer.

The applications your teams live in: departments and messaging, meetings with sovereign minutes, documents and spreadsheets, CRM, projects and tasks, and the specialist studios for finance, legal, engineering and operations. The studios share the substrate; each workflow still needs defined permissions, audit coverage and processing boundaries. External messaging and other connectors require separate approval and evaluation.

One assistant surface coordinates work across studios, brains and automation. The architecture separates planning, authority to execute and verification of the outcome. Agree which steps are recorded and signed, then test permitted actions, denied actions and failures in the proposed version.

Fifty specialised brains, twenty five domain and twenty five operational, coordinated by a deterministic arbiter. Each brain has a domain; the arbiter routes requests or composes a quorum across several. Evaluate routing quality, human review and the routing events captured in the audit record for the agreed workflows.

The trust plane combines the Open Audit Record, hardware identity, Sentinel and the sandbox gateway. OAR uses hash linkage and ML-DSA-65 signatures designed for offline verification with a trusted public key. Hardware attestation, destructive-action checks and prompt-injection inspection are controls to evaluate, not proof that attacks cannot succeed. Test audit coverage, key custody and the configured egress paths.

On-device inference across CPU, GPU and NPU, with the execution balance selected for the workload. Offline operation requires the models, authentication, extraction, retrieval and other supporting services to be local. Inspect telemetry, licensing, updates and support tooling as well as inference; connected workflows need an explicitly scoped network path.

The deployment options use customer-owned hardware: a sovereign workstation, an office estate, or rack-scale inference with Pantheon. Size and test the estate against model memory, concurrent requests, storage and recovery needs. Adding machines also requires review of identity, permissions and operational support.

Scope offline operation

Keep the required workflow and its dependencies local, then test a disconnected start and recovery. Live external information requires a connection or controlled import.

Define the egress boundary

Map and test data flows, including telemetry, backups and support. Separately scope any operator-approved gateway; a connected workflow is not fully air-gapped.

Verify recorded actions

Agree which actions and outcomes enter the signed audit record. Check integrity, missing events and key trust separately; a valid signature does not prove correctness.

The operator holds the keys

The design places key custody with the operator. Confirm storage, administration, backup, recovery and support access for the actual deployment.

Sovereign workstation

A single-operator deployment on one machine, with local models, company knowledge and audit services. Assess casework, deal-room or incident-response workflows against their requirements. Air-gapped operation depends on the configured services and controlled imports.

On-premise estate

An installation in your server room serving departments across your internal network. Test department permissions, concurrent workloads and audit coverage. On-premise location alone does not establish zero egress; inventory source connections and external services.

Air-gapped enclave

An environment isolated from external networks, for workflows whose requirements call for that separation. Keep required services and verification materials inside the boundary, with controlled updates and transfers. Demonstrate disconnected operation, key recovery and restoration for the agreed period and workload.