The Ownership Operating System

Strata is not four protocols — it is one coordinated system of specialized engines.

Strata is built as a single Ownership Operating System: four specialized engines connected by shared control planes, liquidity, and data layers. The engines are independent enough to be governed and risk-managed separately, but interoperable enough that origination, credit, liquidity, and settlement reinforce one another.

The four engines

Tokenization

Asset onboarding, SPV lifecycle, KYC, and the engine that turns a real-world asset into a structured, investable vehicle.

Money

Issuance of srUSD, the commodity-backed settlement dollar and the system’s control plane for supply.

Credit

Asset-backed credit origination and underwriting against real collateral.

Markets

Liquidity, structured products, and protocol-owned-liquidity management.

How they relate

The system has a clear division of labor:

Layer	Role
Money	Control plane — issuance authority for srUSD
Markets	Liquidity and financial primitives
Credit	Asset origination
Structured products	Financial-engineering layer (tranching, leverage)

Core insight: Money is the control plane that gates issuance; Markets provide liquidity and primitives; Credit originates assets; and the structured layer engineers the payoff. No single engine is the product — the coordination is.

Shared primitives, built once

Several primitives are built once and reused across every engine. This is what makes Strata a system rather than four disconnected forks:

Global control plane

A money-policy controller and engine registry enforce global caps, throttles, and issuance gating across every engine that can touch srUSD supply. Defined first, because everything eventually touches issuance.

Oracle & risk framework

Oracle adapters, risk-config registries, and asset-approval frameworks shared across all forks. The oracle and risk layer is the real protocol; the forks are execution engines.

Registry layer

A unified registry pattern indexes every deployed financial object — markets, engines, risk configs, and fee configs.

Go deeper: Protocol Architecture

The forks behind each engine and the control planes that connect them.