Built on SOMA - Structured Orchestration with Memory and Authority

The architectural framework underlying Memrail. A formal separation between observation, memory, and authority that makes AI decisions deterministic and reproducible.

The Framework

Three layers of formal separation

SOMA introduces a formal separation between observation, memory, and authority. This separation means that no matter which LLM generates a proposal, no matter which orchestrator coordinates the workflow, the authority layer makes the same decision given the same context.

Observation

Structured facts about the world. Typed atoms: state (current values), tags (classifications), and events (timestamped occurrences). The raw inputs to every decision.

Memory

Rules encoded as executable units with explicit triggers, actions, and policies. Not neural memory - structured, versioned, inspectable memory that fires deterministically when conditions are met.

Authority

Deterministic evaluation, arbitration, and resolution - independent of the model. The authority layer evaluates observations against memory and produces binding decisions.

Properties

Key architectural properties

Pure functions of documented inputs

Rules are pure functions. Given documented inputs, they produce predictable outputs. No hidden state, no side channels, no emergent behavior from interaction effects.

Deterministic and reproducible

Same inputs plus same rule versions plus same timestamp equals identical output. Every time. This is what makes decision traces audit-grade.

No generative component

The execution layer has no generative component. It evaluates, it does not hallucinate. It selects from defined options, it does not invent new ones.

Built-in change management

Versioning, lifecycle management, and promotion gates are architectural features, not add-ons. Every change is governed by the same rigor as the decisions themselves.

Diagram

The decision plane in context

Memrail sits between intent and execution. Proposed actions pass through the decision plane, where they are evaluated against your business rules to determine what should happen.

SOMA architecture diagram showing observation, memory, and authority layers

Research

Go deeper

For the formal treatment of SOMA architecture, request access to our research preprint. The paper covers the theoretical foundations, formal properties, and proofs underlying Memrail's deterministic authority model.

Request Research Preprint

See the architecture in action

The 14-Day Pilot applies the SOMA architecture to your workflow. See how observation, memory, and authority layers work on your real data and business rules.

Start a Pilot

Questions

Frequently asked

Is SOMA an open standard?

SOMA is an architectural framework developed by Memrail. The conceptual model is public. The formal treatment is available in our research preprint (request access above). Implementation details are proprietary.

How does SOMA relate to other agent frameworks?

Most agent frameworks handle orchestration - coordinating which agent does what and when. SOMA addresses authority - ensuring that whatever the agent proposes is evaluated against business rules to determine what should happen. They are complementary layers, not competing approaches.

Does SOMA require a specific model or framework?

No. SOMA's authority layer is model-independent by design. It works with any LLM, any agent framework, and any orchestrator. The formal separation between observation, memory, and authority means the evaluation layer has no dependency on the proposal layer.