Evergreen catalog due diligence now needs an AI-era origin layer.

Separate the age of a recording from the date of a declaration

A declaration submitted today about a historical recording is a present-day statement about that recording. It is not a backdated certificate. OpenTimestamps provides evidence that a digest existed before a point in time; it does not establish who composed the music or whether a declarant owns the rights.

Preserve the historical evidence separately: session records, contributor credits, contracts and the history of transfers. ACC's file hash ties the declaration to one set of bytes. An MP3 conversion or a metadata edit can change that hash, even when listeners hear the same recording.

Large catalogs cannot be checked manually track by track

A 200,000-track catalog cannot rely on bespoke review for every recording. Buyers, licensors and catalog teams need sampling, batch processes and machine-readable evidence.

Even when legal ownership is documented, operational teams may still need to know which works carry origin declarations, which are uncertified and which require further review.

Origin evidence changes the diligence conversation

A certificate does not replace legal review. But it can provide a repeatable provenance layer: work hash, declaration hash, certificate status, category, identity assurance level and ledger evidence.

That turns a vague question into a workflow: query catalog, identify certified assets, identify gaps, select risk-based review sets and document what was known at the time of diligence.

Batch certification is the practical unlock

For evergreen assets, the business value is not one certificate. It is the ability to process a catalog quickly, expose status through an API and anchor batches into a ledger lifecycle.

ACC's architecture is built around that direction: hash-first processing, public verification, ACC API, ledger events and OpenTimestamps-ready anchor batches.

Start with an auditable batch, not a blanket assertion

1. Inventory file versions, identifiers and the evidence supporting each human-origin declaration.
2. Confirm who is authorised to make statements for the catalog. Separate unknown history from documented history.
3. Use a small representative batch to test mapping, duplicate handling, failed rows and public verification.
4. Agree throughput and retry limits before increasing batch size. Record unresolved items instead of silently certifying the entire catalog.

Measure evidence coverage and exceptions per batch. A 200,000-track catalog is a scale requirement to validate, not an established speed benchmark.

Sources and scope

• OpenTimestamps: what a timestamp proves

External sources describe their own standards or observations. The proposed workflows are ACC's analysis, not an endorsement or partnership with the organisations cited.

Test this with your workflow

Bring one intake or catalog problem. Agree the evidence boundary and success measures before expanding the integration.

Related reading

• Catalog flooding is not a philosophy problem. It is an operating cost.
• The AI disclosure gap starts before a track reaches the market.