A collaborator's AI tool choices become part of your rights picture

The audio task

A producer who receives stems, a MIDI file, or a rough mix from a collaborator is inheriting more than audio; they are inheriting whatever tools the collaborator used upstream. A generated drum pattern, an AI-cleaned vocal take, or a stem pulled from someone else's recording all carry a rights posture the receiving producer did not create and may not know about. Asking about it before building further is cheaper than discovering it after release.

What the documents show

The U.S. Copyright Office's statement of policy requires an applicant seeking to register a work containing AI-generated material to disclose that material and describe the human authorship contributed, and states that a work combining human and AI-generated content can still be registered for its human-authored portion. That duty falls on whoever files the registration, which may be the receiving producer, not the collaborator who used the tool. Fairly Trained's certified-models page lists companies given its 'Licensed Model' certification, including the music tool Lemonaide, and states it certifies 'the companies and models that we've certified so far,' recommending them 'when considering generative AI providers.' Neither document tells a producer what any specific collaborator actually used; both give a producer language and criteria for asking.

Rights status

The Copyright Office's guidance establishes a disclosure duty tied to registration, not a warranty that a collaborator's material is clear to use. A Fairly Trained certification indicates that organisation's own review found a company's training data licensed, according to its own published criteria; it is not a court finding or a guarantee, and a tool's absence from that list does not mean the tool is improperly trained, only that no certification was found here.

What to check before you use it

This is an editorial checklist. Ask a collaborator which specific tools touched the material, whether generation, drum programming, vocal cleanup, or separation; ask what licence or terms governed the tool at the time; and ask whether the collaborator can point to documentation, such as the tool's own terms page or a certification, rather than a general assurance that everything is clean.

• Which AI-assisted step, if any, produced this stem or MIDI file before it reached me?
• Does the collaborator have the tool's terms of service, or a certification like Fairly Trained's, to point to?
• If this track is registered for copyright, who is responsible for disclosing the AI-generated portion?

A finished-sounding stem does not disclose its own production history; only the person who made it, or their notes, can.