الأوراق البيضاء

نموذج INDEX

لماذا تحتاج الأعمال السمعية البصرية للذكاء الاصطناعي إلى معرّف دائم، وكيف صُمِّم سجل INDEX ومستويات الضمان وبيانات الاعتماد.

الإصدار 1.0نُشر في 21 نوفمبر 2026مدة القراءة: 16 دقيقةLire en français
تُنشر هذه الوثيقة بالفرنسية والإنجليزية، والنسخة الإنجليزية هي النسخة المرجعية. والنص أدناه هو النسخة الإنجليزية.

01Executive summary

AI audiovisual works travel fast and far: from festival submission platforms to markets, sales catalogues, streaming services and audiences in many countries. At every step someone needs to know what the work is, who declares the rights in it, how AI was used to make it, and which of these statements anyone has checked. Today the answers are scattered across emails, forms and contracts, and they rarely travel with the work.

INDEX.FILM — International AI Audiovisual Asset Registry gives each work one permanent identifier, the INDEX ID, and one public record. The record is versioned, hash-chained and time-stamped. Every field states whether it was declared by the registrant or verified by a named issuer. Content is bound by cryptographic fingerprints, not stored. Four assurance levels — REGISTERED, BOUND, VERIFIED and CLEARED — state what has been checked and by whom, and certificates embed signed W3C Verifiable Credentials that anyone can check.

The Alliance, an international non-profit organisation, operates the register under the registry–registrar model familiar from internet domain names: it keeps the register and the INDEX Standard, accredited registrars serve rights holders, and accredited partners such as law firms and festivals act as issuers within defined scopes. This paper sets out the problem, the design requirements and each component of the model, and closes with the principal threats and their mitigations. The INDEX Standard 1.0 (index.film/standard) is normative and prevails over this paper.

INDEX records registration facts and verification scope, supporting the recognition of rights worldwide. It does not decide who owns rights: courts and competent authorities do.

02The problem

A work is rarely handled by one organisation from first cut to last screening. It may be submitted to many festivals, screened at markets, licensed by territory and medium, re-cut, dubbed and repackaged. Each participant keeps its own reference for the work — a submission number, a catalogue code, a platform asset identifier — and its own copy of what the producer said about it.

  • Fragmented identity. One work appears under several titles, transliterations and working names. Duplicates are hard to reconcile, and a statement made in one place cannot be reliably connected to the same work elsewhere.
  • Statements that cannot be checked. Most statements about a work are self-declared, which is how every registration begins. But a recipient cannot tell a declaration from a checked fact, cannot see who checked it, and cannot tell whether a document is current, superseded or forged.
  • New questions from AI production. Which images were generated? Are performers or voices synthetic, and with whose consent? Does the work depict a real person? May it be used to train models? Festivals, buyers, performers, audiences and regulators ask, and the answers carry legal and commercial weight.
  • Borders and languages. A record that serves a festival in Europe, a distributor in Asia and a platform in the Americas must be legible in their languages while remaining one record with one authoritative text.

The INDEX model does not replace contracts, collective management, national registers or legal advice. It gives them a stable point of reference: a permanent identity for the work, and a verifiable account of what has been declared, what has been checked, by whom and when.

03Design requirements

RequirementWhat it meansHow INDEX meets it
PermanenceAn identifier printed on a poster or certificate resolves for the life of the work and beyond.IDs never reused or deleted; permanent addresses; revoked and merged records remain resolvable.
AttributionEvery statement names who made it, on what basis and when.Field sources (declared or verified); credentials naming their issuer; time-stamped versions.
Verifiability without trusting a websiteA document can be checked without relying on its appearance or on a server being available.Signed W3C Verifiable Credentials; hash-chained versions; RFC 3161 time-stamps; offline verification.
PrivacyThe register publishes what identification and trust require, and no more.Opaque registrant references; evidence as hash references; no files stored.
InteroperabilityThe record connects to identifiers and systems already in use.ISAN, EIDR and other external identifiers; JSON-LD; an OpenAPI-described API.
MultilingualRecords and documents work across languages and scripts without competing versions.Original titles preserved; certificates in eleven languages under one number and one credential.

Two constraints run through every choice. Neutrality: every rights holder, registrar and issuer is treated under the same published rules. Proportionality: a short film by an individual creator and a feature with a complex chain of title can both register, with further assurance added only where a user of the work needs it.

