What must an AI likeness licence prove?
An AI likeness licence must prove who agreed, what they agreed to, which identity asset and campaign the permission covers, that payment was secured, how generation stayed inside scope, which output was released and whether permission remains active. A contract, synthetic-media label or provenance credential can answer part of that question. None answers all of it alone.
The seven required records
| Record | What it establishes | Fail-closed question |
|---|---|---|
| 1. Verified identity | The participant is the real person whose face or voice is proposed for use. | Can the platform connect the participant to an independently verified identity without exposing private KYC material? |
| 2. Reviewed consent | The identified person explicitly chose to participate before listing, capture, cloning or use. | Was consent reviewed before the identity asset entered the licensing workflow? |
| 3. Signed licence scope | Both parties accepted one document hash covering the buyer, campaign, identity elements, use, script rules, approvals, channels, territory and term. | Does the proposed use fit the signed scope exactly? |
| 4. Secured payment | The agreed payment is secured before licensed generation or delivery unlocks. | Is the commercial obligation secured before the buyer receives value? |
| 5. Terms-locked generation | The covered asset version and production route are restricted to the signed script and terms. | Can a user generate or export something the licence does not permit? |
| 6. Verifiable output receipt | The released file connects to the person, asset version, licence, generation event and content credential. | Can an independent party check the receipt and the output bytes? |
| 7. Current licence status | Expiry, pause or revocation is visible and future generation stops when permission is no longer active. | Can the production system act on the current status instead of relying on a stale copy? |
The decision rule
If any required record is missing, disconnected or stale, the use is not ready on SocialGravity. The missing record must be resolved before generation, delivery or release proceeds. Access to an asset is never treated as permission to use it.
Face and voice need different delivery controls
A licensed face workflow may use an approved reference pack through the agreed production route. A licensed voice workflow stays on SocialGravity’s hosted, metered generation route, so the buyer receives approved output rather than reusable model weights. Both routes bind the exact asset version to the licence and the release record.
What a buyer should retain
- The signed agreement hash and human-readable scope.
- The covered identity asset version and approved production route.
- Confirmation that payment was secured before generation or delivery.
- A receipt for every registered output, including its file hash and generation event.
- The current licence status and the agreed treatment of outputs already released.
What this standard does not establish
It does not claim that every lawful AI likeness arrangement must use SocialGravity, that a technical receipt decides legal validity, or that one workflow replaces counsel, union terms, platform rules or jurisdiction-specific clearance. It states the evidence and controls SocialGravity requires before its own licensed generation and delivery can proceed.
Apply the buyer checklistInspect the evidence chain
This is SocialGravity’s public operating standard. It is not an industry standard, legal opinion or claim of regulatory compliance.
Common questions
What is the SocialGravity AI likeness licensing standard?
It is a seven-record operating standard connecting verified identity, reviewed consent, signed scope, secured payment, terms-locked generation, a verifiable output receipt and current licence status.
What proof should an AI likeness vendor provide?
A buyer should receive checkable evidence of the person, permission, scope, asset version, payment gate, controlled production route, each released output and the licence’s current status.
Is a signed contract enough to prove an AI likeness output was authorized?
No. A contract can establish agreed terms, but the buyer still needs a reliable connection from those terms to the asset version, generation event, specific output and current licence status.
Is this an industry or legal standard?
No. It is SocialGravity’s public operating standard for its own licensing workflow and does not replace legal advice or jurisdiction-specific requirements.