Festival forms
A festival can later import the thirteen stages and only ask about relevant answers.
JSON format
explained.
The “generated code” is not a program. It is a structured data file: the same declaration written so both people and computers can read it.
JSON is the container; Audiovisueel AI Statement defines the content.
JSON uses names, values, lists and nested blocks. “VFX: AI as a tool” therefore remains exactly the same fact when later transferred to a festival form, spreadsheet, archive, website or database. A text PDF is pleasant to read; JSON is better for reliable reuse.
Concrete uses
What can the code do beyond the report?
Broadcasters and clients
A system can automatically create a short AI summary without retyping the full report.
Archive and handoff
The file can stay with masters, contracts and cue sheets as durable production information.
Public registry
A future registry can ingest the JSON, validate its shape and publish it under the existing ID.
Credit text
Counts and the Audiovisueel AI Statement ID can automatically become a consistent end-credit statement.
C2PA preparation
IPTC terms and a summary can become candidates for a genuine C2PA workflow.
Small example
Read it like a form with labels.
value is the selected answer. aiSystem names the tool, model and version. departmentsAffected names the crafts involved. agentTakeover records whether an AI agent took over work and what human oversight remained.
"vfx": {
"value": "generated",
"aiSystem": {"name": "example model", "version": "3"},
"departmentsAffected": ["VFX", "compositing"],
"agentTakeover": {
"present": true,
"extent": "partial",
"departmentOrFunction": "initial shot selection",
"humanOversight": "editor approved every decision"
},
"extent": {
"approximate": true,
"percentage": 5,
"imageCoverage": "partial",
"soundCoverage": "none"
}
}Main blocks
How a complete file is organised.
| Block | Contains | Purpose |
|---|---|---|
identifier | Audiovisueel AI Statement ID and local status | Recognise the report consistently. |
title, type, year | Basic production data | Search, display and link. |
scope | Whether delivery and campaign are included | Prevent false conclusions about omitted stages. |
stages | Thirteen stages, crafts, details, extent and any takeover by an AI agent | The substantive AI declaration. |
iptc | Canonical Digital Source Type URIs | Connect to other media systems. |
signed | Self-attestation, name, role and date | Record who made the declaration. |
interoperability | Status of possible downstream steps | Show that C2PA is not yet signed or embedded. |
Limits
Useful data is not proof by itself.
Can someone edit JSON?
Yes. JSON is plain text. The current signature is a self-attestation. A registry, digital hash or C2PA binding can later make changes easier to detect.
Is the Audiovisueel AI Statement ID the same as JSON?
No. The ID is the number on the envelope; JSON is what is inside the envelope.
Can I open the file?
Yes, in any text editor or modern browser. A print/PDF is usually more pleasant for everyday reading.
Why not a secret proprietary format?
An open text format avoids vendor lock-in and makes future migration easier.
Practical storage: keep the final
.audiovisual-ai-statement.json beside the master and retain a readable PDF. JSON is for exchange and automation; PDF is for people. You get that PDF straight from the form, alongside the JSON file.