Version browser over retained checkpoints #58

New issue

Closed

opened 2026-09-21 18:05:10 +01:00 by cruelacid · 1 comment

cruelacid commented

2026-09-21 18:05:10 +01:00

Owner

Part of #37. Depends on #38 having shipped and accumulated data.

What Relay does

Not shipped. Edit history is the single item on their Planned list —
committed, unbuilt.

Why this issue is later than its value suggests

The writer is in Phase 15 and this is in Phase 19 deliberately: a checkpoint
not written today cannot be browsed in June. The irreversible half ships first;
this half can wait, and is worth roughly double once the writer has been running
for months.

What changes

A view over the doc_checkpoints this client can decrypt, offering "restore this
note to how it was yesterday" and a diff between checkpoints. Restoring writes a
new version rather than overwriting — per CLAUDE.md, restoring must not itself
be a way to lose the current text.

Risk

risk:none. Reads data the server already holds; decryption is client-side, and
the server cannot read any of it.

A claim we can make that Relay cannot

Version history on a server that cannot read any version. Worth stating once the
feature is real — and not before, per docs/positioning.md.

Verification

Restore from a checkpoint and confirm the pre-restore state is still reachable.

Part of #37. **Depends on #38 having shipped and accumulated data.** ## What Relay does **Not shipped.** Edit history is the single item on their **Planned** list — committed, unbuilt. ## Why this issue is later than its value suggests The writer is in Phase 15 and this is in Phase 19 deliberately: **a checkpoint not written today cannot be browsed in June.** The irreversible half ships first; this half can wait, and is worth roughly double once the writer has been running for months. ## What changes A view over the `doc_checkpoints` this client can decrypt, offering "restore this note to how it was yesterday" and a diff between checkpoints. Restoring writes a new version rather than overwriting — per `CLAUDE.md`, restoring must not itself be a way to lose the current text. ## Risk `risk:none`. Reads data the server already holds; decryption is client-side, and the server cannot read any of it. ## A claim we can make that Relay cannot Version history on a server that cannot read any version. Worth stating once the feature is real — and not before, per `docs/positioning.md`. ## Verification Restore from a checkpoint and confirm the pre-restore state is still reachable.

cruelacid added this to the Phase 19 - Review and history milestone

2026-09-21 18:05:10 +01:00

cruelacid added the

labels

2026-09-21 18:05:10 +01:00

cruelacid referenced this issue

2026-09-21 18:08:51 +01:00

Relay feature parity, with end-to-end encryption (tracking) #37