Per-take technical health report

[erik-sutton95]

Goal

Create a technical health record for every take using the camera and monitoring signals OpenZCine already observes.

Why it matters

A take can appear successful while hiding an audio clip, thermal warning, timecode discontinuity, storage warning, connection interruption, or prolonged exposure/focus problem. Capturing those events at the moment of recording gives the crew a chance to review or repeat the take before striking the set.

Proposed experience

• Start and stop a take record from authoritative Nikon recording-state transitions.
• Capture clip identity, start/end timecode, duration, camera and lens identity, recording format, exposure settings, white balance, media destination, and available capacity.
• Summarize battery, temperature, link quality, live-view stalls, camera warnings, audio peaks/clipping, exposure-assist events, and focus-assist confidence where the data is trustworthy.
• Show a concise post-take result such as clean, review suggested, or incomplete data, with the exact reasons visible.
• Let the operator add or dismiss annotations without rewriting the historical telemetry.
• Associate the report with smart-slate notes and include selected fields in proxy sidecars or cloud delivery metadata.
• Export a privacy-bounded production report without credentials, network identifiers, or unrelated device diagnostics.

Success looks like

Immediately after cut, the crew can see whether OpenZCine observed any technical risk during the take and can carry that evidence through review and editorial handoff.

Open questions

• Which assist events are reliable enough to record without producing distracting false positives?
• Should thresholds be global, production-specific, or disabled by default?
• How should missing live-view data be distinguished from a camera-side recording fault?
• Which report fields belong in Frame.io, sidecars, CSV exports, or local-only history?