IF-14 · Operations interface

Video trigger, media evidence and custody

Correlate trigger, clocks, media segments, policy, access, review, export and lifecycle without rewriting source evidence.

Authority model

Name the source—and name what it cannot prove.

The same message can be observation, projection, plan, receipt or physical evidence. This contract keeps those meanings separate.

Authority

Device observations and immutable media identity remain authoritative; human review appends disposition without mutating trigger evidence.

Degraded behavior

Lens, thermal, storage, clock, upload and corruption states degrade independently; protected evidence survives configured pressure.

Outcome boundary

A trigger is not a judgment; metadata is not media; retrieval authorization is not byte delivery; export intent is not custody receipt.

Product allocation

A product can appear on both sides when it transforms one authority into another; each transformation retains its own evidence.

versioned→fail-closed

Transport allocation

The program can select one or more transports without changing the source authority or failure contract.

Event metadata APIChunked media uploadPurpose-gated retrievalCustody export receipt

OEM program workshop

Allocate owners, transport, schema, releases, policy, content, degradation, replay and target acceptance in one controlled baseline.