Products, Policies & Plan Families
OmegaX coverage is built as a layered health-plan system rather than a one-off policy record.
That is a meaningful difference. The goal is not to mint a single policy artifact and hide the rest in operator workflow. The goal is to make products, policy rights, premiums, and claims legible parts of the same plan system.
The coverage structure
OmegaX coverage can be understood as:
- Health Plan
- Products and series
- Member policy position
This allows one plan to support multiple offerings while still sharing the same broader policy, reserve, and oracle boundaries.
Why this model matters
It allows OmegaX to separate:
- plan-level capital and trust policy
- reusable product or series terms
- member-specific participation state
That separation is important for coverage, protection, sponsor plans, and future capital comparability.
What the current public surface already supports
The public repo already includes:
- reusable coverage product flows
- policy-series and payment-option surfaces
- member self-subscribe and operator issue pathways
- premium ledgers and payment rails
- coverage policy positions and optional wallet-visible linkage
Why products and series matter
Reusable products and series make it easier to:
- run multiple offerings under one plan
- update or compare offerings over time
- connect claims and pricing to cleaner product semantics
- support sponsor-led, open, and more constrained participation modes on the same foundation
Payment-rail reality
Coverage products eventually need more than one payment path.
OmegaX therefore needs product surfaces that can support:
- onchain payments
- attested offchain payments
- multiple asset rails over time
- restricted or wrapper-aware paths where needed
Why this page is only one layer
Products and policies are not the whole coverage story.
Coverage also depends on:
- claims and settlement
- premium truth
- reserve effects
- interoperability and coding depth for richer products
Plan families inside the same foundation
OmegaX should not be understood only as one coverage style.
The same shared health-plan foundation can support:
- simpler protect or acute-event products with clear triggers
- broader coverage products with richer policy state
- sponsor-led plans with stronger operating requirements
- later AI-assisted plan management around the same rights and reserve structure
That matters because OmegaX is stronger when product breadth comes from one coherent foundation rather than from separate primitives for every new idea.