1.7 Know what changed

Exploring

Review and recover without becoming a source-control client.

After 1.0. Version numbers mark the intended order, not dates or paid upgrades; scope is provisional and may change with evidence and demand. Checked against the development repository on 15 October 2026.

In short

Review and recover without turning into a source-control client. 1.7 keeps a local history at each save.

Compare the current text with earlier saves or snapshots, restore or copy from them, and see changed lines marked in the margin. The same comparison helps when a file changes on disk while you’re editing it.

In practice

You rewrote a section an hour ago and want one paragraph back: open the history, compare with the last save and copy just that paragraph.

Why it isn’t simple

  • History needs somewhere to live. Keeping every save of every document takes space, so it needs limits, and it has to follow files through renames and moves without cluttering your folders.
  • Comparing prose is harder than comparing code. Rewrap one paragraph and every line looks changed. A useful comparison has to show what you actually changed, not every line the wrapping moved.
  • It mustn’t turn into a second Git. No branches or merges means deciding carefully what history covers and what it doesn’t.

What it won’t do

  • History stays on your Mac, and the space it takes is bounded.
  • It isn’t a Git client.

What it covers

1.7Know what changed

Exploring

  • Local save-boundary history
  • Compare current text with saves/snapshots
  • Restore or copy from history; changed-line gutter
  • Reuse diff for conflicts with bounded local retention

Depends on Edit it naturally.

Product direction, October 2026Plan reference 1.7

Builds on

Leads to

Nothing else on the roadmap.

What the labels mean

Exploring
to be re-checked once earlier versions prove the approach.