Build a provenance log that a future collaborator can read.

Record decisions, not every click

A useful provenance log explains the lineage of important material. It does not need a screen capture of the entire session. Focus on externally sourced inputs, generated or transformed elements, voice models, licenses, plan status and the human revisions that shape the release.

Give every asset an identity

Use stable filenames and hashes for final inputs and outputs. Record the source URL or agreement, acquisition date, creator, permission and project role. Keep the governing terms or download certificate with the asset where contracts allow.

Add a generation record

• Tool, model or feature and account plan.
• Date, prompt or operation, settings and seed if available.
• Input asset IDs.
• Output asset ID.
• Selection reason and rejected alternatives.
• Subsequent performance, arrangement and mix changes.

Connect the session to delivery

The release record should identify the exact master, metadata, disclosure supplied, distributor, territories and any platform response. Preserve the delivery copy rather than assuming the DAW bounce is identical to what shipped.

Keep uncertainty visible

If training provenance, copyright status or a contract term is unclear, write “unknown” with the date checked. Do not turn missing evidence into a reassuring inference. A later reviewer can then target the gap.