Connected checks
No single signal tells the whole story.
Permitted input activity
Disclosed event categories, timing, durations and coarse movement describe activity without retaining what someone typed.
Creative tool context
Supported project and application observations connect activity to the chosen work. An unsupported action stays unknown rather than becoming evidence of a human decision.
Integrity and continuity
Signed sources, ordering, receipts and coverage checks preserve the record and make interruptions or missing evidence visible.
AI supporting verification
An evidence analyst for your process.
Explain a finding
A useful result names the activity and supporting evidence, the method used and the information missing. Your explanation belongs alongside that result.
Keep uncertainty honest
If analysis is unavailable or coverage is incomplete, that state must remain visible. An unavailable result is not a clean finding and is not an incident.
Your permission
Recording permission and AI analysis permission are separate.
The evidence boundary
- Source footage, audio and creative project files are not collected
- Typed text, passwords, scripts, prompts and screenshots are excluded
- Analysis uses limited process evidence with references back to its source
- Stop controls and permission withdrawal must be respected
- Private evidence remains separate from information selected for publication
- Identity, device integrity, observed activity and authorship remain distinct
The strict programme
Warnings help you act. Confirmed incidents affect publication.
Read and respond
A warning identifies the affected activity and evidence. Explain the workflow and request review if the finding is wrong. A model output, gap or suspicion alone never confirms an incident.
First confirmed incident
The affected recording or version is held from programme publication. Address prohibited use and follow the review process before it can be considered again.
Third distinct incident
The project becomes ineligible for directory submission and publication. Multiple observations of one continuous episode count once.
Review and correction
Qualified evidence and attributable actions support confirmation. Corrections preserve history and update dependent restrictions; they do not silently republish an old version.
Technical integration
Use a contract that exists today.
Public API v1
The documented GET routes resolve approved public records. They do not submit film activity, run AI analysis or return a final human creation verdict.
Device and security review
The documented simulator contract remains separate from customer recording. Agree any additional connector or analysis integration with DigiBridge before sending evidence.