01 · DAW work
Activity witnessedMidnight Cartography
48 kHz · 24-bit
Lead vocal
Keys
Bass
Percussion
Content-free observations
- takes
- edits
- saves
- time on task
Creation history, structured.
The production recordbehind every track.
A finished track cannot show how it was made. Chronatum records the production data in your DAW session, structures it, and binds that creation history to the exact export.
- For artists
- Carry evidence of your process.
- For platforms
- Verify the record at ingest.
Built for the tools musicians already useLogic ProAbleton LiveFL Studio
What someone receives
A result you can read in seconds.
Cryptographic facts come first. The witnessed process sits one layer deeper, and anything unseen stays unknown.
Bundled registered sample · AI-assisted
Verified by Chronatum
Embedded in the audio (C2PA)
Neon Tides.wav
- Exact audio match
- Issued by Chronatum
Evidence conflict
The two accounts do not agree.
The captured observations and the creator's AI-use declaration are shown together so a reviewer can judge both.
Published evidence
- Recording
- Observed
- MIDI notes
- Not observed
- AI-assisted material
- Declared · almost all
Observed session only — not an authorship or final-audio contribution claim.
Cryptographic result
- Status
- Verified
- Audio binding
- Exact file match
- Issued by
- Chronatum
Technical identifiers
- Issued
- 2026-08-02T05:39:46Z · UTC
- Proof ID
- b32fdaf2-6…c1f63c50aae
- Credential
- Embedded C2PA
Why this exists
Credits name contributors.They do not show the process.
AI changed music creation faster than the release pipeline changed. Finished audio cannot show how it was made, and a credit alone carries no evidence.
of Deezer's daily uploads are fully AI-generated, about 75,000 tracks in 2026.
Those tracks earn only 1–3% of streams. Upload volume and listener demand are different stories.
Deezer, April 2026The catalogue changed. Its context did not.
The scale is visible across delivery, spam, and listening. None of those numbers can explain how one specific track was made.
Three different questions need three different tools.
- 01
Credits
Who contributed?
Names, roles, rights, and splits.
- 02
Finished-audio analysis
What does the output resemble?
A probability inferred after the work is complete.
- 03
Creation provenance
What happened while it was made?
A signed record collected during the supported creative process.
Chronatum is the third layer. It records the process instead of guessing from the result.
How it works
It watches the work.Not your screen.
Enable one supported DAW. Chronatum turns content-free activity summaries into a small process record on your Mac, then submits the finished audio only when you choose to seal it.
Lyrics, note content, track and clip names, and full paths stay private.
daw · session log● rec
Capture records content-free summaries
edit-densitytake-counttime-on-taskrevision-depth
Seal a notarized proof and the finished export is uploaded and retained; choose a local-only proof and nothing is uploaded.
Verified
- 01
Observe one DAW
Chronatum reads supported timing, take, edit, and save activity from the DAW you enable.
- 02
Summarize on your Mac
The activity becomes content-free counts and timing summaries.
- 03
Seal the export
Chronatum binds the process record to the exact audio only when you ask it to.
Built for provenance
A music-specific record inside Content Credentials.
Content Credentials can describe where media came from and how it changed. Chronatum adds supported DAW activity witnessed during creation, then binds that record to the export.
Audio layer
.WAVStandard WAV
Plays in existing audio software
Credential layer
C2PA v2 manifest
Signer, assertions, and asset binding
Creation layer
Chronatum record
Supported DAW activity and honest unknowns
Designed to fit the provenance stack
- C2PA v2
- Content Credentials
- DDEX workflows
- Legacy .poh
One record. Three honest states.
Witnessed
Observed process
Supported activity recorded while you work in the DAW — the Human Contribution module of the record.
Disclosed
AI-assisted material
Declared assistance and positively observed generation signals stay in context.
Not witnessed
Unknown origin
Missing evidence stays unknown. It never becomes an accusation.
The boundary
“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.”
Chronatum signing works today. Public C2PA trust-list enrollment is the next infrastructure step.
It attests
- Supported DAW activity
- Declared assistance
- Exact audio binding
It does not claim
- An AI-free certificate
- A binary authorship verdict
- A guess about unseen work
For platforms
One record. Any policy.
Verify the credential at ingest, read the creation context, and decide how your product uses it.
Step 01
Accept
track.wav
credentialed audio
Receive one credentialed WAV or a legacy audio and .poh pair.
- API receipt
Step 02
Verify
Check the signer, registry record, and exact audio binding.
- Signer
- Checked
- Registry
- Checked
- Audio binding
- Exact
Step 03
Decide
policy inputs
- Witnessed
- Disclosed
- Unknown
Use the evidence under your own review or routing policy.
Design partners
Building the transparency layer with distributors, libraries, and rights teams.
Give the trackits history.
Start a creation record on Mac, or inspect one in your browser.
macOS only · Logic Pro, Ableton Live & FL Studio.