DIAP Protocol digital identity network visualization
Digital Identity Authorization Protocol

The Universal Consent Layer
for AI Identity

One protocol that lets actors, creators, and studios control exactly how AI uses their face, voice, expression, and motion — across every app and pipeline. Built on consent. Revocable by default. Every frame auditable.

Consent-First

Blocked unless authorized

Two-Layer Consent

Visibility + Usage control

Provenance

Verifiable receipts & watermarks

The Problem

The Internet Lacks Identity Infrastructure

AI generation quality has crossed the “convincing” threshold. The result is legal risk, reputational harm, fragmented deals, and talent opting out entirely.

Fragmented AI identity systems visualization showing disconnected face outlines and warning indicators

Unauthorized Generation at Scale

AI makes it cheap to synthesize convincing humans. Likenesses and voices are generated without consent, creating legal risk and reputational harm.

Fragmented Enforcement

No standard method exists to request consent, enforce scope limits, or prove authorization across apps and vendors.

No Standard Verification

Platforms and distributors lack a shared verification method to confirm whether synthetic content was authorized.

Weak Audit Trails

Studios, unions, and talent representatives have no reliable way to audit how identity assets are being used.

Value Misalignment

Value accrues to platforms while talent lacks residual-like economics for their digital identity usage.

Visibility Exposure

Even being searchable or selectable inside an AI app can violate talent intent if platform access was never granted.

Why Now

Generation quality crossed the convincing threshold
Studios need provable compliance to reduce liability
Talent demands control, visibility & compensation
Platforms need scalable deepfake verification
Regulators focus on biometrics, consent & AI disclosures
The Solution

Two-Layer Consent Engine

DIAP distinguishes between platform visibility and project usage authorization, preventing premature exposure of identities inside AI applications.

Two-layer consent engine architecture showing data flowing through blue and cyan authorization layers
Layer 1

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.

Granularity:By app_id, app_class (studio-only vs public), issuer_id, organization (KYB), or distribution channel
Effect:If PVA is denied, identity is invisible and unselectable — no project request possible
Economics:Platform access can be free, paid, invite-only, or contract-bound
Layer 2

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.

Scope:Time window, render limits, rights, territory, medium, rating constraints
Modes:Per-render, per-project, quota-based, or auto-approve under limits
Provenance:Every authorized output carries a watermark and independently verifiable receipt

Enforcement Flow

01

Certification Check

App verifies its own DIAP-Certified status via Trust Registry

02

Visibility Check (PVA)

App checks Platform Visibility Authorization for target identity

03

Identity Displayed

If allowed, identity may be shown as selectable under listing constraints

04

License Request (PCUA)

On selection, app creates a scoped LicenseRequest for the project

05

Token Issuance

Issuer evaluates request against compliance profile; approval yields signed token

06

Execution & Receipts

Gateway verifies token, enforces scope, produces outputs and provenance receipts

Human-Rooted Authority

Least Exposure

Interoperable

Revocable

Auditable

Policy-First Safety

Architecture

Protocol Components

A modular, build-ready architecture designed for security, interoperability, and enterprise-grade deployment.

DIAP Identity Vault secure digital storage with biometric data visualization

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 / Consent 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 kill switches.

Execution Gateway

The enforcement point. Verifies tokens, enforces policy, routes generation through adapters, 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.

VoiceModule

Voice embeddings and synthesis parameters

VOICE_RENDER
FaceModule

Facial geometry, texture, and appearance

FACE_RENDER
ExpressionModule

Facial expression mapping and control

EXPRESSION_RENDER
MotionModule

Body motion capture and kinematics

MOTION_RENDER
FootprintModule

Optional persona metadata (not required for core auth)

Rights Taxonomy & Scope

Rights

VOICE_RENDERFACE_RENDEREXPRESSION_RENDERMOTION_RENDERTRAINING_USEDISTRIBUTION_USE

