Patch history
Creative changes are stored as patch operations rather than only as opaque project folders.
Current implementation
ArtRiver currently exists as a Rust command line tool for local-first audio project history, but a working GUI is well underway.
Prototype status
At present, ArtRiver focuses on local repository mechanics, content-addressed assets, signed patch history, DAW project state tracking, runoffs, checkout, and basic audio/project diffing.
arp session initializes a local .arp project session.arp revise stages audio and project files into the Index.arp flow records staged changes into the TimeShore as signed patches.arp log shows local patch history.arp runoff creates a branch for an alternate creative direction.arp checkout restores the workspace from a runoff or patch.arp diff compares files, patches, or historical states.arp time estimates active project time from patch history.
Every ArtRiver project has a local .arp directory. This stores
repository metadata, branch refs, the staging index, signed patches, and
content-addressed assets.
.arp/
├── HEAD
├── config
├── identity
├── index
├── assets/
├── patches/
└── refs/
└── heads/
Creative changes are stored as patch operations rather than only as opaque project folders.
Audio and project files are stored by content hash to reduce duplication and support verifiable history.
Valid .dawproject files can be tracked as semantic project
state.
WAV files can be compared using technical and acoustic analysis.
ArtRiver is not a finished DAW plugin, cloud sync platform, or polished end-user application yet.
The prototype proves that ArtRiver can treat an audio project as more than a pile of files. It can model the creative process as history: assets, state, branches, authorship, restoration, and comparison.
Next step
The demo page walks through a mock audio project using the current CLI surface.