A local-first record for music sessions

Problem

Music releases often collect important context in scattered messages, notes, and memory. Track intent, creative software use, source materials, and collaborator status can become difficult to reconstruct. Tonevera provides a single, local record for those facts while they are current.

The product does not replace contracts, licenses, professional review, or a rights registry. It creates an inspectable session summary that the creator controls.

Principles

• Creator-declared: the user supplies every disclosure and status.
• Local-first: working data is kept in browser storage.
• Honest state: unavailable, pending, confirmed, failed, and recovery remain distinct.
• Separated authority: wallet connection, receipt creation, and proof anchoring are distinct.
• Minimum claims: no ownership, clearance, legal, model, or database claims.

Local architecture

Tonevera is a browser application. Project data and receipt records are serialized into localStorage. Release notes are assembled with deterministic templates. Session digests are calculated with the browser Web Crypto API.

No audio upload, cloud synchronization, shared team account, or server-side project database is part of this version. Clearing browser storage or changing devices can remove access unless the user exports receipt JSON.

Track and disclosure model

A Track Brief contains title, genre, BPM, key, mood, intended use, and a creative note. BPM is optionally validated between 20 and 300.

AI Use Disclosure has three creator-selected levels: None, Assistive, and Generative. Optional purposes include inspiration, lyric suggestions, arrangement suggestions, sound synthesis, and mix feedback. Tonevera does not analyze a track or infer a level.

Asset ledger

Each asset record contains a name, source URL or provider, type, license or permission note, and optional context. Entries are user-maintained notes. They are not validated against a copyright, licensing, fingerprint, or provenance database.

Consent model

Each collaborator entry contains a name, role, pending/confirmed/declined status, an optional confirmation date, and notes. A date is required when the local status is confirmed.

The register does not capture, verify, or reproduce a signature. Users remain responsible for obtaining appropriate agreements through suitable channels.

Receipt schema

The tonevera-session-receipt/v1 payload contains tool version, ISO creation time, the Track Brief, disclosure data, selected asset fields, and collaborator statuses. Object keys are stably ordered before hashing.

Web Crypto calculates a SHA-256 digest, rendered as 64 lowercase hexadecimal characters. Recomputing the same stable payload yields the same digest. Any payload change yields a different result. A digest supports integrity checking only; it does not establish authorship, timing outside the local clock, permission, or ownership.

Wallet and proof separation

Connection requests the user-selected public address and active chain ID. It does not request a signature, transaction, token approval, payment, transfer, or proof submission.

The only contemplated chain operation is anchoring a Tonevera session digest. It has a separate transaction preview covering business ID, digest payload, wallet, chain, contract, value, and expected result. Without a verified contract configuration the action is unavailable.

Proof lifecycle

1. A user completes or reviews session data.
2. The browser produces a real SHA-256 receipt and business ID.
3. The user opens the separate proof transaction preview.
4. Unavailable remains visible when contract evidence is missing.
5. Pending may begin only after a wallet returns a real transaction hash.
6. Confirmed requires a real receipt, block time, and explorer link.
7. Failed exposes the provider or receipt error; recovery requires an explicit retry.

Threats and safeguards

Local records can be incomplete, intentionally misleading, or altered before a receipt is generated. A compromised browser extension may observe wallet details or interfere with user interactions. Device clocks can be inaccurate. LocalStorage may fail or be cleared.

Safeguards include explicit states, minimal wallet methods, deterministic receipts, no audio handling, no automatic disclosure inference, and downloadable JSON. Users should verify critical facts independently and secure exported records.

Limitations

• No audio generation, upload, playback, analysis, or fingerprinting.
• No copyright lookup, rights clearance, authorship decision, or ownership judgment.
• No legal advice, verified signatures, cloud backup, team access, marketplace, token claim, or generic transfer product.
• No guarantee that a collaborator, platform, court, or third party will accept a receipt.
• No verified proof contract or mainnet launch evidence in this release.

Roadmap

Potential future work includes user-controlled encrypted exports, receipt verification utilities, configurable proof adapters, and clearer portability tools. Roadmap items are exploratory, may change, and are not promises.

Disclaimers

Tonevera is an informational documentation tool. It does not provide legal advice, determine ownership, warrant non-infringement, certify consent, perform a security audit, or guarantee regulatory, platform, distributor, or marketplace acceptance. Consult qualified professionals for decisions that require legal, financial, licensing, or technical advice.