Guilds need machine-readable guardrails. The industry has none.
SAG-AFTRA, WGA, and DGA contracts mandate consent, territory limits, training restrictions, and usage caps. But the industry has no technical mechanism to translate those clauses into machine-readable rules across render farms and AI pipelines. Meanwhile, outside actors — AI companies like ByteDance training on public footage, synthetic replacement generators, post-acquisition entities — aren’t bound by any contract at all. DIAP gives guilds the guardrail system to protect members from both: machine-readable compliance for professional pipelines, and infrastructure to detect and block unauthorized external use.
160K+
SAG-AFTRA members affected
0
Machine-readable contract standards
0
Shared audit standards for AI pipelines
What DIAP Does For Guilds & Unions
Union-Ready Compliance Profiles
DIAP compliance profiles map directly to union contract clauses. Territory limits, usage caps, duration rules, training restrictions, and consent requirements become machine-readable parameters — not just legal text. The Union-Ready profile includes mandatory checkpoints for role and script approval, a final output review window, and a hard separation of training rights from render rights. Distribution holds are supported for active disputes.
Bulk Member Registration
Unions can onboard members in bulk through the DIAP API. Each member gets an Identity Vault with guild-level default consent settings. Members can tighten their own restrictions at any time. No member can have their settings loosened without their explicit approval.
ScriptModule — Built for the WGA
The industry has no infrastructure for script-level consent — no way for writers to track access, and no way for studios to prove authorization. ScriptModule extends DIAP to written works. Writers register scripts with a cryptographic fingerprint. Any AI system that wants to access, analyse, summarise, or train on that work must request explicit authorization first. TRAINING_USE is a separate right — and it defaults to no. Every access is logged permanently via AuthorshipReceipts — protecting writers and giving studios a clean provenance trail.
Two-Layer Authorization — For Every Member
Layer 1 controls whether a member’s identity is even visible to an AI system. Layer 2 controls per-project usage — which studio, which rights, which territory, for how long. Both layers are revocable at any time. A member can be invisible to all AI apps by default and selectively visible only to verified studios.
Emergency Revocation — Shared Safety Mechanism
Emergency revocation blocks unauthorized AI use of a member’s identity — it never breaks valid licenses. If a member licensed their identity to a studio for two years, that agreement is honored. It targets external threats: unauthorized deepfakes, synthetic replacements, post-acquisition misuse. Anyone in the authorized chain — members, agents, studios, and guild representatives — can trigger it when they detect unauthorized use.
Audit Export for Contract Compliance
Guild auditors can pull compliance bundles — token histories, render receipt logs, revocation records, AuthorshipReceipts — in a format that maps directly to contract clauses. Machine-readable records for human review and resolution.
Build a Branded Member Portal
Guilds can build a fully branded member portal on top of DIAP’s open API. Members manage consent settings alongside union cards, dues, and contract terms — without rebuilding the authorization engine from scratch. DIAP provides the infrastructure. The guild provides the interface. Agents and managers can also access the portal through delegation — managing consent for their roster of members, approving token requests, reviewing audit logs, and triggering emergency revocation when they detect unauthorized use.
How It Works For Guilds & Unions
Integrate DIAP API into your member portal
The guild connects DIAP’s API to their existing member management system. Members manage consent settings alongside union cards, dues, and contract terms.
Set guild-level compliance defaults
The union sets baseline Union-Ready compliance profiles that reflect current contract terms. Members inherit these defaults but can tighten restrictions on their own Identity Vaults at any time.
Onboard members in bulk
Bulk registration via the API. Each member gets an Identity Vault with the guild’s default consent settings. No individual setup required.
Audit and verify
Guild auditors pull compliance bundles at any time. Token histories, render receipts, AuthorshipReceipts, and revocation logs map directly to contract clauses for compliance review.
WGA — Writer declines TRAINING_USE. Permanently logged.
A writer registers their screenplay through ScriptModule. Cryptographic fingerprint created.
A studio requests SCRIPT_READ access for development. The writer approves.
Three months later, the studio requests SCRIPT_TRAINING_USE — to feed the script into a model.
The writer sees the request in their vault and declines.
The training pipeline is blocked. The AuthorshipReceipt logs the declined request permanently.
SAG-AFTRA — 50,000 members onboarded. Compliance auto-verified.
Guild integrates DIAP API into existing member portal
50,000 members onboarded with Union-Ready default consent profiles
Studio requests token for 200 members for a dubbing campaign
Compliance profile auto-verifies territory limits and blocks TRAINING_USE
Guild auditor pulls compliance bundle — all render receipts mapped to contract clauses for review
What Guilds & Unions Get
- Union-Ready compliance profiles mapped to contract clauses
- Bulk member registration with guild-level defaults
- ScriptModule — cryptographic script registration, AuthorshipReceipts, TRAINING_USE separation
- Two-layer consent for every member (visibility + per-project usage)
- Emergency revocation — blocks unauthorized use, available to everyone in the authorized chain
- Agent delegation model for talent representation
- Audit export for contract compliance review
- Open API to build a fully branded member portal
- Dispute workflows with distribution hold support