AI companies are ingesting scripts with no authorization layer, no audit trail, and no guardrails.
The studio that hired you isn’t the problem — your development deal works. The gap is in the infrastructure: AI companies ingesting scripts for model training with no authorization layer, overseas entities accessing leaked material, and post-acquisition strangers inheriting work they never commissioned. The industry has no shared standard for script-level consent — no way to log access, no way for writers to know it happened, and no way for studios to prove their authorization was scoped correctly. ScriptModule is the infrastructure layer for written work — it gives writers visibility and gives studios a cryptographic provenance trail. The same protocol that covers an actor’s face now covers a writer’s script.
0
Machine-readable authorization standards for scripts
No
TRAINING_USE defaults to no — always
∞
AuthorshipReceipts — permanent, tamper-proof
What ScriptModule Does
Cryptographic Script Registration
A writer registers their screenplay, treatment, story bible, outline, or dialogue. A cryptographic fingerprint is created. From that point, any AI system that wants to access, analyse, summarise, or generate derivatives from that work must request explicit authorization first. No valid token, no access.
Four Separate Rights — All Explicit
SCRIPT_READ — access for development or breakdown. SCRIPT_DERIVATIVE_GENERATION — generate new scenes, dialogue, or variants. SCRIPT_EXPORT — export the script or portions. SCRIPT_TRAINING_USE — use the script to train or fine-tune an AI model. TRAINING_USE is always separate and always defaults to no.
AuthorshipReceipts — Permanent Provenance
Every access generates an AuthorshipReceipt — a timestamped, tamper-proof record of who accessed the script, when, under what authorization, and what they did with it. If a question arises, the provenance chain is already built. Receipts are exportable for compliance review, guild auditing, and dispute resolution.
Two-Layer Authorization
Layer 1 controls whether a script is even visible to an AI system. Layer 2 controls per-project usage. A script can be invisible to all AI apps by default and selectively accessible only to verified studios under specific terms.
Emergency Revocation — Shared Safety Mechanism
Emergency revocation blocks unauthorized AI access to your script — it never breaks valid licenses. If a studio has a legitimate two-year development deal, that deal is honored. It targets usage outside your agreements: the overseas entity that accessed your work without authorization, the AI company that ingested it with no license. Anyone in the authorized chain — writers, agents, studios, or guild reps — can trigger it.
Guild Integration
ScriptModule is built to align with WGA and international writers' guild structures. Compliance profiles include mandatory checkpoints, exportable statements for representatives, and hard separation of training rights from all other rights. Guilds can build a branded member portal on top of DIAP's open API.
Free for Writers — Always
ScriptModule is free for individual writers. Studios and platforms pay for API access. Writers never do.
TRAINING_USE — Always Separate
A studio requesting SCRIPT_READ for development does not get SCRIPT_TRAINING_USE. Ever. These are independent authorizations. No right is implied by any other right.
How It Works
Register Your Script
Upload your screenplay, treatment, or story bible. A cryptographic fingerprint is created — your work is now on-chain without exposing the content.
Set Your Rights
Choose independently which of the four rights (READ, DERIVATIVE_GENERATION, EXPORT, TRAINING_USE) are available — and to whom. TRAINING_USE defaults to no.
Studios Request Access
Any AI system or studio must request a valid token for the specific rights they need. Writers or their representatives approve or decline each request.
Every Access Is Logged
AuthorshipReceipts record every interaction permanently. If a dispute arises, the provenance chain is already built and exportable.
Real Scenario — Script Authorization Flow
A screenwriter registers their pilot script through ScriptModule
Studio requests SCRIPT_READ access for development breakdown
Writer reviews the request in their vault and approves
Three months later, studio requests SCRIPT_TRAINING_USE to feed script into a model
Writer sees the request and declines — TRAINING_USE is blocked
AuthorshipReceipt logs the declined request permanently
Training pipeline is not authorized. Both parties have a clear, permanent record.
What Writers Get
- Cryptographic script registration — fingerprint-based, not just metadata
- Four independent rights: READ, DERIVATIVE_GENERATION, EXPORT, TRAINING_USE
- TRAINING_USE defaults to no — always separate, always explicit
- AuthorshipReceipts — permanent, tamper-proof access log
- Two-layer consent — visibility before usage
- Emergency revocation — blocks unauthorized use without affecting valid licenses
- Guild-aligned compliance profiles (WGA and international)
- Free for writers — always