Stage 3: EXPAND + MASTER PLAN

### R1: Unity on Jetson Orin Nano Performance [CRITICAL] - **Failure scenario:** Unity URP + compute shaders + VFX Graph + video recording exceeds Jetson's 25W GPU budget. Frame rate drops below 30fps, making the experience unusable. - **Probability:** MEDIUM-HIGH (40%) - **Impact:** CRITICAL. The entire product is the visual experience. If it stutters, there is no product. - **Mitigation:** (a) Build a performance benchmark on actual Jetson hardware in Week 2. Target: 60fps with 256x256 fluid sim, 30K particles, 1080p output. (b) If Unity fails: port the 3 compute shaders to native CUDA/Vulkan. The shaders are standard HLSL and translate directly to CUDA. Lose VFX Graph but gain 3-5x performance. (c) Fallback: drop to 720p output and 128x128 fluid sim. Still looks good on a projector from 6ft. - **Validation criteria:** Measured frame time < 16.6ms (60fps) with full pipeline running on Jetson dev kit. - **Owner:** Mohamed - **Timeline:** Must be resolved by end of Month 1. ### R2: Real-Time Video Compositing + Recording Simultaneously [CRITICAL] - **Failure scenario:** Recording composited video (camera feed + visual overlay) to NVMe while rendering the visual pipeline causes frame drops or recording corruption. - **Probability:** MEDIUM (30%) - **Impact:** HIGH. Content creation is the primary value proposition. If recording degrades the experience, users choose between "good visuals" and "record content," which breaks the product promise. - **Mitigation:** (a) Use Jetson's dedicated hardware video encoder (NVENC) which runs independently of the GPU compute pipeline. H.265 encoding at 1080p30 consumes ~2W and does not steal GPU cycles. (b) Record at 1080p30 even if display is at 1080p60 (30fps is standard for social content). (c) Compositing happens in GPU memory. The final render target is both displayed AND piped to NVENC. No CPU-side copy needed. - **Validation criteria:** 5-minute continuous recording at 1080p30 with zero dropped frames while maintaining 60fps display output. ### R3: Femto Bolt Depth Quality at Room-Scale Distances [MEDIUM] - **Failure scenario:** At 3-5 meter distance (typical studio), the Femto Bolt's depth accuracy degrades. Silhouette edges become noisy. The fluid sim looks jittery instead of smooth. - **Probability:** LOW-MEDIUM (25%) - **Impact:** MEDIUM. Noisy depth can be filtered, but aggressive filtering adds latency. - **Mitigation:** (a) Use NFOV mode (640x576 @30fps, 75x65 deg) for tighter, more accurate depth at distance. (b) Apply temporal filtering (exponential moving average across 3-5 frames) to smooth depth edges. (c) The Sobel edge detection in DepthReprojection.compute already provides clean edges from noisy depth. (d) Femto Bolt is rated to 5.5m with <11mm accuracy. At 4m, accuracy is ~15mm. This is acce