From b489a57a77753ff9a618486bffccf8b342e86a9b Mon Sep 17 00:00:00 2001 From: Nicky Leach Date: Tue, 6 Oct 2026 08:07:45 -0700 Subject: [PATCH] Clarify the one-time journal baseline Distinguish the migration baseline from runtime delivery, which has no later backfill scan. Co-Authored-By: Paperclip --- doc/DATABASE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/DATABASE.md b/doc/DATABASE.md index c3f363bb545..4e8bb3a3a57 100644 --- a/doc/DATABASE.md +++ b/doc/DATABASE.md @@ -540,7 +540,7 @@ for each plugin and event; plugin and event deletion cascade acknowledgments. Reads return creation first, then the earliest unacknowledged transition for each resource, up to 100 resources. Acknowledging a later event is rejected. Reads never consume work, so crashes, retries, and restarts cannot lose a hook; concurrent reads can repeat an -event. There is no global cursor or backfill scan. Consumers must serialize their +event. There is no global cursor or runtime backfill scan. Consumers must serialize their processing and make provider operations idempotent before acknowledging success. Retention and provider integration remain separate work.