04The INDEX ID

PropertyRule
Length and alphabet10 characters from 31 symbols: 23456789ABCDEFGHJKMNPQRSTUVWXYZ (0, 1, I, L and O are excluded as easily confused)
DisplayUpper case, grouped 4-4-2 in a monospaced face: 7K3P 9Q2M 4X; case-insensitive on input
Links and QR codesWritten continuously: index.film/7K3P9Q2M4X; canonical IRI https://index.film/{ID}
AssignmentRandom; the ID carries no year, category or registrar information

IDs assigned by the Registry end with a check character: taking each symbol's value from its position in the alphabet, the sum of each value multiplied by its position in the ID must be divisible by 31. Because 31 is prime, every single-character error and every transposition of adjacent characters is detected — the commonest mistakes when an ID is read aloud or typed from a poster. Identifiers issued before the Registry opened remain valid as issued.

The identifier deliberately carries no meaning. Meaningful identifiers mislead when the meaning changes — a work is reclassified, a record moves to another registrar — and can disclose information not meant to be public. Everything the identifier refers to lives in the record, where it can be versioned and attributed.

  • An INDEX ID is never reused and never deleted.
  • When duplicates are merged, the merged IDs are kept as aliases and continue to resolve; legacy identifiers can also be kept as aliases.
  • A revoked record remains publicly resolvable with its revoked status, so a printed identifier never silently leads nowhere.

05The record

An INDEX record describes one work: a film, series, episode, character, workflow or world. The last three let the register describe the reusable elements of AI production as well as finished titles. The table summarises clause 5 of the INDEX Standard 1.0.

FieldsRequired from
INDEX ID and aliasesCreation
Work type, form type; original title, original language and translationsCreation / BOUND
Logline, production year, duration— / BOUND
Original languages, countries, genres, creditsBOUND / —
Rights holder name, as declaredCreation
Rights holder legal name, jurisdiction and an organisational identifier (registration number, LEI or ISNI)VERIFIED
AI disclosure: summary, generated imagery, synthetic performers, synthetic voice, real-person likeness, toolsCreation / BOUND
AI-use policy; external identifiers; relationsOptional
Assets: role, SHA-256, ISCC, size, media type, cutBOUND
Level, status, version, version hash, time-stamp, registrar, attestations, current documentSystem

Field sources

Every public field states its source. It is declared when the registrant supplied it through a registrar, and verified when a named issuer has checked it and signed a credential saying so. A verified field that later changes returns to declared until it is checked again. A reader never has to guess whether a statement has been examined.

The registrant

The registrant declares the work through a registrar and is answerable for the declaration. The register stores an opaque reference supplied by the registrar, not the registrant's contact details, so declarations can be attributed without turning the register into a directory of personal data. For an individual rights holder, only the name is published.

Versions, hash chain and time-stamps

Every change creates a new version; nothing is overwritten. Each version is canonicalised with RFC 8785 and hashed with SHA-256. The version hash includes the hash of the previous version, so the versions form a chain: altering any past version would change every hash after it. Each version hash is time-stamped by a trusted time-stamping authority under RFC 3161, and the token is published with the version, so anyone can confirm with standard tools that a version existed no later than the time stated. Earlier versions remain available at index.film/{ID}/v/{n}.

A record is active, disputed, revoked or merged. A disputed record is publicly flagged while a matter is examined under the INDEX Dispute Resolution Policy (IDRP).

06Binding content to the record

A register entry that cannot be tied to a specific file is a description, not an identity. INDEX binds content with cryptographic fingerprints.

SHA-256

For every bound file the registrar submits a SHA-256 digest with the file's role, size, media type and cut. The digest is computed from every byte: any change — one frame, a re-encode, a different subtitle track — produces a different value, and constructing a different file with the same digest is computationally infeasible. Anyone holding a copy can compute its digest and look it up at index.film/verify. A master or screener fingerprint is required for BOUND; a master fingerprint belongs to one work only, which exposes attempts to register the same master twice. Retired fingerprints remain in the record history.

ISCC

An exact digest identifies one file, not the work in all its encodings. A registrar may therefore add an International Standard Content Code (ISCC, ISO 24138), derived from the content so that similar content yields similar codes. SHA-256 answers “is this the registered file?”; ISCC helps to answer “is this probably a version of the registered work?”.

