“The voice is the identity — independent of the image.”
From registration to render receipt.
How studios prove every AI-generated frame was authorized.
For studio executives, guild reps, and anyone who wants the quick version
A performer registers once. Their face, voice, and motion are converted into a secure identity record — stored in a personal vault they control. When a studio wants to use that identity in an AI pipeline, they request permission through TrustMark. Every render is logged. Guilds can audit the full chain at any time. The performer (or their representative) can revoke access whenever they choose. Free for performers. Studios pay for the authorization infrastructure.
How it actually works
Six steps. From identity capture to a complete audit trail.
The performer (or their studio or agent) uploads face, voice, or motion data to TrustMark. The platform processes the upload and the raw file stays with the source.
The capture tool converts raw data into a secure, one-way identity record. It can verify who someone is, but can never be used to recreate the original face, voice, or motion.
The identity record is placed in the performer's personal Identity Vault. TrustMark never stores the raw capture — only the secure record remains. The performer controls who can access it.
The performer (or their representative) sets two layers of control: Layer 1 controls who can see the identity. Layer 2 controls per-project usage rights — scoped by project, territory, and duration.
When a studio needs to use a performer's identity in an AI pipeline, they request a license token through TrustMark. The system checks authorization and grants or denies — scoped, time-limited, and fully auditable.
After rendering, the studio submits a render receipt — a verifiable record of what was produced, under what authorization. The audit trail is complete.
CaptureRecordVaultAuthorizeLicenseReceipt
Technical detail
Everything below is expanded in the full specification. These are the highlights.
Agents can manage day-to-day approvals, but critical actions are talent-only:
| Action | Talent | Agent | Studio |
|---|---|---|---|
| Approve license request | ✅ | ✅ | — |
| Set Layer 1 visibility | ✅ | ✅ | — |
| Emergency revocation | ✅ | — | — |
| Delete vault data | ✅ | — | — |
| Add/remove agent | ✅ | — | — |
| Submit render receipt | — | — | ✅ |
| Request license | — | — | ✅ |
Full Technical Specification
Authorization tokens, identity records, AI agent compliance, delegation model, data architecture, and more.
How It Works · Powered by DIAP Protocol