Why finality?

The friction

Two things happened to reading. First, much of it became editable: articles can change after they are quoted, pages can be silently updated, and often you cannot be sure the words you read yesterday are the words someone else reads today. Then AI made content infinite. The result is a web where nothing is ever finished, and finishing is the one thing attention actually wants.

The shift

When generating text is free, commitment becomes the scarce thing. A numbered, dated, sealed edition is a small act of commitment: this is what I said, on this date, and if I was wrong you will see the correction, not a rewritten past.

The concept

A printing press for the web. Not a blog (editable), not a feed (endless), not a blockchain (permanent in the wrong way). Editions, errata, done. The first thousand users would be the writers who already feel this: newsletter authors tired of infinite drafts, essayists who want their work to have a spine, readers who want to finish something and shelve it.

What this demo can and cannot claim

This demo stores editions in your own browser and seals them with a digest you can verify. It cannot enforce immutability, prove authorship or date, or survive a cleared browser. The full concept would need hosted, timestamped, append-only storage to make seals meaningful across devices - that is deliberately out of scope for this experiment.

Prior art is real: scholarly publishing has versioned records (Crossref versioning, Crossmark), arXiv keeps all versions public, perma.cc freezes citations, and a sent email newsletter is already uneditable. What we did not find among checked players: a consumer web platform that treats sealed editions and open errata as the core ritual rather than an archive feature.