A session log beats reconstructing an AI tool history from memory

The audio task

A session that runs through several AI-assisted stages, a generated drum pattern here, an AI vocal cleanup there, a stem separation for a bridge, produces a finished track whose production history is easy to lose track of. Months later, a distributor's upload form or a rights question forces a producer to reconstruct which tool touched which part, from memory, without notes. A simple running log kept during the session, naming each tool, its version, what it did, and the licence in force at the time, avoids that reconstruction.

What the documents show

DistroKid's own help-centre article states that DistroKid accepts music made with AI tools but requires the uploader to 'own 100% of the rights, including the legal right to distribute music created with any AI tools, samples, lyrics, etc,' and separately bars impersonation of another voice or likeness and mass-generated spam. The U.S. Copyright Office's March 2023 statement of policy requires applicants to disclose AI-generated content in a copyright registration application and describe the human author's contribution, and warns that omitting that disclosure can put a registration at risk. Neither document specifies a log format; both depend on the applicant or uploader already knowing, accurately, what was AI-assisted and what was not.

Rights status

DistroKid's rule is a rights-ownership condition on distribution, stated in the platform's own text reviewed here, not a disclosure requirement. The Copyright Office's guidance is a registration disclosure duty tied to U.S. copyright law, addressing what can be claimed as authored, not what a streaming platform will accept. Neither source states that a specific log format is legally required; a session log is an editorial convenience for answering both kinds of question later, not a compliance document either source mandates.

What to check before you use it

This is an editorial method record, not a claim about what any specific distributor currently requires. A workable log needs, at minimum, the tool name and version, the date and session it was used in, what it was applied to, and the licence or terms in force that day, since a vendor's terms can change between sessions. Save the log with the project files, not only in memory.

• Which parts of this specific track involved an AI-assisted tool, and which did not?
• What licence or terms of service governed that tool at the time it was used, not today?
• If a distributor or the Copyright Office asked next month, could this log answer the question without reopening the session?

Neither DistroKid's upload rule nor the Copyright Office's disclosure duty tells a producer how to keep records; both reward having kept them.