Release status

Audivane is preparing its first public release, version 0.1.0. This page states what is ready, what is in progress, and what simply does not exist yet. No download links are published here until the matching artifacts have passed their acceptance checks and been published with checksums. See the downloads page for the current availability summary.

Desktop app

• Linux (x64). Tested by the developer. Final release packaging and publication are in preparation. The initial target baseline is Ubuntu 24.04 x64; the installed app’s sandbox and package lifecycle have been checked in Ubuntu 24.04 virtual machines. An Arch x86_64 package is produced with native tooling and passed its install, sandbox and removal checks in an Arch virtual machine, with its remaining acceptance still open. Linux testing to date is development-host evidence, not a claim of distribution-wide certification.
• Windows (x64). Pending testing on real Windows systems. No Windows download is available, and none will be announced before real install, runtime and lifetime acceptance is recorded.
• macOS. Deferred. No release packaging or acceptance is implemented, so no macOS build should be expected in the 0.1.0 timeframe.

Browser app

The browser app is in preparation for public release. A working preview is served at /demo/. It shares the audio policy with the desktop app and runs local WASM codecs. Application source and verified codec source/build materials accompany the preview. A tagged 0.1.0 release remains in preparation.

Planned initial downloads

When 0.1.0 is published, downloads will appear on the downloads page per platform:

Target	Planned initial download
Ubuntu 24.04 x64	.deb package
Arch x86_64	Optional .pkg.tar.zst package
Windows x64	Per-user .exe installer; optional portable .zip

Every published artifact will ship with SHA-256 checksums, provenance, and the complete matching source, build and license materials described on the licenses page. Additional formats — Flatpak, AUR, WinGet — are later-channel projects that each need their own acceptance; they are not available now.

What has not changed

Release work does not soften the scientific policy. Preparation validity, delivered-byte verification, fixed-trial scoring and the validity-versus-audibility boundary described in the scientific policy are part of every build.