Why we built save points for writers

Every writing tool already saves your work. Autosave is table stakes — nobody loses a screenplay to a crash anymore. So when writers hear that Inkwell has "save points," the reasonable first reaction is: I already have that. You don't, and the difference is the whole point.

Autosave protects the file. It does not protect the decision.

Autosave answers one question: what is the latest state of this document? That is a storage question, and it is solved. But writing is not storage. Writing is a sequence of decisions — to cut the cold open, to give the antagonist the better line, to try the whole second act in present tense. Autosave flattens all of those decisions into a single moving target. The version where Act 2 still worked is gone the instant you keep typing.

Writers already know this, which is why the folder of any working screenwriter is an archaeology site: SCRIPT_v4.fountain, SCRIPT_v4_FINAL.fountain, SCRIPT_v4_FINAL_real.fountain, SCRIPT_notes_from_jenny.fountain. Those filenames are a manual version-control system invented out of necessity. They are also brittle, unsearchable, and impossible to diff. The instinct is right; the tool is missing.

A save point is a named moment you can always return to

Borrowed from how software is built — but reshaped for prose — a save point is an immutable, content-addressed snapshot of your draft at a moment you chose to mark. "Table read draft." "Before the studio notes." "The version where she doesn't come back." You can keep writing without fear, because that moment is preserved exactly, forever, and it is one click away.

• Immutable — a save point never changes after you create it, so "go back to the table-read draft" always means exactly what it meant.
• Content-addressed — identical content is stored once, so a hundred save points of a lightly-edited scene cost almost nothing.
• Named by you — the value is the label. A timestamp tells you when; a name tells you why.

That last point is the one we obsessed over. The mechanics of snapshotting are solved computer science. The product problem is making the act of naming a moment feel as light as hitting save — because a version-control system nobody uses is just an expensive backup.

Once moments have names, everything downstream gets easier

Naming moments is not the end of the story — it is the foundation the rest of Inkwell stands on. Because save points are real, structured snapshots rather than a pile of files, the tools that operate on them can be precise. You can compare two save points and see semantic changes — this line of dialogue rewritten, that scene moved — instead of character-by-character noise. You can branch a save point into a draft line to try an alternate ending without touching the original. You can let an AI skill propose edits against a known, stable version instead of a document moving underneath it.

None of that works on a folder of similarly-named files. All of it works when a draft is a sequence of named, immutable moments. That is why save points came first: not because version control is exciting, but because it is the substrate that makes everything else trustworthy.

Autosave keeps you from losing your work. Save points keep you from losing your nerve. You can take the risk — cut the scene, try the other ending, accept the bold note — because going back is no longer an act of reconstruction. It's a click.