Analyse
Two views of one scene, analysed against a fixed checklist of visible actions.
Demo control — show a loop stage
Phase 1 has no provider, so each stage of the investigation loop is shown on request. Nothing runs in the background.
Scene 01 · Candy aisle
Uploaded scene, two views
- Aisle view · vid_a1c9
- 34 s · 48.0 MB
- Checkout view · vid_b2d7
- 41 s · 57.0 MB
- Offset of checkout view
- +1.4 s
Investigation loop
Visible while it happens, in order
Checking the uploaded files
Type, size, duration, and the offset between the two views.
Not started
Analysing aisle view
Five questions about visible actions, answered over the full clip.
Not started
Evidence incomplete — checking checkout view
A decisive question came back obscured, so the matching time window of the second view is requested.
Not started
Merging results
One record, both sources named, missing evidence kept as missing.
Not started
Provider calls used: 0 of a maximum of 2 per scene. The decision to consult the second view is made by the application, not by the model.
Ready to analyse
Both views are aligned
The aisle view is analysed first. If a decisive question comes back obscured, the application requests the matching window of the checkout view — that decision is made in code, not by the model.
Running an analysis arrives in Phase 4, together with the mock provider. Use the demo control above to walk each stage.
Technical details
- Provider
- mock
- Model
- mock-fixture-1
- Prompt version
- p1-2026-07
- Maximum provider calls
- 2 per scene