evidence · 2.5 KiB

controls-audit.md

Committed at docs/evidence/splash-initial-scene-ready/controls-audit.md. This is what grounds the requirements that cite it.

Open raw source

Camera audit: initial-scene controls recording

Source: 20260922T223311Z-initial-scene-ready-controls.mp4

SHA-256: b9831514a542c77ac820a2e2fd4a611e817b50e7e3120e21cfeacf7416827420

ffprobe reports H.264, 1920x1080, 30/1 fps, and 65.000 s. The capture manifest identifies a 30 fps /dev/video0 camera recording rotated 180° and labels the control provenance as injected; it makes no real-finger claim.

Method

I reviewed the complete recording at 1-second cadence and made 2 fps contact sheets for the keyboard interval and the display-off/recovery interval:

ffmpeg -y -hide_banner -loglevel error \
  -i docs/evidence/splash-initial-scene-ready/20260922T223311Z-initial-scene-ready-controls.mp4 \
  -vf 'fps=1,scale=320:-1,tile=7x10' -frames:v 1 /tmp/controls-audit/all.jpg
ffmpeg -y -hide_banner -loglevel error -ss 6 -t 20 \
  -i docs/evidence/splash-initial-scene-ready/20260922T223311Z-initial-scene-ready-controls.mp4 \
  -vf 'fps=2,scale=480:-1,tile=5x8' -frames:v 1 /tmp/controls-audit/keyboard.jpg
ffmpeg -y -hide_banner -loglevel error -ss 26 -t 20 \
  -i docs/evidence/splash-initial-scene-ready/20260922T223311Z-initial-scene-ready-controls.mp4 \
  -vf 'fps=2,scale=480:-1,tile=5x8' -frames:v 1 /tmp/controls-audit/dpms-recovery.jpg

Observations

The camera therefore records visible recovery after the display-off interval. It does not measure DPMS latency, prove compositor state preservation beyond the visible result, establish touch accuracy, or distinguish injected input from real finger input. Glare and the oblique camera angle also prevent a complete physical keyboard geometry or label-readability claim.