Digital-Replica & Performer-Consent AI Agent

What this agent does

Assembles the consent record, never the authorisation

A replica is registered from production photography, a scan session or a VFX vendor manifest.

A capture is matched to the engagement, so a footage-derived asset is registered like a scanned one.

Reason

A new use is proposed, and it is read against the description of intended use in the signed consent.

An agreement version is pinned to the project — the 2026 SAG-AFTRA TV/Theatrical cycle runs to 30 June 2030.

A consent artefact is checked for bold-and-capitals form, a separate signature and a named project.

Decide

A gap is raised — no consent, a description too thin to reach the use, or a replica with no engagement.

A determination is routed to the named business-affairs executive, who decides whether the use proceeds.

Out

A consent does not lapse on death, so the record outlives the production — scope, not a term, is the limit.

A write happens only inside the approval boundaries agreed during implementation, never ahead of approval.

→ Product statement

The agent matches a use to the consent; a performer signs the consent, a business-affairs executive approves the use, and the union bargains.

Example workflow

One proposed use, register to approval

AgentHuman

1Replica identifiedScan record, VFX vendor manifest, shot list or footage-derived asset inventory

2Consent assembledThe signed artefact, its use description, the notice served and the script version delivered

3Scope match proposedIn scope, out of scope or ambiguous, with the consent text cited and confidence

4Controls appliedArtefact-form checks, California and New York definition tests, clock checks and threshold

No human action required

Stages 1 to 4 run unaided, and no use is authorised at any of them — the agent is assembling, and the executive's lane opens at the confidence gate.

5DecisionBranches at the confidence threshold

High confidence

Goes to the business-affairs executive.

Low confidence

Adds a production counsel read first.

Executive approval

The use is held with its consent citation, its gaps and the confidence.

Approve · Amend · Send to counsel

Approved — cleared for use▼

6Project systems updatedOnly where write access and approval policy allow it

7Outcome evaluatedScope-call reversals, replicas missed at the register and consent findings raised after release

Amendments

A use found unconsented after release is re-determined and counted.

What should not run autonomously

Human approval stays in control

Outside the boundary — human approval required8 items

Signing a digital-replica consent.

Deciding that a proposed use may go ahead.

Serving union notice and bargaining a synthetic.

Stating the articulable business reason for a scan.

Automation boundaryAgent acts unaided

✓Maintain the replica register from capture and vendor sources.

✓Match a proposed use to the consent's description of intended use.

✓Check the consent artefact against the formal requirements.

✓Run the clocks, raise the gaps and hold the use back.

Any write happens inside the boundaries agreed at implementation, never ahead of the approval.

Warranting a consent chain to a distributor.

Distributing a voice model of a named performer.

Setting an ICDR's engagement terms.

Changes to consent, scope or approval rules.

Example output

One proposed use, annotated

Everything the agent determines is attached to the consent it was read from.

Consent-match output · single useIllustrative example

Production

Proposed use

Replica type

Consent cited

Confidence

Determination

Series, season two

Dub of a scene into two territory versions

Employment-based

Signed replica consent

92%

In scope — dubbing described

As receivedTaken from the register and the signed consent on file — nothing on this side is written by the agent.

Consent evidence used Separate signature Use description Script version on file

Why this determinationThe consent describes dubbing for this picture — the call the executive approves.

ActionApproveAmendSend to counsel

What the score decidesBelow the configured threshold the use picks up a counsel read before it reaches the executive.

Value

Where AI adds value

The same four claims, placed at the point in the workflow where each one applies.

Where the value landsValue 01 – 04

Each registered useFrom the replica register

03Matching

Match against the consent

Read the signed consent's description of intended use, the notice evidence and the script version on file.

01Approved path

A replica need never be scanned

Footage-derived likenesses belong in the register beside scanned ones — the trigger is existence, not capture.

02Human review

Answer what other agents defer

Our dubbing and marketing agents generate no voice or likeness; this one holds the record when a vendor does.

04Build an evidence trail

The use, the consent it was matched to and the executive who approved stay on the project.

Integrations

Typical integrations

Five system groups connect to the same agent. Which of them are in scope is decided in discovery.