Why files are not stored

Unreleased masters are among a producer's most sensitive assets, and a register holding them would be an attractive target. The Registry does not distribute works and should hold nothing it could be asked to distribute. A fingerprint is enough to establish that a file presented later is identical to the one bound. Files therefore remain with the registrant or registrar, under their own contracts. The same applies to evidence: verification materials, contracts and consents enter the Registry only as hash references, and when an original is produced later, its hash shows that it is the document relied on, unaltered.

07Assurance levels

Not every work needs the same depth of checking, and no single party is competent to check everything. INDEX therefore expresses assurance as four levels, which only increase. Each is represented by a seal and states exactly what it means.

LevelRequirementGranted byDocument
REGISTEREDValid INDEX ID and core fields; public recordRegistrar submissionNone
BOUNDAt least one master or screener SHA-256 bound; BOUND fields completeRegistrar submissionCertificate of Registration
VERIFIEDA verification credential covering at least the rights holder's identity and the registrant's authorityAccredited registrarCertificate of Registration, re-issued
CLEAREDA Rights Clearance Schedule from reviewing counsel stating territory, media, term, exclusions and conditionsAccredited law firmCertificate of Registration and Rights Clearance Schedule

VERIFIED is not an undifferentiated stamp. A verification credential lists the scopes examined — rights holder identity, legal entity, registrant authority, file integrity, AI disclosure review — with the basis and method, the date and hash references to the evidence. A registrar verifies only within the scopes for which it is accredited.

PartyMay attestCredential
Registrant, through a registrarDeclared fields, including the AI disclosure and AI-use policyRecorded in the signed, time-stamped record version
RegistryRegistration facts: ID, title, declared rights holder, fingerprints, registrar, time, version hashRegistrationCredential (did:web:index.film)
Accredited registrarVerification scopes within its accreditationVerificationCredential
Accredited law firmA clearance conclusion with its scope of review, territory, media, term and exclusionsClearanceCredential and Rights Clearance Schedule
Accredited festivalAn honour: edition, section, honour, recipient, citationHonourCredential and Certificate of Honour

A level describes what has been checked, not who owns what. BOUND means files are bound and declarations published, not that the declarations are true. VERIFIED means specific facts were checked by a named verifier on a stated basis. CLEARED means reviewing counsel reached a documented conclusion for a stated territory, media and term: a legal opinion, not a judgment.

08Credentials and documents

INDEX separates evidence from presentation. The evidence is a set of signed, machine-verifiable credentials; the presentation is a document that embeds them and leads back to the register.

Verifiable credentials

  • Credentials conform to the W3C Verifiable Credentials Data Model 2.0. Their subject is the work, identified by https://index.film/{ID}.
  • Proofs use the eddsa-jcs-2022 cryptosuite: Ed25519 signatures (RFC 8032) over JSON canonicalised with RFC 8785.
  • Issuers are identified by did:web; the Registry signs as did:web:index.film, with its DID document at index.film/.well-known/did.json.
  • Status entries of type BitstringStatusListEntry allow a credential to be suspended or revoked.

did:web anchors an issuer's keys to a domain it already controls, without a blockchain or a proprietary trust service. All these specifications are open, so a verifier needs no INDEX software to check a credential.

Certificates

  • A Certificate of Registration (IC-{ID}-{nn}) is issued from BOUND by the Registry with the submitting registrar. Each work has one current certificate; a change of level issues a new version.
  • Earlier versions keep their signatures and verify as superseded, with the newer number given. A superseded certificate is not a forgery but an accurate statement of an earlier state of the record. A revoked certificate no longer verifies as valid.
  • A Rights Clearance Schedule (RS-{ID}-A{nn}) is issued by an accredited law firm; a Certificate of Honour by an accredited festival.
  • Every certificate embeds its signed credential and carries a QR code to index.film/verify/{ID}?v={n}, with a microtext border, a guilloche watermark, the official seal, the assurance seal for the level and the document number on every page.

Each certificate states: “This certificate attests the registration facts and verification scope listed, supporting the recognition of rights worldwide. The live record at index.film is authoritative.” Print features deter casual counterfeiting, but the security model is the signature and the live record: whatever a document looks like, its QR code, number and credential lead back to the register, and the live record prevails.

