Name the instruments a title's structure requires and the ones that do not exist, run the statutory registration, recordation and termination clocks against each, and hold the defect list for counsel.
A chain is assembled from the title's structure — credited writers, depicted persons, clips, cues and locations.
02
An instrument is matched to each required link, and any link with nothing behind it is reported as absent.
Reason
03
A signature is tested against §204(a) — unsigned, wrong entity, or a loan-out with no inducement, all fail alike.
04
A clock falls due — §412 from first publication, §205(d) from execution, §203 and §304 from each grant.
05
A recordation protects only where the work is registered under §205(c), so an unregistered work registers first.
Decide
06
A transfer routes to the online recordation system opened in 2022; a termination notice may still need paper.
07
A closing §205(d) window is raised as a special-handling candidate against the Office's working-day target.
Out
08
A defect is held with the instrument it was measured against, the clock behind it and the report it feeds.
09
Execute write actions only inside the approval boundaries agreed during implementation.
→Product statement
The agent names gaps and tracks clocks; counsel opines on the chain, a producer signs the E&O application, and the underwriter binds on it.
Example workflow
One title, structure to opinion
AgentHuman
1Title structure receivedProduction files, delivery schedule, cast and music lists, contract repository
2Required instruments enumeratedThe writers, depicted persons, clips, cues, locations and archival frames the structure implies
3Defect list proposedAbsent links, open clocks, expedite candidates and confidence
4Controls applied§204(a) writing checks, §205(c) registration checks, domestic and foreign windows, and confidence threshold
No human action required
Stages 1 to 4 run unaided, and nothing is warranted at any of them — the agent is listing gaps, and counsel's lane opens at the confidence gate.
5DecisionBranches at the confidence threshold
High confidence
Goes to production counsel to review.
Low confidence
Adds a paralegal chain read first.
Counsel review
The list is held with its instruments, its open clocks and the confidence.
Approve · Amend · Send to outside counsel
Approved — released to the package▼
6Clearance systems updatedOnly where write access and approval policy allow it
7Outcome evaluatedAmendments, gaps raised late, windows missed and post-binding disclosures
Amendments
Every amendment counsel makes is counted, including one raised after a policy bound.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Opining that a chain supports exploitation.
Signing or warranting the E&O application.
Deciding whether a change is material to the insurer.
Certifying a copy as a true copy of the signed original.
Automation boundaryAgent acts unaided
✓Enumerate the instruments the title's structure requires for the named owner.
✓Match the corpus to each link and name what is absent.
✓Compute the §412, §205(d), §203 and §304 clocks per item into the review queue.
✓Flag a closing window, and hold the list for counsel.
Any write happens inside the boundaries agreed at implementation, never ahead of counsel.
Serving or signing a §203 termination notice.
Waiving a link as an acceptable commercial risk.
Accepting a clearance report as counsel-reviewed.
Changes to enumeration, clock or approval rules.
Example output
One chain link, annotated
Everything the agent reports is attached to the instrument it was measured against.
Gap-analysis output · single linkIllustrative example
Title
Required instrument
Status
Source of record
Confidence
Clock
Feature, US chain
Assignment from the second credited writer
Not signed
Deal memo on file
88%
§205(d) window still open
As receivedTaken from the production files and the contract repository — nothing on this side is written by the agent.
Evidence checkedDeal memo, unsignedWriter credit listRegistration record
Why this is a defectPayment does not cure a missing §204(a) writing — the link counsel weighs.
ActionApproveAmendSend to outside counsel
What the score decidesBelow the configured threshold the list picks up a paralegal chain read before it reaches counsel.
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
Every titleFrom the title's structure
03Gap analysis
List what must exist
No regulator, court or insurer publishes a chain-of-title defect rate, so the work runs from your structure and the statute rather than from a benchmark.
01Approved path
The missing paper is the risk
Retrieval returns what exists; a chain fails on what does not, so the list is built from the structure first and matched to the corpus after.
02Human review
Put counsel's read on the absences
Before a policy binds, a missed gap is a chase for a signature. After it binds it sits inside a warranted application the carrier issued in reliance on.
04Build an evidence trail
The gap, the instrument it was measured against and the counsel who opined stay on the chain.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
A slate-level gap-detection figure can read as healthy while a small number of rights cohorts carry most of the missed instruments. Nestack reports the missed-gap rate by slice, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Archival and stock footage
7.1%
3.5×
Review
Music cues and needle-drops
5.6%
2.8×
Review
Life rights and depiction
3.3%
1.6×
Watch
Single-author originals
1.8%
0.9×
Normal
Bar: missed-gap-rate lift vs. single-author baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
A named cause does not close a cycle
A cycle closes when the unnoticed gap is a regression case the next release must pass. That suite is what the next chain reviewed is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Missed-gap rate rises in a rights slice.
02Diagnose
The assignment nobody could find because it was never signed is traced back to the deal memo the enumeration accepted as a link.
03Improve
The fix gets a number, and the chains that raised it are held against it.
04Verify
The release is held until each touched gap case clears a second run.
05Learn
The case stays for good, and the clocks it touches are recorded with it.
Learn → DetectThe return edge. The next detection runs against a suite one missed-gap 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, gap-analysis workflow, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Clearance workflow discovery and boundary work.
02Repository and records source review.
03Instrument, clock and termination-rule mapping.
04Title-structure ingestion and enumeration.
05Gap matching and instrument binding.
06Confidence scoring and defect routing.
07Counsel review workflow.
08Repository and calendar integration.
09Gap and deadline cases.
10Guardrails and opinion controls.
11Chain-trail instrumentation.
12Deployment, documentation and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal 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 tierPilotOne title, one slateProductionProduction repositoriesAdvancedMultiple slates / entities
Introduced at Pilot
Gap analysis to your structure✓✓✓
Counsel review✓✓✓
Gap-detection baseline✓✓✓
Introduced at Production
Reporting by title—✓✓
Approval workflow in your systems—✓✓
Approved write-back—✓✓
Contract-repository integration—✓✓
Introduced at Advanced
Multi-jurisdiction chain rules——✓
Multi-stage counsel approvals——✓
High title volume——✓
Multi-title chain controls——✓
Build priceFrom $5,000From $8,000Custom 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 title structure and delivery schedule→Title-structure ingestion and enumerationWeek 1
02Titles you have already cleared and warranted→Gap baseline, instrument binding and clock computationWeek 2
03Your chain-of-title standard and counsel's rules→Instrument, clock and termination-rule mappingWeek 1
04Access to relevant APIs, feeds or exports→Repository and records assessment, then integration setupWeek 2
05Chains you would not want warranted→Defect cases and failure-mode testingWeek 4
06What no warranty may cover→Confidence scoring, defect routing, guardrails and opinion controlsWeek 3
07Named counsel to review the defect list→Counsel review workflow, then pilot and production validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
The weeks are taken from the filing clocks, so the fifth band carries evaluation and the pilot together.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Clearance workflow discovery, clock mapping and the automation boundaryW2Repository integration and the gap baselineW3Gap-analysis workflow, confidence logic and review controlsW4Evaluation suite, §204(a) checks and failure-mode testingW5Calendar integration, pilot titles and targeted correctionsW6One slate cleared under the head of business affairs, then Agent Care handover
Reading the bandEach bar covers only the weeks its work is named in. The week 5 overlap is real work, not padding.
At the end of W6The last checks clear on live titles 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 clearance agent around the warranty a producer signs.
Show us one title's structure, your repository and your filing calendar. Your own production counsel will tell you in the first session which links have no paper behind them, and that list is what we build against.
