# Chronatum — the production record behind every track

> A finished track cannot show how it was made. Chronatum records the production data inside your DAW session, structures it, and seals that creation history to the exact audio.

Creation history, structured.

**The production record behind every track.**

Chronatum separates direct observations, rule-based inferences, creator declarations, conflicts, and anything it could not verify. That evidence account is bound to the exact audio export.

Supported today: Logic Pro · Ableton Live · FL Studio · macOS. For everyone who makes music.

- [Download for Mac](/download)
- [Verify a proof](/validate)
- [Developers](/developers)

## Create the record. Or verify it.

Supported credentialed WAVs carry the proof inside; older exports keep the portable .poh sidecar. Read a clear summary first, then open the process and technical receipt when you need them.

- **Make a proof.** Create as usual. Chronatum records the supported parts of the session and writes a transparent evidence account when you export. [Download for Mac](/download)
- **Verify a proof.** Drop one credentialed WAV, or pair older audio with its .poh. Inspect what was observed, inferred, declared, conflicted, and left unverifiable. [Open the verifier](/validate)

Building for a platform or distributor? See [Where Chronatum lives](/verify) or the [verification API](/developers).

## Example result

The bundled registered sample shows the result before you have a proof of your own:

- **Verified by Chronatum** — the .poh is genuine and issued by Chronatum.
- **Exact audio match** — the proof is bound to the sample track.
- **Structured evidence account** — direct observations, rule inferences, creator declarations, and unverifiable gaps are kept distinct.
- **Report-only** — the report is not an authorship verdict or an AI-free claim.

[Try the live sample](/validate)

## The problem

Nobody can tell how music was made anymore.

