Architecture
Use this page when you want the system map before reading object-level protocol details or SDK workflows.
OmegaX is organized as one shared settlement foundation with layered product, operator, and market access around it.
Three layers
| Layer | Main job | What stays out |
|---|---|---|
| OmegaX Health | App, event-production, oracle, and privacy-sensitive workflow | Public raw health records |
| Business Console | Sponsor/operator configuration, monitoring, and reporting | Settlement-critical hidden accounting |
| OmegaX Protocol | Durable rights, liabilities, reserves, capital, and settlement truth | Local workflow and raw evidence |
OmegaX Health
OmegaX Health is the first health app plus event-production and oracle layer.
This is where user-facing health guidance, evidence normalization, attestations, and privacy-sensitive workflow sit. It produces the commitments and event references that the protocol can settle against.
Business Console
The business console at business.omegax.health is the sponsor and operator surface.
This is where organizations configure health plans, manage policy series, operate sponsor budgets, monitor claims, and understand outcomes and costs.
OmegaX Protocol
OmegaX Protocol is the shared settlement foundation on Solana.
This is where the durable public truth lives:
- rights
- liabilities
- reserves
- capital positions
- settlement consequences
- scoped controls
One foundation, multiple access models
OmegaX should not fork into separate public and private protocols.
Instead, it uses layered constraints:
- reserve domains for true legal or custody segregation
- health plans for sponsor and operational policy
- policy series for tighter product semantics
- capital classes for investor eligibility and transfer restrictions
That is how OmegaX can support open DeFi participation and more restricted wrapper-mediated participation on the same accounting base.
Reserve truth
The architecture is designed so the protocol can always answer:
- what is funded
- what is allocated
- what is reserved
- what is owed
- what is claimable or payable
- what is impaired
- what remains free
This is why reserve ledgers exist across domain, plan, series, funding line, capital class, and allocation scopes.
Why this matters
The point is not to force healthcare workflow onchain.
The point is to keep the economically material truth onchain while leaving raw data, local human workflow, and institution-specific operations around the protocol where they belong.