TrustMark IP — Protocol Specification
The complete technical specification for the Digital Identity Authorization Protocol (DIAP).
The Internet Lacks Identity Infrastructure
AI generation quality has crossed the “convincing” threshold. But the industry has no shared guardrail system — no way for studios, agencies, guilds, or talent to verify authorization at the pipeline level.
Outside Actors Training on Public Footage
AI tools like ByteDance’s Seedance can generate hyper-realistic likenesses from public photos alone. Nicolas Cage’s face, Mick Jagger’s voice — anyone’s identity can enter a model without a single authorization.
No Guardrails in the Pipeline
Studios, agencies, and platforms have no shared infrastructure to verify authorization at the render level. Every AI pipeline is a silo with no standard authorization layer.
No Way to Prove Authorization
When Disney sends a cease-and-desist over AI-generated Spider-Man, there’s no industry standard for the other side to prove they had authorization. Or for Disney to prove they did.
Synthetic Replacements
Someone can train a model on a performer’s public footage and generate content without ever hiring them. No contract exists because no relationship exists.
Post-Acquisition Exposure
When a studio gets acquired, performance data can end up with new owners who have no relationship with the talent. The original authorization was with a company that no longer exists.
Visibility Without Authorization
Being searchable inside an AI tool — before any project starts — means a talent’s identity is already exposed. The industry has no mechanism to control who can even see the data.
Why Now
Two-Layer Authorization Engine
DIAP separates platform visibility from project usage authorization — giving every participant clear, auditable control at each stage of the pipeline.
Platform Visibility Authorization
A policy decision by the identity owner controlling whether a given AI app can list, search, display, or select their identity. If denied, the identity is completely invisible and unselectable.
Project/Campaign Usage Authorization
A scoped license token grant for a specific project or campaign under a compliance profile. Enables rendering within defined limits and triggers provenance and receipt logging.
Authorization Flow
Certification Check
App verifies its own DIAP-Certified status via Trust Registry
Visibility Check (PVA)
App checks Platform Visibility Authorization for target identity
Identity Displayed
If allowed, identity may be shown as selectable under listing constraints
License Request (PCUA)
On selection, app creates a scoped LicenseRequest for the project
Token Issuance
Issuer evaluates request against compliance profile; approval yields signed token
Execution & Receipts
Gateway verifies token, verifies scope, produces outputs and provenance receipts
Human-Rooted Authority
Least Exposure
Interoperable
Revocable
Auditable
Policy-First Safety
Protocol Components
A modular, build-ready architecture designed for security, interoperability, and enterprise-grade deployment.
Identity Vault
Stores identity modules (voice, face, expression, motion) with KMS/HSM integration and secure enclave support. Assets never leave the vault without authorization.
Platform Visibility Service
Evaluates PVA policies in real-time. Returns allow/deny decisions with listing constraints (discoverable, invite-only, hidden).
Policy / Authorization Engine
Evaluates LicenseRequests against compliance profiles. Manages approval workflows including per-render, per-project, and quota-based modes.
License Authority (Issuer)
Issues signed, PoP-bound license tokens. Manages quotas, audit logs, and delegation from the DIAP Central Authority.
Revocation Registry
Low-latency revocation checks with push-based updates and webhooks. Supports license, app, and campaign-level revocation with emergency revocation protocols.
Execution Gateway
The authorization checkpoint. Verifies tokens, applies policy, routes generation through adapters, embeds dual-layer watermarks, and emits events for provenance tracking.
Provenance Service
Watermarking and receipt generation. Verification endpoints enable downstream platforms to confirm authorization of any synthetic output.
Trust Registry Service
Central directory of certified issuers, apps, keys, and revocation endpoints. The root of trust for the entire DIAP ecosystem.
Developer Portal & SDKs
Registration, key management, conformance tests, and integration examples. Integrate once, be compliant everywhere.
Studio Compliance Suite
Approvals dashboard, audit exports, role-based controls, and campaign management for enterprise studio workflows.
Identity Modules
Identity is represented as independent modules with explicit purpose limitation and sensitivity metadata. Each module can be licensed independently.
VoiceModuleVoice embeddings and synthesis parameters
VOICE_RENDERFaceModuleFacial geometry, texture, and appearance
FACE_RENDERExpressionModuleFacial expression mapping and control
EXPRESSION_RENDERMotionModuleBody motion capture and kinematics
MOTION_RENDERFootprintModuleOptional persona metadata (not required for core auth)
Rights Taxonomy & Scope
Rights
TRAINING_USE is explicitly separate from render/inference rights.
Scope Dimensions
Approval Modes
Dual-Layer Watermark & Modification Tracking
Every asset rendered under DIAP carries two independent watermarks: a pixel-level cryptographic payload in the image data, and an ultrasonic audio frequency fingerprint in the sound track. A separate modification map records exactly what AI changed — and what it didn't.
Layer 1: Pixel Cryptographic Watermark
PIXEL-LEVEL ENCODING
A cryptographic watermark encoded directly into pixel data. Invisible to the human eye but machine-readable. Survives compression, re-encoding, and social media upload.
Encodes
Channel: Visual. Embedded in pixel data — travels with images and video frames.
Layer 2: Audio Frequency Watermark
ULTRASONIC FREQUENCY TONES
Inaudible ultrasonic tone patterns embedded in the audio track. 49 frequency sub-bands encode a unique fingerprint. Even if the video is visually altered, the audio frequency signature persists.
Encodes
Channel: Audio. Independent of visual data — survives video re-encoding and visual alterations.
Forensic Layer: Modification Mask
STORED IN DIAP VAULT
A modification map recording which regions are original vs. AI-modified. Stored securely in the DIAP vault, linked to the render receipt by Token ID. Never embedded in the file.
Records
Channel: Off-file. Forensic-only — visible to agents, studios, and auditors.
Why Three Separate Layers?
Independent Channels
Pixel watermarks live in visual data; audio watermarks live in the sound track. They operate independently — if one layer is lost, the other still carries full provenance.
Resilience to Alteration
A deepfake can replace the visual frames, but the original audio frequency fingerprint persists in the ultrasonic range. Audio can be stripped, but the pixel watermark in remaining frames still identifies the source.
Quality Preservation
Each layer encodes only what fits its channel. Pixel watermarks stay invisible. Ultrasonic tones stay inaudible. The modification map stays off-file entirely.
Forensic Security
The modification mask — which reveals exactly what AI did — is too large and too sensitive to embed in the file. It stays in the DIAP vault, protected.
Three Levels of Verification
Different participants see different depths of information. Public verification is open to everyone. Detailed modification data is restricted to the people it belongs to.
Public Verification
Anyone — platforms, moderators, audiences
Free API call, no authentication required
Returns
Does Not Return
Dual-Layer Survival: Downloads & Distribution
Both watermark layers are embedded in the content itself — not in file metadata. They travel with the file through different channels (visual + audio), providing redundant tracking.
How Verification Works in Practice
Platform verifies content
Public verificationA streaming platform receives content containing a talent's likeness.
Their content pipeline scans the file with DIAP's public Verification API.
The watermark is extracted → Token ID found → DIAP returns:
Deepfake detected
No watermark foundSomeone creates a deepfake of Marcus Rivera without going through DIAP.
The same platform scans the content. No DIAP watermark found.
Talent reviews what AI actually did
Owner verificationMarcus logs into his Identity Vault on diap.my.id.
He opens the Meridian render receipt and views the modification mask:
Modification Report — Meridian, Episode 3
Frames 4200–4847: 23% of pixels AI-modified
Model used: Nuke AI Face Enhance v3.2
Rights verified: FACE_RENDER authorized
Heatmap available: View pixel-level modification map →
Summary: What Lives Where
| Data | Stored In | Visible To | Survives Download |
|---|---|---|---|
| Layer 1: Pixel watermark | Embedded in pixel data | Anyone (public API) | Yes — travels with images & video frames |
| Layer 2: Audio frequency watermark | In the audio (ultrasonic range) | Anyone (public API / Sound ID lookup) | Yes — travels in audio track |
| Modification mask (pixel-level) | DIAP audit trail | Talent + delegates + auditors | N/A — not in the file |
| Render receipts | DIAP audit trail | Talent + delegates + auditors | N/A — not in the file |
| License status | DIAP registry (live) | Anyone (public API) | N/A — live check per request |
Two independent watermark channels — pixel (visual) and audio (ultrasonic) — provide redundant public proof that travels with every file. The modification mask is the private forensic detail secured in DIAP's vault. Together, they form a resilient three-layer provenance system.
Technical Deep Dive
Token spec, asset fingerprinting, vector core, AI agent compliance layer, and SDK reference.
ScriptModule
Writer & authorship protection. A first-class protected asset type for authored writing and project literary materials — extending DIAP with authorization-first script governance.
Non-goal: ScriptModule is not a replacement for copyright registration, chain-of-title, or legal guild processes. It is a technical infrastructure and audit layer that ensures scripts are handled according to their owner's authorized policies within AI systems.
Protected Writing Assets
DIAP is primarily an identity authorization protocol (voice / face / expression / motion). However, studio-grade compliance requires protecting writing assets and their authorized downstream use — especially when scripts are used to generate derivative outputs or as training material.
Any authored writing used in development/production — screenplay drafts, outlines, treatments, bibles, pitch decks, scene text, dialogue, alt-lines, script notes, revisions.
The natural person(s) who authored the Script Asset, or an authorized rights holder/representative (estate, production company) acting on their behalf.
Any AI-assisted generation using Script Assets as input/context — new scenes, dialogue, scene variants, summaries, character breakdowns.
Using Script Assets to train/fine-tune a model, build embeddings for general reuse, or incorporate content into persistent model weights beyond the specific job.
Rights Taxonomy (Writing)
Industry Implementation
From film production to distribution verification, DIAP provides the authorization infrastructure for every stage of the AI identity pipeline.
Film & Television
Previs, dubbing, localized promos, and digital doubles under strict scope. Union-ready controls with mandatory checkpoints for role/script approval and final output review.
No-photoshoot posters & key art via Marketing Avatar Workflow
DIAP-Certified design tools check PVA before showing talent
Creative-lock checkpoints: shortlist approval, final select
Every exported output carries dual-layer watermark (pixel + audio) for verification
Audit bundles for legal/compliance; usage statements for agents and studios
Advertising & Marketing
Actor avatars for posters, billboards, social ads, and international variants. Brand-safe compliance profiles with reputational protection.
FACE_RENDER + EXPRESSION_RENDER under DIAP-Brand-Safe
Territory-specific licensing with global campaign support
Creative-lock workflow ensures brand alignment
Per-line or per-spot approvals for sensitive campaigns
Games & VR
Motion and voice licensing with usage statements. Real-time rendering authorization with quota-based approval modes.
MOTION_RENDER + VOICE_RENDER scoped to game/experience
Quota-based authorization for interactive applications
Watermarked outputs for distribution verification
Education & Enterprise
Authorized speaker avatars with mandatory disclosure and comprehensive audit trails. Non-commercial constraints verified by policy.
DIAP-Education-NonCommercial profile with disclosure_required
Blocks on political persuasion, endorsements, fundraising
Full audit trail for institutional compliance
Distribution Verification
"Was this authorized?" — verification for platforms. Distribution platforms can require valid receipts for monetized synthetic human content.
Receipt verification via /v1/receipts/verify endpoint
Watermark scanning toolkit for platform-level compliance
High-volume verification API for content moderation
Studio Marketing Workflow: No-Photoshoot Posters & Key Art
DIAP turns identity usage into a controlled, auditable workflow that mirrors existing entertainment contract structures.
Studio uses DIAP-Certified design tool (e.g., Nano Banana Studio Tier)
Tool checks Platform Visibility Authorization for Actor X
If allowed, Actor X is selectable under listing constraints
Studio requests marketing-static rights (FACE_RENDER + EXPRESSION_RENDER) under DIAP-Brand-Safe
Actor/rep approves with optional creative-lock checkpoints
Design tool generates variants; only authorized final selects are exported
Every exported final select carries dual-layer receipt/watermark + Sound ID
Studio obtains audit bundle; actor receives usage statement + compensation
Localization & Dubbing
VOICE_RENDER scope granted per territory/language with strict rating and claim restrictions. Per-line approvals supported for sensitive campaigns.
Union-Ready Controls
Mandatory checkpoints (role/script approval, final output review). Exportable statements for reps. Distribution hold for disputes. Training rights always separate.
Policy Presets
Standardized policy templates that define approval modes, category blocks, provenance requirements, and audit exports. Stored as first-class policy objects.
Talent-Strict
Maximum control for public figures
Brand-Safe
Commercial use with reputational safety
Union-Ready
Union-style approvals and dispute workflows
Indie Creator
Low friction licensing with provenance
Enterprise-Verified
High assurance for studios/enterprises
Education / Non-Commercial
Learning/research with strict constraints
Transparent Pricing
DIAP monetizes infrastructure and compliance — not a percentage of talent pay. Talent access to vault and policy controls is free or subsidized to maximize participation.
Central Authority Access
SDK + registry access + certification + verification endpoints for AI applications.
Studio Compliance Suite
Dashboard, approvals, audit exports, and campaign management for studio workflows.
Distribution Verification
High-volume verification API + watermark scanning toolkit for platforms.
Enterprise Security Pack
Dedicated tenancy, SLAs, advanced attestations, and incident response.
Annual Fee
A predictable annual subscription covers platform access, certification, compliance tooling, and baseline API capacity. Designed to fit studio procurement models — one line item, no surprises.
Usage-Based Billing
Beyond the base tier, usage scales with your actual consumption. Pay only for what you use — billed monthly, metered transparently. No percentage-based fees on talent compensation.
Why This Pricing Model Works
Procurement Fit
Studios buy SaaS tools, not usage taxes. DIAP fits existing procurement workflows with a single, predictable line item.
Predictability
Annual fees give budget certainty. Usage-based overages are transparent and proportional — no hidden multipliers.
Neutrality
No percentage of talent pay avoids conflict-of-interest perception with compensation structures.
Scalability
Supports massive volumes across multiple apps and platforms. Marginal cost decreases as usage grows.
Standardization Path
DIAP starts centralized for speed and evolves to federation as unions, studios, and major platforms participate. Common verification always anchored.
Centralized Pilot
Single DIAP Central Authority + delegated issuers. Publish spec, schemas, and conformance tests publicly. Launch DIAP-Certified program.
Multi-Issuer Expansion
Multiple certified issuers (studios, unions) listed in the registry. Pilot with anchor talent + studio marketing workflow. Expand to localization/dubbing.
Federation Governance
Multi-party steering, transparent audits, standardized key ceremonies. Multi-stakeholder governance for studios, unions, and platforms.
DIAP-Certified Program
Conformance test suite ensures apps verify tokens correctly and emit receipts
Security requirements: key handling, PoP binding, audit logging, revocation checks
Versioned certification tied to app version + integration mode
Ongoing compliance with periodic audits; immediate suspension for violations
Operational Security & Key Management
Formal key ceremonies and rotation schedules for Trust Registry root keys
Issuer key rotation requirements and incident reporting SLAs
Audit logs and tamper-evident storage for critical events
Emergency suspension process for compromised apps/issuers
Standardization Strategy
Publish DIAP spec + schemas + conformance tests publicly
Launch DIAP-Certified program for AI apps and studio modules
Pilot with anchor talent + studio marketing workflow including PVA
Expand to localization/dubbing and distribution verification
Form multi-stakeholder governance for federation