Local-first · browser-based · creator-controlled

ToneveraShape the sound.
Prove the session.

Build a clear, creator-maintained record of your track brief, disclosed tools, assets, collaborator consent, and release context—without uploading audio.

The complete session record

Track Brief

Capture direction, tempo, key, mood, purpose, and the creative note behind the work.

AI Use Disclosure

Declare none, assistive, or generative use yourself—Tonevera never guesses.

Asset Ledger

Record samples, providers, source links, license notes, and context.

Consent Register

Track pending, confirmed, or declined collaborator status without pretending it is a signature.

Release Note

Assemble a consistent disclosure note from the information you entered.

Session Receipt

Create a real SHA-256 digest over a time-stamped session summary in your browser.

Clarity before release day

Music sessions can involve people, source material, and creative software. Tonevera keeps the record understandable while the details are still fresh.

Keep the brief beside the disclosure
Make license notes easy to find
Separate consent from signatures
See unresolved statuses early
Create reproducible receipt data
Keep audio entirely out of the tool

A session trail that stays legible

Each stage adds creator-provided context. Nothing is inferred from audio, because no audio is accepted.

01ShapeSet the track brief and intended use.
02DiscloseDescribe tools and source materials.
03ConfirmRecord collaborator status and dates.
04ProveHash a time-stamped session summary.
Track brief
Disclosure record
Asset & consent ledgers
SHA-256 receipt

Built around honest states

Draft state

  • Empty and editing are visible
  • Save feedback is explicit
  • Storage failure stays visible

Consent state

  • Pending stays unresolved
  • Confirmed includes an optional date
  • Declined is never hidden

Wallet state

  • Missing and rejection are clear
  • Wrong network is not treated as success
  • Address and chain only

Proof state

  • Unavailable is explicit
  • Pending requires a real hash
  • Confirmation requires block evidence

Local by design

Your working record stays in browser storage. A receipt digest is computed through Web Crypto. Tonevera does not upload audio, scan copyright databases, or decide ownership.

You decide what to disclose and when to export. The tool documents your input; it does not replace agreements, licenses, or professional advice.

Receipt anatomy at a glance

A structured JSON payload and its real SHA-256 digest give the session a portable checkpoint.

Session summary

Brief, disclosure, assets, and collaborator status.

Created time

A precise ISO timestamp and tool version.

Digest

A 64-character SHA-256 value over stable JSON.

Generate a receipt

One deliberate flow

Brief

Describe the creative target.

Disclose

Choose the level and uses.

Resolve

Review assets and consent.

Receipt

Hash, copy, or download.

BriefDisclosureConsentReceipt

Proof should never outrun the truth

Wallet connection is read-only
Receipt creation is a separate local action
Proof anchoring has a business-specific preview
Pending requires a real transaction hash
Confirmation requires block evidence
Unconfigured actions stay unavailable

Connection is not consent to transact. Any future on-chain proof remains a separate, labeled action with review.

Frequently asked questions

Ready to shape the record?

Start with a brief, disclose the session, and create a receipt you can inspect yourself.

Open Tonevera workspace