Skip to content

Creation provenance for music

Show the workbehind the music.

A finished track cannot show how it was made. Proof of Human records supported work in the DAW and binds it to the exact export.

For artists
Carry evidence of your process.
For platforms
Verify the record at ingest.

01 · DAW work

Activity witnessed

Content-free observations

  • takes
  • edits
  • saves
  • time on task
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

Embedded in the audio (C2PA)

poh-demo-session.wav

  • Exact audio match
  • Issued by PoH

Evidence report

Observed session evidence.

The report keeps observations, inferences, declarations, and unknowns visibly separate.

Direct system observations

Recording
Observed
Note entry
Observed
Final-audio coverage
Not established

Observed session only — not an authorship or final-audio contribution claim.

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 2026

The 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.

  1. 01

    Credits

    Who contributed?

    Names, roles, rights, and splits.

  2. 02

    Finished-audio analysis

    What does the output resemble?

    A probability inferred after the work is complete.

  3. 03

    Creation provenance

    What happened while it was made?

    A signed record collected during the supported creative process.

Proof of Human is the third layer. It records the process instead of guessing from the result.

How it works

How it works

It watches the work.Not your screen.

Enable one supported DAW. PoH 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.

daw · session log● rec

Only these numbers leave

edit-densitytake-counttime-on-taskrevision-depth
stays on your Mac ↑
Verified
  1. 01

    Observe one DAW

    PoH reads supported timing, take, edit, and save activity from the DAW you enable.

  2. 02

    Summarize on your Mac

    The activity becomes content-free counts and timing summaries.

  3. 03

    Seal the export

    PoH 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. Proof of Human adds supported DAW activity witnessed during creation, then binds that record to the export.

Audio layer

.WAV

Standard WAV

Plays in existing audio software

Credential layer

C2PA v2 manifest

Signer, assertions, and asset binding

Creation layer

Proof of Human record

Supported DAW activity and honest unknowns

One-file delivery. Credentialed WAV exports can carry a C2PA v2 manifest and the nested Proof of Human record. Existing audio and .poh pairs continue to verify.

Designed to fit the provenance stack

  • C2PA v2
  • Content Credentials
  • DDEX workflows
  • Legacy .poh

One record. Three honest states.

  1. Witnessed

    Observed process

    Supported activity recorded while you work in the DAW.

  2. Disclosed

    AI-assisted material

    Declared assistance and positively observed generation signals stay in context.

  3. Not witnessed

    Unknown origin

    Missing evidence stays unknown. It never becomes an accusation.

The boundary

PoH 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.

PoH 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.

  1. Step 01

    Accept

    track.wav

    credentialed audio

    Receive one credentialed WAV or a legacy audio and .poh pair.

  2. Step 02

    Verify

    API receipt

    Check the signer, registry record, and exact audio binding.

    Signer
    Checked
    Registry
    Checked
    Audio binding
    Exact
  3. 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.