Language editions

Every certificate is issued in English, the reference edition, with an edition in the official language of the jurisdiction concerned: the rights holder's jurisdiction, failing that the first country of production, failing that the sponsoring registrar's country. Eleven languages are available: English, French, German, Spanish, Portuguese, Simplified Chinese, Traditional Chinese, Japanese, Korean, Thai and Arabic. All editions share one number, one QR code and one signed credential, so a translation can never become a competing document; where editions differ, English prevails. Titles keep their original spelling and script.

Verification

Anyone can verify an INDEX ID, certificate number or SHA-256 fingerprint free of charge at index.film/verify. The response states one of the results defined by the Standard: valid certificate, updated by a newer version, being issued, under review, or withdrawn.

09The registry–registrar model and governance

As for internet domain names, the Alliance operates the Registry — the authoritative register, the Standard, certificates and credentials, and free public verification — while accredited registrars serve rights holders. Registrars are lawfully and officially registered organisations in their country or region, accredited after review. They register works for registrants, collect data and fingerprints, verify facts within their accredited scopes, and provide a security deposit and a prepayment as the registrar agreement sets out. Accredited partners act as issuers: law firms issue Rights Clearance Schedules and festivals issue Certificates of Honour. Alliance members, organisations of the screen industry, support and help to govern the Standard.

Why separate Registry and registrars

  • Neutrality: the Registry does not compete for clients and applies the same rules to every registrar, issuer and work.
  • Proximity: registrars know local law, language and practice, and can check identities and authority with local means.
  • Accountability: each verification is signed by the registrar that performed it, under its own identity.
  • Portability: a rights holder can obtain a transfer code from the current registrar and move the record to another accredited registrar; the ID and history stay the same.

Accreditation and governance

The Accreditation and Compliance Committee reviews applications from registrars and issuers, recommends accreditation to the Governing Council, conducts compliance reviews and audits, and recommends sanctions: warning, suspension or termination. Because every attestation names its issuer, credentials can be suspended or revoked through their status entries, and an organisation's current standing can be checked live at index.film/m/{code}.

The Standards Committee maintains the Standard: normative changes are published for public comment for at least 30 days, minor versions remain backward compatible, and each version is approved by the Governing Council. Keys, signing, time-stamping and incident response are the remit of the Technology and Security Committee; AI disclosure rules, likeness and consent that of the Ethics and AI Transparency Committee. The Registrar Council, the consultative body of all accredited registrars, advises on policy and operations.

Disputes

Disputes about what the register should record are decided under the INDEX Dispute Resolution Policy (IDRP) by independent panellists; Registry staff and registrars are never panellists. The IDRP covers conflicting claims to be the rights holder, registration without authority, materially false or misleading record data including AI disclosure and real-person likeness, transfer disputes and complaints about attestations. The Registry does not decide who owns rights: it decides what the register should record, and with what flags, on the evidence presented, and it implements final court decisions and arbitral awards. Anyone remains free to go to court. The policy is published at index.film/policies/disputes.

10Interoperability

INDEX is designed to sit alongside the identifiers and provenance systems the industry already uses, not to replace them.

Standard or systemRelationship with INDEX
ISAN (ISO 15706), EIDRRecorded as external identifiers of the work, so that the INDEX record and the systems using them refer to the same work. IMDb and TMDB identifiers, festival submission numbers and platform addresses can be recorded in the same way.
ISCC (ISO 24138)Optional content code bound with each file, supporting the discovery of copies across formats.
C2PAContent Credentials carry signed provenance with a file; the INDEX record is a permanent reference for the work. The two are complementary.
W3C VC 2.0, DIDs, JSON-LD; RFC 3161Open specifications: credentials, issuer identities, public records and time-stamps can be processed and checked with generic tools.

C2PA and the registry record

A C2PA manifest travels with a file and describes that file's history — how it was created and edited — signed by the tools or organisations involved. An INDEX record lives outside any file and describes the work: its identity, its declared rights holder, its AI disclosure as a whole and what has been verified. A manifest can be lost when a file is re-encoded or its metadata stripped, while a fingerprint lookup can still find the record; a record cannot see a file's editing history, while a manifest can. Because embedding a manifest changes a file's bytes, the fingerprint bound to the record should be computed on the file as delivered.

