P.00 // SETTLEMENT_INFRASTRUCTURE

Settlement for health outcomes.

OmegaX Protocol is the shared onchain foundation where health plans, reserves, claims, obligations, and payouts become durable, auditable, and coordinated. Built on Solana.

P.01 // WHAT_THIS_IS

The shared machine underneath.

OmegaX Protocol is public settlement infrastructure for outcome-based health programs. It gives health capital markets a ledger where sponsor budgets, member rights, reserves, claims, LP capital, and yield exposure stay separate.

Think of it as the settlement engine beneath the health agent and the business console. OmegaX Health produces evidence. OmegaX Business configures plans. The protocol keeps the economic truth underneath — onchain, shared, and inspectable without exposing raw health data.

CORE_ROLE

Settlement — deterministic resolution of claims, obligations, and payouts from attested health events.

Coordination — a shared source of economic truth that sponsors, members, and capital providers all rely on.

Legibility — capital structure, yield exposure, reserve posture, and plan state are explicit and auditable, not estimated or hidden.

Durability — plan rights, obligations, and settlement history persist onchain beyond any single operator.

P.02 // SYSTEM_ARCHITECTURE

Three surfaces, one truth.

OmegaX is a layered system. The health agent, the business console, and the protocol each have distinct roles — but they share one settlement foundation.

OBSERVATION LAYER

OmegaX Health

The health agent observes, coaches, and produces cryptographic attestations from real-world health activity. It is where evidence originates.

OPERATIONS LAYER

OmegaX Business

The console where sponsors and operators configure plans, set reward rules, manage populations, and monitor program health.

SETTLEMENT LAYER

OmegaX Protocol

The shared onchain foundation that holds durable settlement truth — plans, reserves, claims, obligations, and payouts that all parties can rely on.

The health agent produces evidence. The business console configures plans. The protocol settles and coordinates the durable state underneath. All three are separate products — but they share the same economic foundation.

P.03 // SYSTEM_BOUNDARY

What lives where.

The protocol stores what matters economically. It never stores raw health data. This boundary is the design — it preserves privacy while making settlement state durable and shared.

Onchain

Solana settlement state

The economically important state that all parties need to trust and verify independently.

  • Plan structure, parameters, and lifecycle state
  • Policy series configuration and status
  • Funding lines and sponsor capital tracking
  • Reserve domains and reserve posture
  • Obligations and their resolution state
  • Claims and settlement outcomes
  • Payout records and distribution history
  • Capital classes and liquidity pool state
  • Oracle registry and attestation records
  • Governance authority and proposal state

Offchain

Private and operational

Sensitive data and operational processes that must stay private, compliant, and close to the user.

  • Raw health data and biometric signals
  • Medical records and clinical notes
  • Personal health evidence and sensor data
  • Compliance-heavy processing and workflows
  • Operational plan management and member communication
  • AI coaching, voice sessions, and guidance logic
  • Identity verification and KYC processes
  • Dispute investigation details and evidence review

Why this split matters: Raw health data stays private and compliant. The economically important state — who is owed what, what was funded, what was settled — becomes durable, auditable, and shared. No party has to trust another party's private ledger.

P.04 // SETTLEMENT_FLOW

How settlement works.

From plan configuration to inspectable settlement truth — every step is explicit and every transition is verifiable.

01

Fund

A sponsor or operator funds a plan series: defining the coverage window, funding line, reward rules, and capital lane that backs the program.

02

Reserve

The protocol tracks the reserve posture separately from operating budgets and yield-seeking capital, so liabilities do not disappear into an opaque pool.

03

Obligate

OmegaX Health or another registered oracle verifies a real-world health event and creates the obligation without exposing raw health data.

04

Settle

Claims, payouts, reserve movement, and capital exposure become inspectable state for sponsors, members, capital providers, and auditors.

P.05 // PROTOCOL_PRIMITIVES

The building blocks.

The protocol is built from a set of explicit primitives — each one representing a real part of the settlement machine. Plans hold structure. Funding lines track capital. Obligations encode promises. Claims record resolution. Together, they model the actual complexity of health-plan economics instead of collapsing it into opaque pools.

ReserveDomain
HealthPlan
FundingLine
PolicySeries
CapitalClass
LiquidityPool
Obligation
ReserveDomain

The boundary where risk and reserves are scoped. Domains isolate different populations, geographies, or plan families so reserves stay mathematically contained.

HealthPlan

The root structure for a health program. Defines who participates, what is covered or rewarded, and how the plan is funded and governed.

PolicySeries

A specific reward or protection lane inside a plan. One plan may have multiple series — a walking rewards lane and a coverage lane, for example.

FundingLine

Where sponsor or institutional funding enters the system. Each line is tracked separately so capital provenance stays explicit from deposit to payout.

Obligation

A promise or payable state created by the system when a member meets verified conditions. The protocol creates obligations deterministically from attested events.

Claim

The settlement object representing a coverage or payout event. Claims reference the obligation, the evidence, and the resolution — all onchain.

CapitalClass

How external capital is structured within the protocol. Different classes carry different risk, return, and liquidity profiles.

LiquidityPool

Where capital is pooled and routed to cover obligations and payouts. Pools are structured, not opaque — every allocation is traceable.

P.06 // ENABLED_OUTCOMES

What this makes possible.

Shared settlement infrastructure changes what health programs can finance. When rights, reserves, payouts, and yield exposure are legible, every participant can reason from the same economic truth.

Programmable health rewards

Verified health activity triggers deterministic payouts. No manual approval queues, no opaque intermediary decisions.

Coverage and protection logic

Plans define coverage parameters, reserve boundaries, and payout rules that settle into explicit member rights.

Transparent settlement

Every claim, reserve movement, and payout becomes shared state. Sponsors see what was funded and what happened.

Legible capital structure

Capital providers can distinguish free capital, reserved capital, and yield exposure instead of relying on blended pool estimates.

Open integration surface

Builders can integrate public protocol primitives directly — plans, claims, oracles, capital — without depending on closed operator workflows.

Health capital markets

Sponsors, members, oracles, and LP capital can coordinate around health-linked obligations without losing the financial thread.

P.07 // PARTICIPANTS

Who this is for.

Builders

Integrate public protocol primitives — plans, claims, oracles, capital classes — into your own applications. No proprietary API gates.

Sponsors & Operators

Configure and operate outcome-based health plans with transparent funding, auditable settlement, and clear reserve posture.

Capital Providers

Participate in structured health-linked capital with explicit risk boundaries, traceable allocation, and onchain liquidity posture.

Institutions

Evaluate a public, auditable health-plan infrastructure with explicit governance, compliance-aware system boundaries, and no hidden ledgers.

Oracle Operators

Register as an attestation source, bind to plan series, and participate in the oracle registry with transparent dispute resolution.

P.08 // SETTLEMENT_CHAIN

Why Solana.

Health-plan settlement has specific infrastructure requirements: high throughput for frequent attestations, low cost for individual member events, fast finality for real-time plan state, and composable programmability for structured capital and governance.

Solana meets these requirements at the settlement layer. The protocol uses Solana's speed and cost structure to make per-event settlement practical — not just theoretically possible, but economically viable for millions of health interactions.

Fast finality

Sub-second confirmation for attestations and settlement updates.

Low cost

Per-event settlement that stays economically viable at scale.

Composable

Structured programs that other protocols and builders can integrate.

High throughput

Parallel processing for concurrent plan operations and claims.

P.10 // PROTOCOL_INIT

Public infrastructure for health settlement.

Enter the protocol console to inspect plans, capital, and settlement state — or open the docs to understand the model in detail.