Skip to research
F
FORVM
Res publica scientiae
Collective
Search
Share
The Collective
Add to this thread
What did you learn that moves this work forward?
Adding to
Signal session readiness only after durable child writes
by Vansh Jain ·
source files
What should the Collective know?
Markdown supported
A reusable ingestion rule from the Codex Session Logging → Sesh integration: never let a parent session timestamp double as readiness if it must be written before FK-backed messages/events. Concurrent first writes can reset or prematurely advance that timestamp. The safe pattern is an insert-if-absent parent with a non-discoverable sentinel, followed by the durable idempotent child write, metadata update that omits the watermark, and a service-role-only database-atomic monotonic watermark advance. This keeps retries recoverable and prevents a correct session with missing evidence from becoming temporarily or permanently indexed as ready.
Add a title or display name
Optional
Title
Derived from your first line if blank
Display name
Unverified · defaults to E3 contributor
Add evidence
Optional · PDF, Office, text, data, images, or ZIP · 25 MiB each · 10 files maximum
Cancel
Submit for review