DISTROBOLT

DISTROBOLT ARTIST GUIDES

Build a release evidence package for an AI-assisted project

An AI-assisted release evidence package should connect the final master to its sources, human contributions, permissions and declarations. Share a focused review copy rather than an unrestricted folder of private production and identity data.

Build an index for the exact version

Record release and recording references, final audio filename, project version and owner of the review. List each supporting item and what it demonstrates. Keep drafts clearly labelled. A folder containing many unrelated files is harder to assess than a short index tied to one delivered master.

Include relevant source evidence

Collect applicable tool terms and entitlement dates, input permissions, human contribution notes, voice or image authorisations where relevant, and approved metadata. Do not imply a licence receipt settles every right. Record missing evidence explicitly and assign a follow-up owner rather than inserting a generic approved status.

Minimise private information

Use controlled access and share only what the verified reviewer needs. Keep passports, tax records, passwords, codes and bank details out of ordinary production packages. If identity verification is genuinely required, use the provider’s appropriate secure process separately. Do not expose a collaborator’s raw files without authority.

Preserve the review outcome

Save who reviewed the package, the question answered, any conditions and the exact declaration submitted. Recheck when the master or source material changes. Ask DistroBolt for its actual requirements before claiming an evidence package is accepted. This guide does not activate uploads to WBBT or guarantee that documentation resolves a legal or platform dispute.

Sources and review

Reviewed 4 November 2026. Platform requirements and plan terms can change. Examples are planning aids, not a promise of account access, release acceptance or earnings.

Continue your release planning

Ask the DistroBolt team about your release. Send a concise question and release reference; never send account passwords or verification codes.