aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-16 14:35:13 +0000
committertv <tv@krebsco.de>2026-11-16 16:26:53 +0100
commit0dde043f1e8c6e8c99a876b4d0dffdd499a9c961 (patch)
treedef0e27869d92f18d91dc72d36dfc411c3aa3a5d /docs
parente320826b6fbaab162029ff16c53cfbdbb83231a5 (diff)
docs/store: a remake whose base comes before a checkpoint
A node that moved to a checkpoint after a remake's base, and switches to it, would have refused the snapshot for the events it forgot, and stayed apart from the nodes that switched. It keeps its own checkpoint instead, and reads none of what the snapshot holds that its checkpoint forgot, as it reads none of it in the old document; only its own refusals and its operator's drops keep it where it is. A snapshot's checkpoint before its own is one it takes.
Diffstat (limited to 'docs')
-rw-r--r--docs/store.md18
1 files changed, 11 insertions, 7 deletions
diff --git a/docs/store.md b/docs/store.md
index 9b81ac1..c51b9ca 100644
--- a/docs/store.md
+++ b/docs/store.md
@@ -268,14 +268,17 @@ record (its ID, its coordinator): two remakes at one base are two epochs.
* **After it switches**, a node puts again every event it holds beyond the base, each
after its dependencies, and, while it keeps the old epoch, syncs it with nodes still
on it and puts again what it takes there. Each event is taken again as it was: its
- history is in the new epoch too.
+ history is in the new epoch too. A node that moved to a later checkpoint since the
+ base keeps its own, and reads none of what the snapshot holds that its checkpoint
+ forgot, as it read none of it in the old document.
* **A node with an empty document**, or one that can't build a remake as no peer keeps
its base, takes the epoch its peers give it, or the one its operator pins, where the
- snapshot's checkpoint is one it can build, the root its operator names, or one its
- operator pins (Pinned checkpoints); it judges every event after it, and puts again
- what it held. Where it refuses an event the snapshot holds, it stays where it is. A
- made-up epoch can withhold events from it, and keep it apart from the others, but make
- it take nothing it wouldn't.
+ snapshot's checkpoint is one it can build, one before its own, the root its operator
+ names, or one its operator pins (Pinned checkpoints); it judges every event after it,
+ and puts again what it held. Where it refuses an event the snapshot holds, by its own
+ refusals or its operator's drops, it stays where it is; what a checkpoint of its own
+ forgot, it reads none of. A made-up epoch can withhold events from it, and keep it
+ apart from the others, but make it take nothing it wouldn't.
So a remake changes no event a node holds, only which document carries them, which the
fold never sees. A swarm that never remakes holds what one that remakes all the time
@@ -341,7 +344,8 @@ crafted changes. *Sim*: a simulation. *Bench*: measured, not judged.
| 22 | A checkpoint a node can't build, handed to it by peers | Taken only where its operator pinned it | unit |
| 23 | An event not above the heads of the checkpoint a node moved to | Refused; a change the node holds that carries one is dropped, its other events put again | unit |
| 24 | A node away while the others moved to a checkpoint and forgot what came before | It builds the checkpoint from what a peer kept, or takes it where its operator pins it | sim |
-| 25 | Flooding: events, writers, history, remakes | Slow, or out of memory; not wrong | bench |
+| 25 | A remake whose base comes before a checkpoint, switched after nodes moved to it | They switch, keep their checkpoint, and read none of what it forgot | sim |
+| 26 | Flooding: events, writers, history, remakes | Slow, or out of memory; not wrong | bench |
## Tests