The fragments survive. The reason evaporates.

The problem

A clipboard manager can tell you what you copied. Scroll back far enough and there it all is: links, prices, notes, snippets, in the order they happened.

What it cannot tell you is what you were doing. The six fragments that were one afternoon of research look exactly like six unrelated fragments, because the thing that connected them was never part of what got saved. You are left reconstructing your own reasoning from a list.

That gap is the whole product. Not storage, which is solved. Context.

The approach

RVLTION records locally, then looks for structure in what accumulated. When a run of copies turns out to be about one thing, it says so and shows the evidence. You decide whether that connection is worth keeping, and if it is, it persists with the reasons attached.

Later, when related activity appears, it can point back at the context you preserved. It suggests. It does not act.

The intelligence is deterministic on purpose. Repeated words, repeated sources, timing, and a few shape rules. No model, nothing learned, nothing to train. That constraint is what makes every conclusion explainable in a sentence, and a system that reasons about your own work is only worth trusting if it can show its working.

Principles

• Silence is a valid answer. Interrupting wrongly costs more than missing a connection, so the gates are set to stay quiet.
• Evidence, not scores. The interface never shows a confidence percentage, because a number implies a precision the evidence does not have.
• Nothing is added on your behalf. RVLTION finds and suggests. Keeping and accepting are yours.
• Local is architectural. There is no network code to disable, so there is no setting to get wrong.
• Say what is true. Including the parts that are unflattering, like the database being unencrypted and the builds being unsigned.

Where it is

RVLTION runs on Windows, where it is built, installed, and used daily, and on Linux, where the binary, the Debian package and the AppImage have each been launched and observed capturing the clipboard on an X11 session. The macOS backend is written and has never been compiled. Those are different states and this site keeps them apart.

There is no company, no account system, and no server. It is a desktop application that keeps its data on your desk. Current state is on the changelog.