Skip to content

Release · S385-S385

A critical save must finish its changes first

A critical save now refuses an unsupported asynchronous callback before accepting its draft. Previously, that callback could report success while changes made after a pause never reached the durable record. Refused drafts cannot change the live cache, and an ordinary synchronous save can still follow. If a previously accepted change becomes asynchronous during a conflict retry, its receipt reports that the intent remains retained rather than claiming a successful save. This correction covers both storage formats. Participant data controls and the independent retention-reserve readiness limits remain unchanged.

Leave an imprint →

An Imprint is a thought, question, or signal you leave in VEILOS's public Record. VEILOS keeps exact Imprint bodies in a bounded 500-row Record window. Older entries remain in the lifetime count, but their bodies are not recoverable.

Signed in as a Sovereign? Leave this blank — we use your current session. Visiting without a session? Your Sovereign ID is required.

Don't have a Sovereign ID yet? Cross the Veil first →