TRAINING_USE is explicitly separate from render/inference rights.

Scope Dimensions

app_idissuer_idproject_idcampaign_idmediumratingterritorytime_windowmax_rendersmax_seconds

Approval Modes

PER_RENDERPER_PROJECTQUOTAAUTO_APPROVE_UNDER_LIMITS
Technical Specification

Protocol Mechanics

Certificates, tokens, receipts, and verification endpoints — the building blocks of machine-enforceable consent.

Proof-of-Consent Certificate

VERIFIED

Every AI-generated frame carrying a human likeness embeds a DIAP PoC Certificate in its metadata. This is the cryptographic proof that consent was obtained before render.

DIAP PoC Certificate
cert_7f3a9b2e-d1c4-4e8f-a6b2-9f0e3c7d1a5b
Identity Subject
Subject IDusr_talent_a8f2d1
Modules UsedFACE · EXPRESSION · VOICE
KYA StatusVerified — Tier 2
Authorization Chain
License JTIlic_9f2e4b71
Policy ProfileDIAP-Brand-Safe:v1
Expires2026-03-16T14:32:00Z (24h)
Authorized Scope
Campaigncmp_poster_global_2026
TerritoryGLOBAL
Max Renders500 (127 used)
Provenance
Output Hashsha256:e3b0c44298fc...
Watermarkdiap-v1 embedded
SignatureES256 — Valid
Signed by DIAP License Authority · Issuer: issuer_01
Consent GrantedToken IssuedRender ExecutedPoC Certificate Embedded

Verification Semantics

Token Verification

Signature chain to certified issuer in Trust Registry + PoP binding + scope checks + revocation status

Receipt Verification

Signature chain + output hash match + watermark payload validation for downstream proof

Platform Verification

Distribution platforms can require valid receipts for any monetized synthetic human content

Revocation & Threat Model

Short-lived tokens reduce blast radius by limiting exposure window

Revocation Registry: revoke by license_jti, app_id, or campaign

Push-based revocation for emergency kill-switch behavior

Gateway enforcement: registry check required at render time

Threat Model

ImpersonationAttacker pretends to be a legitimate app/studio
Token TheftStolen tokens used for unauthorized renders
Replay AttacksReuse of old approvals beyond scope/time
Insider AbuseExporting identity modules or misusing privileged access
Model InversionReconstruct identity from embeddings/outputs
Watermark RemovalAttempts to strip provenance markers
Fraudulent ReportingUnder-reporting events to reduce payouts

Trust Registry (Root of Trust)

The DIAP Central Authority anchors global verification through the Trust Registry. It maintains certification status and root trust keys that allow any participant to validate whether a token/receipt is authentic and whether an issuer/app is compliant.

Root Keyset

Signs Trust Registry snapshots and updates

Issuer Registry

Approved License Authorities with public keys

App Registry

DIAP-Certified apps, versions, and status

Revocation Endpoints

Per-issuer revocation check endpoints

Policy Profiles

Canonical IDs for compliance conformance tests

Key Rotation

Documented procedures for compromise response

DIAP v1.1 Addendum

ScriptModule

Writer & authorship protection. A first-class protected asset type for authored writing and project literary materials — extending DIAP with consent-first script governance.

Consent-First
Least Exposure
Separable Training
Auditable Provenance
Revocation

Non-goal: ScriptModule is not a replacement for copyright registration, chain-of-title, or legal guild processes. It is a technical enforcement 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.

Script Asset

Any authored writing used in development/production — screenplay drafts, outlines, treatments, bibles, pitch decks, scene text, dialogue, alt-lines, script notes, revisions.

Author

The natural person(s) who authored the Script Asset, or an authorized rights holder/representative (estate, production company) acting on their behalf.

Derivative Generation

Any AI-assisted generation using Script Assets as input/context — new scenes, dialogue, scene variants, summaries, character breakdowns.

Training Use

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)

