Lilith Metaverse · Reference & analysis

V3 Region Rollout Compliance

The wave-1 region dossiers live at:

4sections2 minread
Markdown source
On this page

Manifest version: v3-region-rollout-compliance.v1

This gate implements V3/V3_TODOS.md §73B. V3 launch is regional, not global: the tier router opens only signed-off wave-1 regions, routes unavailable regions or tenants to the regional waitlist landing, and keeps wave-2 and wave-3 plans separate from GA launch eligibility.

Wave-1 Sign-Off#

The wave-1 region dossiers live at:

  • V3/docs/regions/us-ca.md
  • V3/docs/regions/de.md
  • V3/docs/regions/gb.md
  • V3/docs/regions/in.md
  • V3/docs/regions/br.md

Each dossier signs off age-gating, content-rating, residency, payment-provider coverage, localization, tenant-policy adaptation, and operator-language coverage. The executable router matrix lives in apps/oshun/bff/src/routes/v3-lilith-launch.ts and the machine-readable evidence lives in V3/regions/tenant-region-availability.json.

Router Behavior#

The BFF route GET /api/v3/lilith/launch evaluates region, tenant, installed-client state, WebRTC support, and Pixel Streaming capacity. Regions outside wave-1, wave-2 plans, and wave-3 projects return:

  • tier: regional-waitlist
  • landingUrl: /v3/landing?mode=regional-waitlist&region=<region>&tenant=<tenant>
  • waitlist.signUpUrl: /api/v3/lilith/launch/waitlist
  • waitlist.acceptingSignups: true when the durable authority is configured

The regional waitlist landing reuses the public V3 page while switching the join form into a focused availability signup. The form requires explicit v3-regional-waitlist-consent-v1 consent and discloses the email-only availability-update delivery contract and 180-day retention limit. POST /api/v3/lilith/launch/waitlist acknowledges only after the owner-mapped snapshot is durable. It returns a private management token whose SHA-256 digest, not the token, is retained. The token authorizes GET /api/v3/lilith/launch/waitlist/:recordId/export and DELETE /api/v3/lilith/launch/waitlist/:recordId. Erasure is saved before its receipt is returned. Deployments without the shared snapshot authority still fail closed with 503 regional_waitlist_not_configured and retain no email.

Tenant Availability#

Saraswati Stage launches in fewer regions than Tara Studio and Lilith Commons. The GA matrix opens all three tenants in us-ca, de, and gb; India and Brazil open Tara Studio and Lilith Commons while Saraswati remains on a regional waitlist until music-rights and local content reviews clear.

Wave-2 And Wave-3#

Wave-2 plans are tracked under V3/docs/regions/wave-2/; South Korea has a signed plan with regional rating-board, residency, and localization requirements listed separately from GA. The GCC block is tracked as a scoped regional plan for KSA / UAE / Qatar.

Wave-3 plans are tracked under V3/docs/regions/wave-3/. Mainland China is a partner-of-record project with ICP, age-gating, IP, and local-residency review. Russia is marked sanctions-prohibited pending geopolitical review. Neither is treated as a copy of the wave-1 or wave-2 launch path.

Run pnpm verify:v3 region-rollout-compliance to validate this gate.