From ed6c2bc4986585ad86672f7fde9d367496eb0e4d Mon Sep 17 00:00:00 2001 From: Meta Vens Date: Sun, 13 Sep 2026 20:52:57 +0200 Subject: [PATCH] Record the sequenced read rule for latest-value consumers Operator chose option A on all three: a public cache read returns a document with the current sequence, and consumers subscribe before reading; OnUpdate and CultNet's derived streams stay unprotected and documented as such; schema-alias handles and removals are documented as not stale-protected. Co-Authored-By: Claude Opus 5 --- docs/cultcache-migration-cut.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/cultcache-migration-cut.md b/docs/cultcache-migration-cut.md index a70ce85f8..a066642d3 100644 --- a/docs/cultcache-migration-cut.md +++ b/docs/cultcache-migration-cut.md @@ -607,6 +607,13 @@ home store, before `_entries` changes. `_lifecycleGate`, and could stall a cache on an interrupted wait; and a non-blocking delivery queue, which kept the same authority in the cache. Cross-process order stays with `StoredAt` and conditional commit. +- Latest-value consumers subscribe first, then take the cache's one sequenced + read (document and current sequence under the gate) and ignore any change at + or below that sequence (operator decision 2026-09-13; Soul found CultMesh + mirrors' snapshot reads carried no sequence). `OnUpdate` and the streams + CultNet derives from it carry no sequence and are not order-protected; + schema-alias handles and removals are not stale-protected. Both are + documented, not fixed here. - Follow-ups outside this migration (found while landing the sequence, CultLib `4562340`; none introduced by it): `CultNetDatabaseSubscriptionServer.ApplyProjectedChange` keeps a latest value per record from `CultNetDatabaseChange`, which carries no