Hard rule: SCRIPT_TRAINING_USE must be explicitly granted and must NOT be implied by any other right.
Use Cases

Industry Implementation

From film production to distribution verification, DIAP provides the consent 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 receipt/watermark for verification

Audit bundles for legal/compliance; usage statements for talent

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 enforced 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.

1

Studio uses DIAP-Certified design tool (e.g., Nano Banana Studio Tier)

2

Tool checks Platform Visibility Authorization for Actor X

3

If allowed, Actor X is selectable under listing constraints

4

Studio requests marketing-static rights (FACE_RENDER + EXPRESSION_RENDER) under DIAP-Brand-Safe

5

Actor/rep approves with optional creative-lock checkpoints

6

Design tool generates variants; only authorized final selects are exported

7

Every exported final select carries receipt/watermark

8

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.

Compliance Profiles

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

Approval: PER_RENDER
Training Use: DENY
Visibility: HIDDEN — Studio-Only
VOICE_RENDERFACE_RENDEREXPRESSION_RENDERMOTION_RENDER

Brand-Safe

Commercial use with reputational safety

Approval: PER_PROJECT + CREATIVE_LOCK
Training Use: DENY_BY_DEFAULT
Visibility: Discoverable / Invite-Only / Hidden
VOICE_RENDERFACE_RENDEREXPRESSION_RENDER

Union-Ready

Union-style approvals and dispute workflows

Approval: PER_PROJECT + SCRIPT_ROLE + FINAL_OUTPUT_REVIEW
Training Use: SEPARATE_NEGOTIATION_REQUIRED
Visibility: INVITE_ONLY
VOICE_RENDERFACE_RENDEREXPRESSION_RENDERMOTION_RENDER

Indie Creator

Low friction licensing with provenance

Approval: AUTO_APPROVE_UNDER_LIMITS
Training Use: DENY
Visibility: INVITE_ONLY
VOICE_RENDERFACE_RENDER

Enterprise-Verified

High assurance for studios/enterprises

Approval: PER_PROJECT
Training Use: Per negotiation
Visibility: STUDIO_ONLY
All render rights (per negotiation)

Education / Non-Commercial

Learning/research with strict constraints

Approval: PER_PROJECT
Training Use: N/A
Visibility: HIDDEN
Per project scope
Pricing

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.

Platform access & SDK license
Full access to registry, vault integration, and developer tools
Annual certification & audit
Initial conformance testing, annual re-certification, and compliance audit
Seat-based studio access
Named seats for dashboard, approval workflows, and campaign management
Baseline API capacity included
A generous base tier of visibility + verification calls bundled in

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.

Monthly receipts issued
Each RenderReceipt or AuthorshipReceipt generated counts as a metered unit. Covers provenance tracking for every render or script operation.
Monthly API calls (visibility & verification)
PVA/SVA visibility checks, token verification, receipt verification, and registry resolution calls. Metered per-call beyond the base tier.
Annual certification + audit fees
Conformance testing, security review, and ongoing compliance monitoring. Billed annually per app/entity being certified.

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.

Governance & Roadmap

Standardization Path

DIAP starts centralized for speed and evolves to federation as unions, studios, and major platforms participate. Common verification always anchored.

Current
Phase 1

Centralized Pilot

Single DIAP Central Authority + delegated issuers. Publish spec, schemas, and conformance tests publicly. Launch DIAP-Certified program.

Phase 2

Multi-Issuer Expansion

Multiple certified issuers (studios, unions) listed in the registry. Pilot with anchor talent + studio marketing workflow. Expand to localization/dubbing.

Phase 3

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 enforce 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

01

Publish DIAP spec + schemas + conformance tests publicly

02

Launch DIAP-Certified program for AI apps and studio modules

03

Pilot with anchor talent + studio marketing workflow including PVA

04

Expand to localization/dubbing and distribution verification

05

Form multi-stakeholder governance for federation