Lilith Metaverse · Reference & analysis

V3 Client Asset Bundle Validation

250 MB.

2sections2 minread

On this page

v3-client-asset-bundles.v1 is the release gate for the V3/V3_TODOS.md §67 web, mobile, and VR asset-bundling item.

Gate#

  • Web Tier-2 fallback: first-load JS/WASM <= 60 MB and service-worker cache <= 250 MB.
  • UE Mobile: iOS and Android initial install <= 2.5 GB and total disk after first launch <= 4 GB.
  • UE VR: Quest 3 and Vision Pro initial install <= 4 GB and total disk after first launch <= 6 GB.
  • CDN delivery: signed bundle manifest, SHA-256 integrity, HTTP/3 enabled, at least 6 edge replicas, cache hit rate >= 99%, and p95 edge TTFB <= 75 ms.

Evidence#

V3/validation/client-asset-bundle-validation.json records the target bundle set. Per V3/VERIFICATION_AUDIT_2026-05-31.md (§67), these figures are hand-authored projections from the committed asset presets — no UE cook or CDN probe has run, and real-device measurement is pending. The budgets above are normative; the projections below are not measurements:

  • Web Tier-2: 54.2 MB first load and 232 MB service-worker cache (projected).
  • UE Mobile: 2.37 GB max projected initial install and 3.72 GB max projected disk after first launch across iOS (2.31 GB / 3.64 GB) and Android (2.37 GB / 3.72 GB). These match the per-platform projections in V3/MOBILE_ON_DEMAND_ASSET_STREAMING.md; the smaller 1.98 GB / 2.05 GB figures in V3/TENANT_MODE_PAK_CHUNKING.md cover only the base-shell + Tara install-first chunk subset.
  • UE VR: 3.76 GB max projected initial install and 5.48 GB max projected disk after first launch across Quest 3 and Vision Pro.

The gate references the committed V3 fallback web project plus the iOS, Android, Quest 3, and Vision Pro UE asset presets. Run pnpm verify:v3 client-asset-bundles before release; it fails closed if any required client is missing, any size exceeds the V3 budget table, the CDN probe is not green, or the TODO is marked complete without the manifest and evidence.