What did the camera observe?
Explore an illustrative maneuver and compare the scope of retained policy and pixel-run results.
This 324-frame clip preserves 10.8 seconds through confirmation. The parent 720-frame controlled run emitted one expected queue-cut event and zero extra events. It does not establish field accuracy.
These are retained synthetic pixel runs, separate from the 82 authored-coordinate policy cases. The videos show source input; measured overlays are separately identified. No live camera, field accuracy or legal determination is represented.
What changes. What remains.
A successful controlled event and a camera miss belong in the same engineering account. The recorded input, run identity and outcome stay together as you switch between them. A measured snapshot is identified by its source time and is not presented as a continuous diagnostic layer.
Use the controls to inspect one change at a time. Reset returns an interactive model to the same starting conditions. The videos keep their original source timing. Nothing here controls a live truck, camera or production service.
Read the engineering account