Table of Contents

Enum ErasureWriteOutcome

Namespace
Excalibur.Compliance
Assembly
Excalibur.Compliance.Abstractions.dll

What a fenced write against an erasure request actually did.

public enum ErasureWriteOutcome

Fields

Applied = 1

The write was applied. Proceed.

ClaimLost = 2

The caller's claim is no longer the one the request carries, so nothing was written.

Stand down silently. Write nothing further for this request — including any terminal-failure record — and do not report a defect. Another executor holds the request and is handling it, and a terminal failure written here would mark as failed an erasure that is in progress elsewhere.

A lapse alone does not produce this. Only a RE-CLAIM does. An executor whose run outlasted its own lease, but whom nobody superseded, still holds the identity the request carries and its writes still apply — otherwise an erasure that destroyed keys could never issue the certificate attesting it.

NotDetermined = 0

Nothing decided this. The write must not be treated as having been applied or refused.

Reachable only from a default value, so a caller that sees it has been handed a result nobody produced. It exists to make that case nameable rather than to be returned.

NotFound = 4

No such request exists in the ambient tenant.

On a write made while holding a claim this is an anomaly rather than an ordinary outcome: the row went away underneath a live claim. Report it.

StatusRefused = 3

The request exists and the caller holds its claim, but the transition is not legal from the current status, or an expected status was supplied and did not match. Report it.

This is a caller error, not a race, and that is a change in what the status predicate means. Before custody was enforced by the claim, a status refusal was how a loser discovered it had lost; now the claim answers that question, so a status refusal while holding the claim says the caller asked for a transition its own state machine should never have requested.

Remarks

A bool conflated a race with a defect. The status write returned true or false, and false meant any of: the row is gone, the transition is illegal, or another executor has taken the request. The first two are caller errors worth reporting; the third is the ordinary outcome of an ordinary race and the only correct response is to stand down silently. A caller that cannot tell them apart either logs a defect on every normal handover or reports nothing on a real one.

Zero is deliberately not a success. A default value, an unassigned field and a task that completed without setting a result all read as NotDetermined. Had zero meant applied, each of those would assert a durable write that never happened — and on the completion write that assertion is a signed certificate. Implementations must never return it and must refuse a presented default.

Test for Applied by name, never by excluding the refusals you know about, or every member added later begins life meaning "it worked".