**44%** of new tracks uploaded to Deezer each day are now fully AI-generated — about 75,000 a day. Yet those tracks represent only 1–3% of streams there. Upload volume and listener demand are different stories. ([Deezer, April 2026](https://newsroom-deezer.com/2026/04/ai-generated-tracks-represent-44-of-new-uploaded-music/))

- Real work looks identical to a bulk upload
- Credits are declared, not shown
- Trust drains for everyone — AI-assisted artists included

### And it isn't one platform.

The same flood is turning up everywhere music is uploaded — from the biggest names in streaming to the firehose underneath them.

- **Apple Music** — **1 in 3** tracks delivered to Apple Music is now fully AI, its SVP says — but under 0.5% of what people actually play. ([Apple Music, 2026](https://www.billboard.com/pro/apple-music-exec-talks-ai-billboard-on-the-record/))
- **Spotify** — **75M+** spammy tracks Spotify pulled in a single year, a purge it tied to the surge in generative-AI tools. ([Spotify, 2025](https://newsroom.spotify.com/2025-09-25/spotify-strengthens-ai-protections/))
- **Every platform** — **~106K** new tracks are uploaded to streaming every single day — the firehose AI is pouring into. ([Luminate, 2025](https://luminatedata.com/reports/yearend-music-industry-report-2025/))
- **Suno** — **~7M** AI songs are generated a day, per Suno’s own investor deck — Spotify’s whole catalog, remade every two weeks. ([Suno deck, via Billboard, 2025](https://www.billboard.com/pro/suno-creates-spotify-catalog-music-two-weeks-pitch-deck/))
- **Listeners** — **97%** couldn’t tell AI from human in a blind test of 9,000 people — across 8 countries, including the US and Canada. ([Deezer / Ipsos survey, 2025](https://newsroom-deezer.com/2025/11/deezer-ipsos-survey-ai-music/))
- **The Velvet Sundown** — **1M+** Spotify monthly listeners for one AI “band” — before it was confirmed to be AI-generated. ([The Guardian, 2025](https://www.theguardian.com/technology/2025/jul/14/an-ai-generated-band-got-1m-plays-on-spotify-now-music-insiders-say-listeners-should-be-warned))

## The creation record

**Evidence sources and unknowns — clearly separated.**

Chronatum reports what happened in the session, not what a finished waveform merely seems to be. The result is creation context, not a simplistic human-or-AI score.

- **Observed: supported DAW activity.** Takes, edits, arrangement, time, and import-related signals when the capture surface exposes them. This is the **Human Contribution** module of the record — one section of it, never a verdict that a human made the finished track.
- **Declared: creator context.** External material and AI-tool answers remain labeled as declarations rather than system observations.
- **Inferred or unverifiable.** Rules never become direct observations, and missing coverage never becomes a favorable conclusion.
- **Portable credential: one transparent creation record.** Bound to the exact export and readable from one credentialed WAV, with .poh sidecars retained for older files.

Not witnessed stays unknown — missing evidence never becomes an AI accusation.

## How it works · Privacy

**Transparency about the work. Silence about the music.**

While you produce, Chronatum observes supported process signals inside the DAW you turn it on for — Logic Pro, Ableton Live, or FL Studio. It is scoped to that app; it sees nothing of your screen, your other apps, or your keystrokes. Capture coverage differs by DAW, and the report keeps unsupported or unseen activity unverifiable.

1. **Observe inside your DAW.** Supported activity becomes content-free events, read from the one DAW you enable and nothing else.
2. **Reduce on-device.** Creative content such as pitches, notes, names, and paths is removed before upload; supported import evidence uses only session-local identifiers and aggregate coverage.
3. **Bind at sealing.** Sealing submits the finished track on the notarized path so Chronatum can hash, sign, and bind the evidence account to those exact audio bytes.

What stays inside your session: project file, notes, pitches, lyrics, full paths, and source names. What leaves on the notarized path: the approved content-free capture record, consent metadata, display names, and the finished export used for binding. The local-only path uploads no proof data.

## What we can and can't prove

**We lead with the limits.**

> Chronatum attests its signature, the exact audio binding, and the scoped evidence account it received. It does not independently certify authorship or that the music is AI-free.

What Chronatum attests:

- Chronatum's cryptographic signature and registry record
- The proof's binding to this exact audio file
- A report-only evidence account whose items retain their basis and capture limitations

What Chronatum does not claim:

- That the music is “AI-free” or “100% human”
- A verdict on the tool — AI now lives in the DAW
- That absence of evidence means AI — it means UNKNOWN

## For platforms

**The process, transparent at ingest. The threshold, yours.**

An upload arrives carrying its compact process record inside a supported credentialed WAV or beside older audio as a .poh file. Chronatum is deliberately agnostic: we provide the transparency; you set your own AI threshold, human threshold, or none at all.

**Validation API · Live.** Verify one credentialed audio file — or older audio paired with its .poh — through Aura's API and feed the report-only process record into the screening you already run. Unverified is never a negative signal and never an AI verdict; the policy is entirely yours. Self-service API keys and a TypeScript SDK on npm — start at [/developers](/developers).

1. **Arrives with the track.** Supported WAV exports can carry the C2PA credential inside the audio; older exports keep the .poh sidecar. Both are bound to the exact file.
2. **A compact process payload.** Confirm the signed record binds to the file's fingerprint. The embedded or sidecar payload holds derived scalars, not a second copy of the audio. Alter the audio or record and it won't hold.
3. **A record + a report-only read.** You get a verifiable record of observed session activity, plus a structured evidence report to weigh however your policy says.

- **Recorded evidence, not a probability score.** A Chronatum credential is a contemporaneous record of observed DAW activity bound to the exact file, not a guess inferred from the finished audio. Chronatum is not a detector and renders no AI verdict.
- **Data that informs. A decision that stays yours.** The report separates observations, rule inferences, creator declarations, conflicts, and unverifiable gaps. It never auto-acts and never gates a proof.

Who Chronatum is for:

- **Distributors** — Read the process record at ingest and route by your own policy.
- **Labels** — A transparent read of the process across your whole catalog, automatically.
- **Rights orgs** — Add auditable process evidence to review queues without treating it as an authorship verdict.
- **Artists** — Carry a signed, scoped record of the process Chronatum observed into pitches, splits, and disputes.

**Design partners.** We're working with early distributors, music libraries, and rights teams. [Request design-partner access](mailto:frank@auramusictechnologies.io?subject=Chronatum%20%E2%80%94%20design-partner%20access)

## Built for provenance

**A music creation record, inside Content Credentials.**

Content Credentials can show where media came from, how it changed, and whether AI was used. Chronatum adds music-specific session context with evidence basis and honest unknowns. Complementary, never a compliance certificate.

Fits alongside: C2PA · Content Credentials · DDEX · EU AI Act · SynthID.

- **System observation** — Supported activity directly exposed by the DAW capture surface.
- **Rule inference / creator declaration** — Shown with its actual basis, never promoted to direct observation.
- **Unverifiable** — Kept unknown, including source-to-final coverage Chronatum did not capture.

**EU AI Act · Article 50.** Machine-readable AI marking applies from Aug 2, 2026. Chronatum can add creation context beside machine-readable AI markings. It does not by itself establish compliance.

## Make the process transparent

Show the evidence and its limits, disclose creator context, and carry unknowns honestly — in a record bound to your track.

[Download the macOS app](/download) · [Verify a proof](/validate)

macOS only · Logic Pro, Ableton Live & FL Studio.

---

More: [llms.txt](https://chronatum.com/llms.txt) · [sitemap](https://chronatum.com/sitemap.md)