Casting and engagementCasting Networks · Breakdown
Deal memos · Exhibit E

Production and VFXShotGrid · ftrack
Vendor manifests · shot lists

Business affairsRightsLogic · FilmTrack
DocuSign · contract stores

Agent

Digital replica & consent

Reads the register
Matches to consent
Holds for approval

Asset managementMAM · DAM libraries
Iconik · Dalet

Observability & evaluationOpenTelemetry · Langfuse
Supported monitoring/evaluation sources

Integration availability depends on the client's existing systems and API access.

Agent controls

Six layers between the model and the master

Six controls, the outermost first. What the whole set misses is written into the map below.

L6 · Outermost — last line of defenceInward → L1 · closest to the model

L6Rollback / safe modeHold the use at unconsented when evaluation or production signals degrade.Roll back

L5Version monitoringTrack model, prompt, consent-rule and agreement-version changes.Track

L4TraceabilityRecord the replica, the consent cited, the determination and the approval time.Record

L3Executive approvalHold the use for the named executive; a use already in a delivered master is past every layer here.Gate

L2Policy guardrailsTest the consent artefact against the formal requirements; a failure returns the use unmatched.Restrict

L1Confidence thresholdsRoute low-confidence scope calls to a counsel read before the executive sees them.Require review

Model coreDetermination proposed — in scope, out of scope or ambiguous, with citations and confidence

L1 – L2Test whether a use may stand

L3Puts the release in an executive's hands

L4 – L5Keep the use and the consent behind it

L6Holds the use at unconsented when signals degrade

How Nestack evaluates it

Evaluate the consent workflow — not only the final determination.

Coverage runs the whole depth of the workflow, and every layer is cut by slice.

Surface — the use the company ships

Depth of coverage ▼

E1Final-output evaluationWas the scope call right against the consent as written?

E2Step-level evaluationDid the agent use the right consent, script version and state test?

E3Tool evaluationDid it read the correct replica asset and the correct project?

E4Confidence calibrationDo low-confidence determinations actually attract more amendments?

E5Slice evaluationHow does performance change across specific replica types?

E6Business outcomeHow many uses needed an amendment or a correction after release?

Floor — the outcome the studio answers for

Failure modes

Where each failure originates in the agent

Seven failure modes, placed at the stage each one originates.

Agent lifecycleDirection of processing →

01 · Retrieval1 mode

RY-03

Register built from scans

A footage-derived replica never enters the register.

Stage gathersScan records, vendor manifests and shot lists

02 · Reasoning2 modes

RY-04

Buried consent accepted

A signed deal memo is read as a replica consent.

RY-06

Wrong script version

An alteration is cleared on a revision never seen.

Stage proposesThe scope call, the consent cited and confidence

03 · Tool / write2 modes

RY-02

Determination taken as approval

An assembly step stands where approval should be.

RY-05

Transfer window lapses

A library sale runs the window unserved.

Stage writesOnly where write access and approval policy allow it

04 · Output1 mode

RY-01

Use outside consent scope

A use is cleared that the description does not reach.

Stage returnsThe determination the executive signs against

05 · Change / Version1 mode

RY-07

Silent scope widening

A model or rule change loosens what counts as in scope.

Stage tracksModel, prompt, consent rules and agreement version

Sev-1 · a use ships with no valid consent Sev-2 · a wrong scope call reaches the file Sev-3 · source degrades, use routes to review

See the complete Media & Entertainment failure-mode catalogue →

Affected slices

Consent coverage can hide one exposed cohort

A slate-wide consent-match rate can look acceptable while a small number of replica cohorts carry most of the unmatched uses. Nestack reports the unmatched-use rate by slice, not only in total.

Slice performance — reported separately, not only in aggregateIllustrative example

Slice	Failure rate	Lift	Status
Footage-derived replicas	9.4%	3.8×	Review
Off-card background engagements	7.2%	2.9×	Review
Deceased-performer catalogue	4.4%	1.8×	Watch
Scanned employment replicas	1.6%	0.7×	Normal

Bar: unmatched-use-rate lift vs. scanned-replica baseline · scale 0–4.0× · tick marks the 2.0× review threshold 2 of 4 slices over threshold

