Skip to main content

Product Modes & Lifecycle

OmegaX is designed to support multiple product modes on one shared health-plan foundation.

That matters because the protocol is not meant for one narrow product wedge. It is meant to support a family of health-plan expressions without rewriting the economic base each time.

Product modes​

1. Permissionless rewards​

  • open or token-gated participation
  • verified outcomes trigger rewards
  • lower-friction, higher-speed plan design

2. Sponsor-led plans​

  • employer, provider, or operator-managed participation
  • stronger reporting and control needs
  • the same settlement foundation with tighter plan policy

3. Coverage and protection products​

  • reusable products or series under a shared plan
  • premium and claim state
  • explicit reserve and payout consequences

4. AI-assisted plans​

  • AI helps with pricing, review, triage, or orchestration
  • final enforceable state still lands in protocol logic

5. Regulated participation modes​

  • credential or wrapper-constrained entry on the same foundation
  • restricted rails where needed
  • same underlying plan economics with additional controls

6. Capital-market participation​

  • explicit capital classes
  • reserve-aware redemption logic
  • wallet-visible exposure and future secondary distribution

Canonical lifecycle​

Most OmegaX products follow the same broad flow.

1. Plan creation​

A sponsor or operator creates a health plan with:

  • eligibility policy
  • oracle trust policy
  • payout and claim rules
  • asset and capital settings

2. Capital formation​

The plan is funded by sponsor capital, treasury capital, outside capital, or some mix of the three.

3. Enrollment and access​

Members join through open, token-gated, invite-based, or credential-aware eligibility paths.

4. Product or series selection​

The plan may offer one or more reward, coverage, or protection paths under the same foundation.

5. Event production​

Health or coverage-relevant signals are observed, normalized, and turned into protocol-usable events.

6. Finality​

Oracle policy, review, or challenge mechanics determine when an event becomes valid for settlement.

7. Liability update​

The protocol books the relevant consequence:

  • claimable reward
  • claim review state
  • reserve impact
  • payout obligation

8. Settlement​

Funds move only through explicit protocol instructions and policy checks.

9. Reporting and renewal​

Sponsors, operators, and capital providers evaluate outcomes, reserves, and economics for continuation or new issuance.

10. Capital consequences​

Payouts, claims, and reserve usage feed back into capital performance, free-capital availability, and future plan design.

Why the shared lifecycle matters​

This common lifecycle is what lets OmegaX support many product forms without splitting into one protocol for rewards, another for coverage, and another for capital.

It gives sponsors a cleaner operating model, gives builders a more stable object model, and gives capital a more legible economic surface to evaluate.

Download PDF