THE PROOF PROTOCOL Rights infrastructure for generative media

Before generation.
After distribution.

Proof makes authority operational across the entire synthetic-media lifecycle: issue the rights, authorize the job, bind the output and verify every use.

ONE PROTOCOL / FOUR DECISIONS

01Issue

What rights exist?

02Authorize

May this job run now?

03Bind

What was actually created?

04Verify

Is this use valid here?

SUPPORTED BYRegistry · Status · Audit

PRODUCT SURFACES A complete control loop

Four services.
One chain of authority.

Each service answers a different question. Keeping them separate prevents a valid signature from being confused with permission to perform any action, anywhere, forever.

01

Proof Issue

What rights exist?

Transforms verified authority, explicit consent and approved terms into a signed, portable and revocable licence credential.

API
POST /v1/licence-requests
OUTPUT
LICENCE CREDENTIAL
Read specification
02

Proof Authorize

May this job run now?

Evaluates the licence against the requester, reference asset, provider, model, script, territory, channel, time and usage limits.

API
POST /v1/authorizations
OUTPUT
ONE-TIME GRANT
Read specification
03

Proof Bind

What was actually created?

Registers the final output, cryptographic digest, optional durable fingerprint, provider evidence and C2PA manifest reference.

API
POST /v1/assets
OUTPUT
BINDING RECEIPT
Read specification
04

Proof Verify

Is this use valid here?

Returns an explainable allow, deny or review decision from signature, status, policy, asset binding and distribution context.

API
POST /v1/verify
OUTPUT
DECISION RECEIPT
Read specification
TRUST FOUNDATIONS
Proof Registry

Identity, IP, organisations and mandates.

Proof Status

Expiry, suspension and revocation.

Proof Audit

Append-only events and receipts.

Proof Anchor

Optional, chain-agnostic external anchoring.

END-TO-END DEMO Marcus Vale × Northstar Sports

One campaign.
Four proof moments.

A fictional but realistic journey showing how a GenAI platform would use Proof before and after generating a licensed fan video.

Marcus Vale, fictional football player
FICTIONAL IDENTITYMarcus Vale

International football player

RIGHTS CEREMONY

Marcus approves one precise campaign.

Northstar Sports requests 50 multilingual fan videos. Marcus or his authorised agency approves the purpose, script family, channels, territories, providers, duration, duties and prohibitions.

Open the complete token record ↗
REQUEST CONTEXTJSON
subject: Marcus Vale
licensee: Northstar Sports
purpose: Fan welcome campaign
territories: FR, GB
max_assets: 50
ISSUEDAAP-LIC-2026-C91F

Signed VC · active until 30 Sep 2026

TRUST ARCHITECTURE Separate what must not be confused

Evidence, authority
and execution.

Proof uses different artefacts for durable rights, temporary execution and later verification. Compromise of one layer must not silently rewrite another.

HUMAN + LEGALIdentity, mandate, consent, contract

Private, encrypted evidence. The legal agreement remains authoritative.

DURABLE CREDENTIALSigned licence token

Portable policy, issuer key, dates, status reference and evidence digests.

EPHEMERALGeneration grant

One requester · one job · short expiry

DURABLEAsset binding

Output hash · provenance · counter

CONTEXTUALVerification receipt

Allow, deny or review with stable reasons and checked-at time.

01No self-issued rights

A platform can request issuance, never invent consent.

02No bearer licence

Possession alone never authorizes a generation.

03C2PA complements Proof

Media history and rights authority remain distinct.

04No chain dependency

Blockchain anchoring is optional and replaceable.

INTEGRATION MODES Start with the authority available

Bring a token.
Or request one.

Platforms can adopt Proof without becoming issuers. Enterprise partners with an existing mandate can later enable tightly constrained just-in-time issuance.

MODE 01 / STANDARD

Bring Your Own Proof

The user presents an existing licence. The platform calls Proof Authorize before every generation and Proof Bind after output.

Fastest integration · lowest governance burden
MODE 02 / REQUEST

Request a licence

Without a token, the platform opens a Proof Issue workflow. The rightsholder approves outside the generation interface.

Best for marketplaces and new commercial uses
MODE 03 / DELEGATED

Just-in-time issuance

An accredited partner issues only inside a pre-approved mandate, schema, spend, scope and audit policy.

Enterprise profile · enhanced controls required