3.6 KiB
Verification Status
Last updated: 2026-08-30
This file owns only cross-module physical evidence that still changes how the current product may be described. Status owns exact source and production identity; product modules and ADRs own accepted behavior; tests and Git own completed implementation evidence.
Route And Network
Still required on representative public networks:
- direct Host-to-Viewer P2P;
- Peer-fed and SFU-fed Browser relay, including a second-level child;
- Host and Viewer TUN/VPN cases;
- relay-ingress failure with subtree retention;
- disconnect and effective-capacity drain;
- two simultaneous rooms with independent SFU publications;
- measured endpoint upload and server ingress/egress during steady routing and make-before-break overlap;
- 20-Viewer queue tail, route depth, resource use, and endurance; and
- all-UDP-blocked bounded failure.
The route model, capacity C=1..3, first-frame commit, rollback, SFU admission,
and managed-room lifecycle have automated invariant coverage. That coverage does
not prove target-network quality, latency, or interoperability. See
ADR-0005 and the
routing contract.
Media Quality
Still required:
- real games at 720p30, 1080p30, and 1080p60 on weaker Hosts;
- actual H.264/VP8 encoder paths and sustained CPU/GPU contention on Windows, macOS, and Linux;
- mixed P2P/SFU quality and recovery on heterogeneous public networks;
- screen-audio presence, stereo correctness, weak-network behavior, and A/V synchronization after SFU RED was disabled; and
- long-running encode/decode cost, thermals, frame delivery, and resource admission at the 20-Viewer bound.
Current controlled Browser evidence supports the H.264/VP8 gate, motion
content intent, startup-quality workaround, LiveKit-owned SFU adaptation, native
edge convergence, and same-edge connection regeneration invariants. The
2026-08-30 production comparison confirms recovery on a fresh same-route sender,
but does not establish its quality or resource benefit on heterogeneous public
networks. Room 8489 confirms synchronized SFU stalls and representation churn,
but retained logs do not prove whether Dynacast layer disablement, subscriber
forwarding, or keyframe reacquisition owned each freeze. See
media quality
and realtime quality research.
Browser Lifecycle
Still required on physical Android Chrome and iOS Safari:
- autoplay and user-gesture recovery;
- foreground/background audio;
- foreground video recovery after background or lock;
- page reclamation and BFCache behavior;
- rotation and viewport changes;
- Wi-Fi/cellular migration; and
- survival or controller recovery when the mobile Viewer is a relay.
Desktop Host background/minimized capture also remains unconfirmed under a current-production real game. Web code cannot promise OS background execution, page retention, or capture keepalive. See presentation and lifecycle and background capture research.
Interpretation Rules
- Configuration, unit tests, loopback, and synthetic signaling prove invariants, not target-network or device behavior.
- Missing RTCStats fields are unknown, not zero.
- Requested quality values are ceilings; actual sender/receiver stats are truth.
- A page-lifecycle correction is recovery logic, not a keepalive guarantee.
- Expensive evidence remains applicable only while its protocol, component, configuration, environment, and acceptance boundary remain materially the same.