Machine interfaces

  • Public record as JSON-LD at index.film/{ID}.json, using the vocabulary at index.film/ns/v1; earlier versions at index.film/{ID}/v/{n}.
  • Registry API at api.index.film/v1, described by the OpenAPI contract at index.film/openapi.yaml and documented at index.film/developers; a sandbox at api-sandbox.index.film.
  • Registry DID document at index.film/.well-known/did.json; credential status lists at index.film/status/{list}.
  • Event notifications that keep registrars' systems in step when records, levels, documents or transfers change.

11Threats and mitigations

No design eliminates risk. The aim is that every attack is prevented, detectable by an ordinary verifier, or correctable through a published procedure.

ThreatMitigations
Forged or altered certificateSigned credential embedded in every certificate; QR code to index.film/verify; certificate number lookup; print security features; the live record prevails over any document.
Outdated certificate presented as currentVerification reports “updated by a newer version” and gives the current number; credential status lists; revoked certificates do not verify as valid.
Unauthorised registrationRegistration only through accredited, audited registrars; registrant authority as a VERIFIED scope; one work per master fingerprint; public, time-stamped records; under the IDRP, a public “disputed” flag within 2 business days where a complaint appears well-founded on its face, then correction, transfer or revocation.
False AI disclosureDisclosure required on every record and attributed to the registrant; declared and verified fields distinguished; AI disclosure review scope; consent evidence referenced by hash; IDRP covers materially false disclosure and likeness; corrections create a new version, history preserved.
Tampering with historyHash-chained versions; RFC 3161 time-stamps from a trusted authority; version hashes and tokens checkable by anyone.
Key compromiseKeys managed under the Technology and Security Committee; did:web allows key rotation; status lists allow affected credentials to be suspended, revoked and re-issued; time-stamps help establish which signatures predate a compromise.
Registry unavailabilityEmbedded credentials and time-stamp tokens can be checked offline with standard implementations; JSON-LD records can be retrieved and kept; permanent addresses remain valid when service resumes.
Impersonation of the RegistryOfficial domains limited to index.film, api.index.film and api-sandbox.index.film; official mailboxes at @index.film; payments only against an invoice from billing@index.film; fraud reports to legal@index.film.

Some risks lie beyond any register. A registry cannot detect a false declaration that nobody has checked or challenged, which is why it labels declarations as declarations. It cannot prevent copying, but it can make a registered copy identifiable. It cannot settle a disagreement about ownership, but it can record the facts and flags that help the parties, their counsel or a court to do so.

12Conclusion

The INDEX model rests on a few deliberate choices: a random, permanent identifier; a record in which every statement names its source and every version is chained and time-stamped; content bound by fingerprints rather than held; assurance expressed as explicit levels and scopes, each attested by the party competent to attest it; credentials verifiable without trusting a website; and governance that separates the neutral keeper of the register from the registrars and issuers who serve and check.

None of these choices is new in isolation; each comes from established practice in internet naming, content identification and digital credentials. Combined, they give AI audiovisual works a shared identity that travels across festivals, markets, platforms and borders, and an honest, verifiable account of what is known about each work. INDEX records registration facts and verification scope, supporting the recognition of rights worldwide; decisions about rights remain with the parties, their counsel, and courts and competent authorities.

13About this paper

The INDEX model: permanent identity and verifiable assurance for AI audiovisual works. Edition 1.0, published 21 November 2026 by the International AI Audiovisual Asset Index Standards Alliance, “the Alliance”, an international non-profit organisation with its seat at Avenue Louise 390, BE-1050 Ixelles, Région de Bruxelles-Capitale, Belgique.

This white paper is published for information only. It describes the INDEX Standard 1.0 (index.film/standard), which is normative and prevails in case of difference. English is the reference edition. Related reading: the white papers on AI disclosure (index.film/knowledge/white-papers/ai-disclosure) and on the recognition of rights (index.film/knowledge/white-papers/rights-recognition), and the INDEX Dispute Resolution Policy (index.film/policies/disputes).

This paper is not legal advice. For advice on a specific matter, consult a qualified lawyer.

الطلبات

انضم إلى شبكة السجل العالمية.

نموذج INDEX · INDEX.FILM