Read the coverage the company does not own: log the licence each extract sits under, hold the clipping under the publisher that wrote it, and leave the rumour call to a named officer.
A title is crawled, and the reservation it published that morning is read before a word is kept.
02
A publisher switches its opt-out on, and that title leaves the corpus until a licence covers it.
Reason
03
An extract is cut, and the rule of the market it will be read in governs how long the cut runs.
04
A broadcast is indexed and made searchable, and the store is configured not to serve the segment.
05
A clipping is filed, and the two-year term under DSM Article 15(4) is filed beside it.
Decide
06
Coverage of a protracted process surfaces, and it goes to the officer named on the delay record.
07
Nothing is found in a market, and that is logged as an absence of publishers, not of a story.
Out
08
A digest names an outlet, and the outlet is checked against the item rather than inferred.
09
Redistribute an extract only inside the licence boundaries agreed during implementation.
→Product statement
Retrieval, extract control and the record belong to the agent. The rumour call belongs to a named officer, who signs it, files it and carries it afterwards.
Example workflow
One clipping, crawl to certification
AgentHuman
1Coverage retrievedWires, named dailies and channels, licensed feeds or the publisher page itself
2Licence position establishedThe publisher, the reservation state on the day of the crawl, the licence in force and the term left
3Extract cut to jurisdictionThe quoted extract, the market it will be read in and the rule that length was cut to
4Controls appliedReservation checks, extract-length checks, outlet-attribution checks and retrieval confidence
No human action required
Stages 1 to 4 run unaided, and nothing circulates at any of them — the agent is assembling, and the officer lane opens at the rumour gate.
5DecisionSplits at the rumour gate
Routine coverage
Goes into the numbered digest.
Anything touching a delayed matter
Reaches the disclosure officer first.
Officer review
The item is held with its publisher, its licence position and the extract taken from it.
Confirm · Deny · Hold for counsel
Certified — by the named officer▼
6Insider list and delay record updatedOnly where write access and the records policy allow it
7Outcome evaluatedLicence accuracy, outlet accuracy, officer corrections and what the review found
Corrections
Each officer correction is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Certifying that a rumour is accurate.
Deciding a delayed matter has leaked.
Agreeing what a publisher licence permits.
Signing the record filed with a regulator.
Automation boundaryAgent acts unaided
✓Index the broadcast itself and never serve the segment.
✓Cut the extract to the redistribution rule of the receiving market.
✓Store the publisher, the crawl date and the licence term left to run.
✓Hold coverage of a delayed matter for the officer.
Nothing is redistributed except by a named officer, inside the agreed licence scope.
Judging whether an extract is short enough.
Telling a board the corpus was complete.
Choosing which titles a digest may reproduce.
Changes to licence scope or extract rules.
Example output
One clipping, annotated
This serves a comms team who may have to show, years later, what they copied and under whose licence — the ground the Autorité de la concurrence covered in decision 24-D-03 of 15 March 2024, not appealed and final.
Clipping record · single itemIllustrative example
Publisher
Item
Extract
Licence of record
Confidence
Held for
National daily, business desk
Board-level story, print and online
Extract within licence
Publisher licence, 3 August 2026
Held uncertified
The named officer, by name
As receivedTaken from a licensed feed and the publisher page it names, and it asserts nothing beyond those two.
What this record holdsLicence in forceReservation stateExtract length
Why no certification hereCalling a rumour accurate is a judgement a named officer makes.
ActionConfirmDenyHold for counsel
What the score decidesBelow the configured confidence the clipping gets a senior read before the officer sees it.
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
Any clipping keptFrom the publisher that wrote it
03Licence
Where the extract may travel
The agent does not weigh what coverage was worth or who was speaking; it records which publisher owns the words, when they were taken and the licence that stood that day.
01Approved path
Somebody else wrote it
Since 5 June 2026 the MAR Article 17(7) rumour trigger reaches undisclosed intermediate steps. UK MAR did not follow: one clipping, two tests.
02Human review
What was checked, and not found
Federal full-text search returns nothing for broadcast monitoring, for clipping service or for news clipping; media monitoring appears once, inside a tobacco rule, and press clipping once, inside a labour list. No FCC rule governs recording a broadcast, so the Copyright Act does.
04Build an evidence trail
The extract, the publication it was taken from and the reader who cleared it stay together.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Licensed news feedsWire services · licensed aggregators Full text under contract
Publisher websitesRobots files · rights metadata Reservation state per crawl
Broadcast and transcriptsRadio · television transcripts Indexed only, never served as clips
Agent
Media monitoring and extract control
Reads the coverage Cuts the extract Holds for the officer
Comms and disclosure recordsInsider lists · delay records Named signatories and the timestamps
A corpus-level licence figure can read clean while the titles carrying a live reservation take most of the corrections. Nestack reports the correction rate by publisher class, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Titles with live reservations
13.8%
3.7×
Review
Broadcast and transcript sources
9.8%
2.6×
Review
Cross-border digest recipients
6.1%
1.6×
Watch
Licensed wire feeds
2.8%
0.8×
Normal
Bar: correction-rate lift vs. licensed-feed baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
What a flipped reservation costs
A cycle ends when the clipping nobody may redistribute is a standing case. That suite is what the next digest circulated is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Correction rate rises on titles carrying a live reservation.
02Diagnose
The extract that was lawful last quarter and is not lawful now is worked backwards until one cause is left standing.
03Improve
The digest goes out numbered, and the extracts that fill it ride with it.
04Verify
One licence case still failing is enough to hold the digest back.
05Learn
It is kept for good, and the extract rules are amended in the same commit.
Learn → DetectThe return edge. The next digest is measured against a suite one 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, extract control, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Licence mapping and automation-boundary definition.
02Publisher, wire and broadcast sources.
03Publisher-attribution and extract-length rule mapping.
04Coverage ingestion.
05Publisher, licence and term binding.
06Extract cutting and rumour routing.
07Officer certification workflow.
08Comms-record integration.
09Licence and extract cases.
10Guardrails and redistribution controls.
11Extract-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 publisher set, one cycleProductionProduction comms workflowAdvancedMultiple markets / languages
Introduced at Pilot
Clipping assembly to your licences✓✓✓
Named officer certification✓✓✓
Coverage-corpus baseline✓✓✓
Introduced at Production
Reporting by publisher class—✓✓
Officer review workflow in your systems—✓✓
Approved record write-back—✓✓
Feed-and-archive integration—✓✓
Introduced at Advanced
Multi-licence reconciliation——✓
Cross-market digest packs——✓
Large clipping archives——✓
Multi-publisher extract controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, publisher coverage, licence 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 live titles and the licence each is read under→Licence capture and reservation trackingWeek 1
02Representative wire, print and broadcast sources→Source binding, extract rules and the coverage baselineWeek 2
03Your disclosure calendar and the officers it names→Licence mapping, extract rules and the automation boundaryWeek 1
04Access to relevant feeds, archives or exports→Wire, print and broadcast source assessment, then integration setupWeek 2
05Extracts you would not want invoiced→Licence cases and the failure-mode roundWeek 4
06What no digest may reproduce→Rumour routing, officer holds, guardrails and release controlsWeek 3
07A named officer who certifies the rumour→Release to the named officer, 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
These bands are counted, never spaced for looks; the fifth week carries two because the two coincide.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Licence discovery, reservation tracking and the automation boundaryW2Feed integration and the coverage-corpus baselineW3Extract control, rumour routing and release controlsW4Evaluation suite, licence cases and failure-mode testingW5Comms-record integration, pilot digests and targeted correctionsW6One coverage cycle run under the comms owner, then Agent Care handover
Reading the bandEach band runs over the weeks its own work is named in, and the fifth week is shared on purpose.
At the end of W6When the extract record validates, Agent Care takes the agent on.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · PR AI agent
Build a media monitoring agent around the licence your last digest never recorded.
Show us one week of coverage and the licence the extracts in it were taken under. If a clipping has been archived, forwarded and quoted with no publisher named, it is being kept on trust. The broadcast exception people reach for is a library exception under 17 U.S.C. 108.
