Epic: the site shaped by what the reader has done

The published site is the editor's view. The reader's view is that view minus what they have marked read, plus their notes, with a history of every action they can undo. Two named views to start ("the editor's" and "the editor of record's"), more audiences later. State lives in the browser now and in a vault later, so the daily agent can read it and several devices can share it. A graph of the pieces (what cites what, what follows what) is what the dynamic rendering and "read next" should be built on.

In this epic (7)

open 020 A wallet drained by actions (as pt.newsroom.sgit.ai)
open 021 Render pages from a graph of pieces, merged with the reader's state
open 048 Send the reader's feedback from the browser to the newsroom over an append lane
blocked 022 Store the reader's state in a vault, for the daily agent and other devices
done 017 Marking a piece read hides it from the front page and the sections
done 018 Two views: the editor's and the reader's
done 019 A history of every action, with undo and redo