Skip to content

Release · S386-S386

An accepted critical save must not be submitted twice

If a critical save is accepted but storage cannot confirm its outcome, the response now tells human and agent clients not to resubmit automatically. Previously, some storage failures invited a retry even though the original intent remained retained, so repeating the request could apply the change twice. The response preserves the underlying storage receipt, and retained work can recover without repeating the business request. A critical change refused before acceptance remains retryable, and a lost acknowledgement that can be verified still resolves successfully. Both storage formats are covered. This correction does not add cross-request idempotency or change the independent participant-data and retention-reserve readiness limits.

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 →