From 24b88d04523450726126deb88aa9fb9180156883 Mon Sep 17 00:00:00 2001 From: Adam Horodyski Date: Fri, 19 Jun 2026 12:53:01 +0200 Subject: [PATCH] docs(SEQUENTIAL_QUEUE): drop overstated dedup guarantee from overview Co-Authored-By: Claude Opus 4.8 (1M context) --- contributingGuides/SEQUENTIAL_QUEUE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contributingGuides/SEQUENTIAL_QUEUE.md b/contributingGuides/SEQUENTIAL_QUEUE.md index f98a6293b31d..dcf378475eb5 100644 --- a/contributingGuides/SEQUENTIAL_QUEUE.md +++ b/contributingGuides/SEQUENTIAL_QUEUE.md @@ -2,7 +2,7 @@ ## Overview -The SequentialQueue is how the app keeps its **offline-first promise**: a user can "do their thing" regardless of connectivity, and every change they make is sent to the server **serially, in order, at the right time** (deduplicated server-side on the rare resend from a retry or leadership change), even across going offline, refreshing the tab, or restarting the app. +The SequentialQueue is how the app keeps its **offline-first promise**: a user can "do their thing" regardless of connectivity, and every change they make is sent to the server **serially, in order, at the right time**, even across going offline, refreshing the tab, or restarting the app. `SequentialQueue` is a **single-flight, first-in-first-out (FIFO), leader-only engine** that drains every `API.write()` request one at a time, with exponential backoff on failure, surviving offline periods and (for most requests) app restarts. It is a coordinator over four collaborators: