aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-06 20:56:23 +0100
committertv <tv@krebsco.de>2026-11-06 20:56:23 +0100
commit7972812fcd2acc4b1d4ab86045d8160b0f0f6ae8 (patch)
tree78adf8464c4821afdff5b34f6d3c372913a6897c /docs
parente9ba6e3119b41935a36addca9cb0afa85074b7ac (diff)
dashboard: remake
Diffstat (limited to 'docs')
-rw-r--r--docs/dashboard.md9
1 files changed, 9 insertions, 0 deletions
diff --git a/docs/dashboard.md b/docs/dashboard.md
index 5a36dd2..143fcc5 100644
--- a/docs/dashboard.md
+++ b/docs/dashboard.md
@@ -271,6 +271,15 @@ key, is listed but can't be opened.
In the protocol data, values and keys get the same readings as in the figures: the
aliases of node IDs (a member's entry, a vote, a coordinator), times and sizes.
+**`remake…`** at the right of the title proposes a remake ([`remakes.md`](remakes.md)),
+this node coordinating it: `compact` (the same content, without its history),
+`replace` (the new store root as JSON, typed or from a file, which fills the text to
+look at first) or `import` (an Automerge document, a backup, uploaded as it is); for the
+last two, rules for the writes made meanwhile (a path prefix moved to another, or
+dropped; what no rule covers is quarantined on the node that made it), and for any, how
+long votes are collected. The answer shows below: the remake's ID, or why it was refused
+(and the API's override, if any). The map shows the votes as they come.
+
## Console
The messages this node exchanged with its peers, one by one: when (on the 24-hour