Who should use this?
For Editors — 10 reasons
See where a draft came from, trace what was pasted in, and build trust with your writers — without ever making it adversarial.
-
Provenance you can see
A running Transcript records how a piece was written, so authorship is something a writer can show you rather than merely assert.
-
Trace what was pasted
Every copy/paste into a document is tracked in the Transcript and visible in the interface — nothing brought in from elsewhere quietly disappears into the draft.
-
A gentle AI-likeness check
Compare a passage against our AI cores to see whether it reads a little AI-like — a similarity signal to raise in conversation, never a claim or an accusation.
-
Non-adversarial by design
No accusations, no adverse inferences. It's a shared surface for you and your writer, not a gotcha machine.
-
AI that assists, never replaces
Any AI in the loop can suggest and organize, but is never allowed to place words in a document on its own. The writer stays the author.
-
The Scribble
A multi-branch history of everything typed. A cut passage or an earlier phrasing is easy to find and recover — down to a single line or word.
-
A Core that grows with the writer
The more someone writes, the better their style is recognized. Accuracy climbs as a writer's Core grows.
-
Private by design
The patterns that truly identify a writer never leave their machine — nothing but sha256 hashes ever reach our servers.
-
A calm place to work
Palette on the left, page in the middle. No clutter fighting for your attention while you read closely.
-
Export anywhere
Move the document out to whatever format your workflow needs, whenever you like. No lock-in.
Want provenance you can actually see?
Join the free Windows beta