Genesis Protect sponsor cohorts
Genesis Protect sponsor cohorts are bounded groups where a sponsor helps fund or support a defined protection window.
Use this page when you are evaluating whether an event, offsite, conference, team trip, or travel cohort can fit the current Genesis Protect launch posture.
Sponsor-supported issuance must still respect posted reserve, staffed Phase 0 review, published terms, and SKU-specific reserve lanes. Sponsorship does not turn app membership into claims-paying reserve.
Which SKU fits
| Cohort need | Current fit | Notes |
|---|---|---|
| Short event, conference, offsite, or team trip | Event 7 | Current launch shell includes a dedicated genesis-event7-sponsor lane. |
| Longer travel window, nomad-style trip, or resident-style travel period | Travel 30 | Current launch shell keeps Travel 30 on premium and liquidity lanes only. |
| Broad employee health insurance or always-on routine care | Not current Genesis Protect | Use the product facts page to keep exclusions and scope clear. |
Sponsor support can cover
- Approved cohort issuance for a defined window
- Explicit subsidy or backstop capital where the SKU supports a sponsor lane
- Clear cohort terms, evidence expectations, and pause conditions
- Reporting and review posture that stays aligned with published launch metadata
Sponsor support should not be described as:
- broad public insurance availability
- a replacement for posted claims-paying reserve
- a way to make app membership fees count as protection reserve
- a promise that issuance stays open if reserve or review readiness falls below the public boundary
Reserve and staffing gates
Before a sponsor cohort is described as open, these must be true:
| Gate | Required public posture |
|---|---|
| Reserve | Posted premium, sponsor, liquidity, or backstop support must cover the marketed cohort window. |
| Review | Phase 0 operator-backed claim review must be staffed for the active cohort window. |
| Terms | Pricing, benefits, exclusions, waiting-period treatment, and evidence requirements must match the published cohort terms. |
| Metadata | Product metadata and evidence schema must stay aligned with the public docs and launch configuration. |
Business path
Sponsors should start from the OmegaX Business Console for cohort intake and operator coordination.
The public docs should stay focused on what can be described safely: product fit, reserve posture, review readiness, evidence expectations, and the boundary between app membership and protection premiums.