From d7b511e7cd23a7264b8f02b5ade29bc5674b678f Mon Sep 17 00:00:00 2001 From: tv Date: Mon, 16 Nov 2026 16:39:12 +0000 Subject: store: what is above some heads names nothing before them An event above some heads has each of its dependencies among them or above them, not only them all in its history. The store holds after its checkpoint only events whose dependencies are its heads and the events after them, and so it holds every event above them: one naming an event before them as well is refused by a node that moved, and never taken by one starting from the checkpoint, which never held what it names. Tests show it for an event offered after the move and one taken before it. --- docs/store.md | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) (limited to 'docs/store.md') diff --git a/docs/store.md b/docs/store.md index b766d41..81f508f 100644 --- a/docs/store.md +++ b/docs/store.md @@ -22,9 +22,9 @@ lower-case hex digits. In its bytes it names the events it builds on, its **dependencies**, by their IDs; how it names them is its fold's. An event's **history** is everything it builds on: its dependencies, theirs, and so on, which its ID fixes. The **heads** of a set of events are the events nothing in it builds on. An event is -**above** some heads where it has them all in its history, and every event of its -history that isn't one of them, nor in their history, has them all in its own: it builds -on them, and on nothing written beside them. None of the heads is above them. +**above** some heads where it has them all in its history, and each of its dependencies +is one of them or above them: it builds on them, names nothing before them, and builds on +nothing written beside them. None of the heads is above them. ## Checkpoints @@ -35,11 +35,10 @@ by the hash of its encoding, which its fold gives, and built byte for byte from heads, so every node holding the history up to them builds the same one. A store holds a checkpoint, the events it keeps, byte for byte, and the events after it: -each above the checkpoint's heads, its dependencies among those heads and the events -after them. The heads are held by their IDs, whether the checkpoint keeps them or not, -and a head brought again is taken as held; a root is its own checkpoint's one head -(below). A store takes an event only once it holds its dependencies, so it holds every -event's history back to its checkpoint. +each above the checkpoint's heads. The heads are held by their IDs, whether the +checkpoint keeps them or not, and a head brought again is taken as held; a root is its +own checkpoint's one head (below). A store takes an event only once it holds its +dependencies, so it holds every event's history back to its checkpoint. A store's first checkpoint is its **root**, taken without judging, whose ID is the store's: its bytes are a checkpoint's, which no fold reads as an event, so the store -- cgit v1.3.1