# Aja Consent NIL Ledger

## Scope

V2 capture sessions cannot enter Aja ingest unless each performer has an active
`@aja/consent-management` record and a validated Themis NIL ledger link. The V2
consumer package is `@v2/aja-consent-nil-ledger`.

## Contract

`@v2/aja-consent-nil-ledger` records:

- performer-scoped Aja consent for studio mocap, face capture, voice capture,
  derivative retarget, and marketing BTS purposes;
- Themis `@themis/likeness` license ID;
- immutable `rightsManifestSha256` from `V2/legal/rights-manifest.json`;
- `consentChainRefs[]` pointing back to the Aja consent record;
- region coverage and collection evidence hash.

The wrapper treats `@themis/likeness` as a contract until the reciprocal Themis
library task lands. It does not import or depend on a nonexistent local Themis
package.

## Revocation

Consent withdrawal emits `v2.mocap.performer_consent.revoked` and links it to
the Themis `themis.license.revoked` cascade. The revocation payload blocks
future Aja processing, blocks Bellona cook for dependent motion assets, and
requests associated capture-data deletion by default.

## Validation

`V2/ue/Tools/check-v2-aja-consent-nil-ledger.py` enforces the package, service
adapter, CI, documentation, and TODO wiring for this contract.