Enum ErasureClaimOutcome
- Namespace
- Excalibur.Compliance
- Assembly
- Excalibur.Compliance.Abstractions.dll
Why a request was, or was not, granted to a caller for execution.
public enum ErasureClaimOutcome
Fields
AlreadyClaimed = 2Another process holds a claim that has not lapsed. Skip quietly and release any retry budget held against this request.
Releasing the retry budget is the part that is easy to miss. The request comes back on its own when the holder's claim lapses, so spending a retry attempt on another instance's work drives this request toward a terminal failure it never earned.
Granted = 1The caller now holds the request, and the result carries the identity it must present on every attestation write it makes for this run.
NotDetermined = 0Nothing decided this. The caller holds no claim and must not execute.
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 = 4No such request exists in the ambient tenant. Permanent: drop it and report it.
StatusMismatch = 3The request exists and is not in the status the caller expected, so this path will never be able to execute it. Stop offering it here.
Distinct from AlreadyClaimed because the two have different futures: a claimed request returns by itself, and a request in the wrong status does not.
Remarks
Custody and outcome are different questions, and this enumeration exists because they were being asked on one axis. An erasure request's status says what HAPPENED to it. Whether some process is currently responsible for it is a separate fact, and it used to be inferred from the status: a request in the in-progress status was taken to be in somebody's hands. Nothing recorded WHOSE hands or for how long, so a request whose executor died was in-progress forever, every query that looked for work correctly excluded it, and nothing anywhere reported that a subject's data had not been erased.
Zero is deliberately not a grant. A default value, an unassigned field and a task that completed without setting a result all read as NotDetermined. Had zero meant granted, each of those would have handed a caller permission to destroy a data subject's keys that nothing had granted. Implementations must never return it.
Test for Granted by name. A caller that proceeds whenever the outcome is not one of the refusals it knows about gives every member added later the meaning "go ahead".