A buyer should be able to move from a final AI face or voice output back through every decision that authorized it. This reference map shows what each record proves and what it cannot prove alone.
Synthetic reference only. No real person, consent, payment or campaign is represented on this page. The chain below is an evidence anatomy. The linked receipt experiment uses an explicitly synthetic signed test fixture.
| Stage | Record to retain | What it establishes | What it cannot establish alone |
|---|---|---|---|
| 1. Identity | Verification result tied to the person | Which real person completed the identity process | Permission for a campaign |
| 2. Consent of record | Signed platform agreement, completed identity check and reviewed consent video | Where the person's explicit agreement, verified identity and reviewed consent record join | The commercial scope of every future use |
| 3. Signed licence | Both signatures, exact terms and document hash | Who agreed to which buyer, campaign, use, assets and term | That a particular file was produced under the licence |
| 4. Secured payment | Payment state and agreed allocation | That the commercial condition was secured before unlock | Identity permission or output integrity |
| 5. Controlled generation | Decision, asset version and generation event | Which authorized route and covered asset produced the event | That the final bytes are unchanged |
| 6. Registered output | Output hash, licence references, content credential and signed receipt | How the released file connects to the recorded workflow | Any upstream evidence that is absent or invalid |
| 7. Revocation | Status event, effective time and existing-output rule | Whether future generation remains available and how the change was recorded | A universal rule for every previously released output |
The buyer package turns the map above into one inspectable JSON document. It names a synthetic person, buyer and campaign, then shows the record expected at every stage and states separately what each record establishes and what it cannot establish.
| Package stage | Illustrative result | Required caution |
|---|---|---|
| Identity | Illustrative verified participant and reviewed identity binding. | No real person or identity check is represented. |
| Consent of record | Illustrative signed platform agreement joined to the identity check and reviewed consent-video record. | No real signature, video or consent is represented. |
| Licence scope | Illustrative two-party document hash covering buyer, campaign, use, channels, territory and term. | No legally effective instrument is created. |
| Payment | Simulated secured state before licensed generation. | No charge, settlement, payout or money movement occurred. |
| Production decision | Illustrative permit bound to the scope and asset version. | No provider execution or media generation is claimed. |
| Output receipt | A separate genuine Ed25519 signature over an explicitly synthetic approved-variation fixture. | The signed fixture is not the licence, consent, payment or campaign above. |
| Current status | Illustrative revocation stops future generation while preserving history. | It is not a real revocation or a universal rule for exported files. |
Download the synthetic buyer evidence package ยท Download the signed test receipt
Composite test evidence. The buyer package explains the whole chain. The signed receipt is a separate synthetic cryptographic fixture. They are intentionally not presented as one production transaction.
The interactive receipt walkthrough contains one genuine Ed25519 signature over an explicitly synthetic test record. Change its permission reference, compare different bytes or select an unknown key to see the verifier refuse unsupported conclusions.
That experiment deliberately does not invent identity, consent, payment, licence or revocation evidence. A passing receipt check is one link, not permission for a real campaign.
Pass, fail and unknown must remain different findings. A valid signature can pass while permission is still unknown because the agreement was not supplied. A file hash can fail while the receipt remains intact. An unfamiliar signing key can be uncheckable without being proven fraudulent.
Try the signed synthetic receiptReview the agreement clauses
This evidence map explains how records fit together. It is not a certification, a production transaction or legal advice.
The chain should connect identity, explicit consent, the signed licence, secured payment, the covered asset, the generation event, the registered output and current status.
No. It can prove the integrity of its signed payload. The identity, consent, licence scope and current status still require their own evidence.
No. The page is a synthetic reference map. The linked receipt walkthrough uses test data explicitly marked as synthetic and represents no real person or campaign.
It shows when future generation stopped and prevents a later reviewer from mistaking an old valid receipt for proof that new generation remains authorized.