Reservoir has expanded its lawsuits against Suno and Anthropic and now seeks more than $445 million in statutory relief. That figure describes a request in litigation. It does not tell a distributor what to do with the next track its screening system flags as artificial intelligence (AI).
The claim and the flag answer different questions
A copyright claim asks whether a party is entitled to relief. An upload flag asks whether a distributor should take a closer look at a particular track before deciding what action its store rules permit. Treating the two as interchangeable would turn a disputed legal demand into an operating rule for an unrelated catalogue.
The scale of Reservoir’s requested relief gives a distributor a reason to take copyright exposure seriously. It does not supply a per-track loss estimate, an infringement finding or a score at which every upload must be removed. The useful number for an upload policy is instead the two thresholds in the AI flagging playbook: they divide incoming flags into ranges that can receive different actions.
That distinction also matters to independent labels using a distributor. A flag is information about a recording in a review system. It is not itself a ruling on the label’s rights. If a distributor acts on the flag, the label needs to know which track was affected, what decision followed and what information could change that decision.
Put a decision behind each threshold
The policy playbook calls for two thresholds, a store-compliant action for each score band, a defensible record and an advisory role for the detector. Those elements form a sequence. A score places the track in a review range. A person or defined process then decides the action available under the relevant store policy. The record explains the decision afterward.
A distributor can express that sequence in a short policy:
- Below the first threshold: record the screening result and apply the ordinary upload process.
- Between the thresholds: send the track for review and record the information used to decide its next step.
- Above the second threshold: assign a prompt review and choose an action that complies with the store’s rules.
Those bands are a way to organize work, not a claim that any particular score proves infringement. Keeping the detector advisory leaves room to assess the track and the applicable policy before taking action. It also makes the decision intelligible to a label that may have to provide information about its catalogue.
The record should connect the flag to the resulting action. Without that connection, a distributor cannot readily explain why one upload proceeded while another faced review. For a label, the same record identifies which decision it needs to address. That is more useful than receiving a score without an account of what the score changed.
Assign the operating cost before it reaches revenue
Review requires work even when a flag produces no dispute. Screening, review and store action each carry costs that labels and distributors need to assign before a dispute reaches the royalty ledger. A contract or operating procedure should therefore identify who handles a flagged upload, who supplies catalogue information and who communicates the resulting store action.
That allocation becomes relevant after delivery as well as at upload. The stated costs of AI-generated music in a catalogue include royalty dilution, platform removals, demonetisation and lost listener trust. Those outcomes do not all appear in the same place: a review task consumes staff time, while a removal or demonetisation changes what a recording can earn. Putting every consequence into a single royalty adjustment would hide the event that caused it.
Rising upload volumes and a copyright lawsuit have put distributor catalogues under scrutiny. At higher volume, a rule that depends on an unexplained judgment for every flag becomes harder to apply consistently. Thresholds give reviewers a common starting point; the documented decision shows what happened to the individual track. Neither step requires a distributor to treat a litigation demand as an upload verdict.
What a label should ask its distributor
An independent label can make this practical before its next delivery. Ask for the distributor’s two review thresholds, the action assigned to each band and the point at which a reviewer can change the detector’s suggested path. Ask who records the decision and how the label will learn that a store action has affected a track. These questions follow directly from the threshold, action and record structure of the AI flagging policy.
Then settle who pays for the work and how any later store action appears in the label’s accounts. Screening and review costs arise before the royalty ledger reflects a dispute. The usable decision is to put that responsibility in writing now. Reservoir’s more than $445 million request belongs to a copyright case; the label’s next upload depends on a review rule it can understand and a decision it can trace.
