From c12ce1a67e387474d17419bb252211bf04b2e443 Mon Sep 17 00:00:00 2001 From: tv Date: Tue, 3 Nov 2026 01:19:05 +0100 Subject: always announce new heads --- docs/architecture.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/architecture.md') diff --git a/docs/architecture.md b/docs/architecture.md index 9b9db71..cc738c1 100644 --- a/docs/architecture.md +++ b/docs/architecture.md @@ -225,8 +225,8 @@ catch-up source. The phases, what each serves and how the files come in: [`lifec the write lock, stamped with the clock) → `publish_change` (bumps the version, emits `DocumentChanged`) → the sync worker generates a message per neighbour → each neighbour applies it, relays its new heads to *its* neighbours, which pull what they -lack. In a full mesh (up to `k + 1` members) the writer reaches everyone directly, but -those on none of its transports, to whom the nodes between announce. +lack. In a full mesh (up to `k + 1` members) too: the writer may not reach everyone +the member list makes its neighbour. **An inbound message.** Consumer → `handle_message`: drop our own and stale-run replies, admit (swarm key), mark the peer seen, record its epoch (ignoring late ones), -- cgit v1.3.1