RVLTION Download

Changelog

No public release yet.

RVLTION has never been released. This page exists so that when it is, the history starts here rather than being reconstructed later.

Unreleased

Version 0.1.0 exists as a build on the developer machine. It has not been published, and there is no download for it. Listing it as released would be the first false statement on this site.

What that build contains:

  • Clipboard capture on Windows, event driven, with a privacy gate that runs before anything is written.
  • Timeline with temporal navigation, and an inspector showing where each fragment came from.
  • Deterministic session detection with plain language evidence, and the reveal.
  • Revelations: kept contexts with preserved provenance, distinguishing what was found from what was added later.
  • Reconnection, which suggests and never adds.
  • FIND, deterministic local retrieval with explainable results.
  • Single instance enforcement, and clean shutdown with no orphan processes.
  • A single decision point for every question of belonging, which returns an answer together with the evidence that decided it, and has no total or score anywhere in it.
  • Threads about a neighbouring subject kept apart and named, and fragments the engine looked at and could not place recorded as held. Both are shown in the reveal rather than known only internally.

What it is missing before it could be released:

  • A code signing certificate. Unsigned builds trigger SmartScreen and may be refused outright by Smart App Control.
  • Hosting for the artifacts.
  • A public support and security channel. There is none today, deliberately, and one has to exist before anyone is asked to install this.
  • Jurisdiction-specific legal terms. The written terms are on the legal page; governing law and liability provisions need counsel.
  • The macOS backend compiled and run at least once. It is written and has never been built. Linux is done: the binary, the Debian package and the AppImage have each been launched and observed capturing.

Released versions

None.

How versions work

One version number, defined in tauri.conf.json and matched in the Rust and Node manifests. Installers take their version from the same place, so an artifact filename always matches the build inside it.

Until there is a first release, this page will keep saying there is not one.