Evidence-linked improvement

The loop closes on a consent case

A cycle closes when the unconsented use is a case the next release has to catch. That suite is what the next use proposed is measured against.

Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn

01Detect

Unmatched-use rate rises in a replica slice.

02Diagnose

The performer who agreed to one picture and appeared in a second is traced to one cause.

03Improve

The fix carries a number, and the uses that forced it travel with it.

04Verify

Nothing goes out until every touched consent case has passed again.

05Learn

It is kept for good, and the consent rules are amended in the same commit.

Learn → DetectThe return edge. The next detection runs against a suite one consent case longer.

Typical build scope

Twelve workstreams across six weeks

The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, consent workflow, evaluation, integration, then production validation and handover.

Workstream Week 1Week 2Week 3Week 4Week 5Week 6

01Consent workflow discovery and boundary definition.

02Register, casting and VFX source review.

03Consent-artefact, scope and state-rule mapping.

04Replica register ingestion and matching.

05Scope-match logic and consent binding.

06Confidence scoring and gap routing.

07Executive approval workflow.

08Asset and contract-system integration.

09Consent and scope cases.

10Guardrails and approval controls.

11Project-trail instrumentation.

12Deployment, documentation and Agent Care handover.

12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallel Final scope and sequence confirmed in discovery

Engagement tiers

What each tier includes

Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.

Capability✓ in scope · — not at this tier PilotOne title, one office ProductionProduction business affairs AdvancedMultiple slates / labels

Introduced at Pilot

Matching to your consents and rules✓✓✓

Executive approval✓✓✓

Scope-match baseline✓✓✓

Introduced at Production

Reporting by production—✓✓

Approval workflow in your systems—✓✓

Approved write-back—✓✓

Asset-management integration—✓✓

Introduced at Advanced

Multi-territory catalogues——✓

Multi-stage legal approvals——✓

High replica volume——✓

Multi-agreement consent controls——✓

Build price From $5,000 From $8,000 Custom quote

Final build priceConfirmed after discovery based on integrations, workflow complexity, transaction volume, approval controls and deployment requirements.

Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.

What we need from you

What you bring, and what we build with it

Each input maps to a piece of build scope and a week in the delivery timeline.

You bringWe build with it

01Your replica register and capture sources → Replica register ingestion and source mappingWeek 1

02Representative signed consents → Scope-match baseline and consent-artefact checksWeek 2

03Your approved consent forms and scope language → Consent-artefact, scope and state-rule mappingWeek 1

04Access to relevant APIs, feeds or exports → Register, casting and VFX assessment, then integration setupWeek 2

05Uses you would not want defended → Scope cases and failure-mode testingWeek 4

06What no use may rest on → Confidence scoring, gap routing, guardrails and approval controlsWeek 3

07Named business-affairs executives to approve → Executive approval workflow, then pilot and production validationWeeks 5–6

Nothing else is required Deployment, documentation and Agent Care handover are ours.

Delivery timeline

Four phases across six weeks

The bands are drawn over the weeks each phase genuinely needs, so the fifth doubles.

Phase W1W2W3W4W5W6

Discovery W1

Build W2 – W3

Evaluate W4 – W5

Pilot & Launch W5 – W6

Week focus W1Consent workflow discovery, scope mapping and the automation boundary W2Register, casting and VFX integration and the match baseline W3Matching workflow, confidence logic and approval controls W4Evaluation suite, consent-artefact checks and failure-mode testing W5Asset and contract-system integration, pilot uses and corrections W6One production run under the business-affairs executive, then Agent Care handover

Reading the bandEach bar covers only the weeks its work is named in. Week 5 carries two phases because it does.

At the end of W6Validation closes on live consents, and Agent Care picks up monitoring.

DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.

Next step · Media & Entertainment AI agent

Build a digital-replica consent agent around your business-affairs file.

Show us your capture sources, your consent forms and who approves a use. If any replica on your slate was built from production footage rather than a scan, the consent regime already reaches it.

Discuss this agent →

Nestack Agents · Digital replica & consentAGT-ME-13 · Agent Care available after launch