GitTunes
Version control for music producers. Protocol-first: content-addressed storage, ed25519 identity, a Rust core, and royalty transparency by design.
This case study is a preview: outcomes and links publish once the work ships.
Stack
Version control for music producers, built protocol-first. The Tunes
Protocol (wire format, object schemas, signing scheme) has a Rust reference
implementation: deterministic CBOR, BLAKE3 content addressing, Ed25519
did:key identity, and a recursive split-routing engine for derivative works,
so royalty transparency is a property of the data model rather than a feature
bolted on later. The core crate is no_std-compatible and compiles to WASM;
a local tunes CLI runs with no server, backed by cross-language conformance
vectors and fuzz targets. The public product site and the collaboration layer
are in progress; the card goes live with them.