Download
The engine first, then the app
One download. The engine that reads your work ships inside the app, so there is no Python to install, no repository to clone and no terminal to open.
macOS
macOS 14 or later · Apple silicon and Intel · Notarised by Apple
Builds are signed and notarised but not public. Watch the repository’s releases and GitHub will tell you when the first one lands. There is no mailing list, because there is no account and nothing to put you in one.
Windows
A Windows version is planned. The part that reads your work is already portable — it is the same code on every platform, and an identity moves between machines as one file. What has to be rebuilt is the window that draws it, and that is the work in front of us.
The first run
On first launch it asks which sources it may read, and it connects nothing until you say so. The first pass takes a couple of minutes; after that it keeps up on its own, or waits until you ask.
What you get
A thin identity, and that is correct
The engine holds back anything it has seen once. A first distillation produces fewer rules than you expect, and the number grows as the evidence does.
Some rules will be wrong
Open one, read what produced it, and hide it or answer the question the engine raised. That loop is the product.
Nothing is connected to an assistant yet
Today it shows you the identity. The connection to the tools you already use is next — see the roadmap.
Verifying the build
Every release is signed with a Developer ID certificate, built with the hardened runtime, and notarised by Apple with the ticket stapled to the disk image. You can check any copy yourself before you open it — the commands are on the security page.