Also known as draft history
A system that records distinct versions of a document you can compare and return to — in Inkwell, through save points, draft lines, and readable structural changes.
Writers already invent version control with folders and filenames; the cost is that nobody trusts which copy is current. Inkwell's writer-facing tools -- save points, draft lines, readable structural changes -- exist so decisions stay recoverable without asking you to manage a developer repository by hand.
The practical win is comparison: you can see what changed scene by scene between two moments instead of guessing from memory after notes land. That matters before a table read, after a page-one, and anytime a room argues about whether a cut helped or only felt safer in the moment.
The same primitives show up in Plot and in Canvas early access, because long-form documents need named history too. Start simple: label moments before risk, keep contested full drafts on draft lines, and restore when a path fails -- without treating history as a casual place to invent new parallels.
No. Inkwell uses writer-facing names -- save points, draft lines, incorporate -- and shows scene-level changes instead of asking you to manage repositories.
Yes. Canvas shares the same platform primitives as Plot -- named save points and draft lines on long-form documents in early access.
Create a named save point so you can restore or compare after notes. If you expect a full alternate path, open a draft line before the experiment begins.
Track Changes marks continuous prose. Screenplay version control here compares structured scenes and lines, which is how rooms already talk about what moved.
