State Machine
The Decision Lifecycle State Machine is the authoritative deterministic model for QUORUM. It defines the strictly linear path from initial event ingestion to the immutable commitment of the system state.
01 // Core Lifecycle Graph
Transition Logic
export const STATE_TRANSITIONS: StateTransition[] = [ { from: "INGESTED", to: "VALIDATING", governed_by: "system" }, { from: "ARBITRATION_PENDING", to: "ARBITRATED", governed_by: "arbitration" }, { from: "EXECUTING", to: "EXECUTED", governed_by: "execution" }, { from: "AUDITED", to: "COMMITTED", governed_by: "system" } ]; // FAILURE_MODES export const FAILURE_TRANSITIONS: StateTransition[] = [ { from: "ARBITRATION_PENDING", to: "FAILED", condition: "conflict_unresolvable" }, { from: "AUDIT_PENDING", to: "DEAD_LETTERED", condition: "audit_write_failure" } ];
System Semantics
Arbitration Modification
The arbitration phase is the only layer permitted to modify the "Decision Result" section of the decision object. Once arbitrated, the outcome logic is frozen.
Execution Lock
The state machine locks the entire decision object upon entering the EXECUTING state, preventing concurrent mutation or logic drift during action dispatch.
Audit Sealing
The final transition to COMMITTED is only permitted after the audit ledger has returned a cryptographic confirmation signature, sealing the state record.
Operational Guarantees
Deterministic Transitions
States are strictly ordered. No event can bypass the arbitration layer or jump to execution without a valid authority chain.
Explicit Failure Handling
All failures are terminal unless explicitly flagged as retryable. Dead-lettered events retain their full state vector for post-mortem analysis.