aboutsummaryrefslogtreecommitdiffstats
path: root/src/remake
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-15 02:50:18 +0000
committertv <tv@krebsco.de>2026-11-15 02:50:18 +0000
commit58efa560c03da03a6c10eaa7efc212fab28ebab2 (patch)
treecf6033c1935f0949586d0c4fb50705f94bfce41c /src/remake
parent22940ca24fb736f43ddc6d6fb9a4b8b0ee638ee8 (diff)
federation: parties vote, rules say who writes, remakes only carry
The design asks less of continuum and of remakes: - Parties vote; there are no voters apart from them. - The policy's rules say who writes where: paths with `*`, `**` and `{party}` (`names/{party}.r`), each naming its writer, the first that matches deciding; shared identifiers are rules, given by versions. The federation's own paths are fixed by its number. - A swarm says which federation it follows (this design is 1); a change to the federation is a design of its own with the next number. - A passed proposal is written as the chain's current version by any party; what lapsed, or doesn't count, any party may delete. - A value counts only while the key that signed it is its party's: a removed key takes back all it signed, the party signs again what was its own. Deletions stay until the key of what they deleted goes. - Agreement holds while fewer than a third of the parties vote twice, as the design now says. - A party without nodes writes through any node; node lists say who is a member and whom a node syncs with. - Remakes are continuum's, when and with whom it likes, of any kind that loses and adds nothing; writes after the base are each judged again, with no replay window. - A fork is a chain of its own within the same document; nodes follow one chain and sync with its parties' nodes only. - What Automerge limits are recommendations; denial of service breaks no promise.
Diffstat (limited to 'src/remake')
0 files changed, 0 insertions, 0 deletions