Verified participation
Use your own verified account and keep contributions attributable to the people who made them. Shared work belongs to a shared project, with each contributor’s record preserved.
THE DIGIBRIDGE STANDARD
When AI can operate the same creative tools as a person, creators need evidence of their human effort. DigiBridge gives filmmakers, media teams and musicians a way to record their contribution, detect prohibited assistance and share eligible work with evidence behind it.
Use your own verified account and keep contributions attributable to the people who made them. Shared work belongs to a shared project, with each contributor’s record preserved.
Link the creative project file, choose the recording scope and build the record as you work. Review session coverage, gaps and the version you want to submit.
Identify collaborators, imported material and assistance relevant to the submitted version. Declarations give reviewers context alongside the recorded evidence.
Resolve findings and complete the required review before publishing. Share only permitted evidence for the version that meets the standard.
DigiBridge combines device, operating system and application evidence, integrity checks and a dedicated AI verification agent to detect prohibited AI assistance and synthetic control. Each film, video or music recording follows the disclosed policy for its connected tool.
AI agents and assistants must not perform creative tool actions in place of the contributor. Declare assistance and imported material so the submitted version can be assessed under the applicable policy.
Agents, scripts, macros and other software that generate tool actions in place of the person are excluded from the strict recording programme. Synthetic assistive or remapper control is also excluded from that programme; check compatibility before recording.
Ordinary playback, sequencing, musical automation, keyframes and rendering are assessed under the disclosed policy for the connected tool. These production functions are distinct from software operating the creative application in place of the contributor.
Do not tamper with recordings, replay evidence, misrepresent a contribution or use another person’s account. Renaming a project, moving a known version or reinstalling does not clear an established finding.
During recording, warnings identify the affected activity, reason and supporting evidence. A warning shows whether an incident is confirmed; AI suspicion, missing coverage or a recording gap alone never counts as a strike.
Warning 1 of 3 identifies the affected recording and confirmed action. The affected version is held from publication under the programme.
Warning 2 of 3 identifies a second distinct confirmed incident and explains the next consequence. Restrictions on the affected version continue.
The third distinct confirmed incident makes the project ineligible for directory submission and publication. A private policy mark is attributed to the responsible account, and a review case is opened.
Confirmation requires qualified evidence of a prohibited action. One continuous episode counts as one incident, even if it contains many events; retries do not add strikes. Repeated abuse can lead to reviewed account suspension or closure. Project status is visible to authorised project users; personal account policy records remain private.
Read the reason and supporting evidence, add your context and request a review if a finding or assignment is wrong. Review can confirm, correct or merge incidents and update the restrictions that follow from them.
Corrections preserve the history. A corrected project goes through a fresh publication review before it is shared again.
“Registered with DigiBridge” identifies an established project record. Verification covers the selected output, recorded coverage, declarations and completed checks shown in its result.
Account identity, activity and authorship remain distinct. A gap in recording is visible as a gap, and time spent or input volume is never converted into a percentage of human creation. Copyright and contractual rights require their own assessment.
Evidence collection excludes source audio, video, MIDI and project files, typed content, passwords and screenshots. Recording, AI analysis, identity checks and publication have separate permissions and notices.