Economic State Lifecycle¶

stateDiagram-v2
    [*] --> Unknown
    Unknown --> ConsensusHealthy: finalized fresh observation
    ConsensusHealthy --> ConsensusHealthyWithDust: micro gap
    ConsensusHealthy --> Warning: threshold degradation
    Warning --> Recovery: reduced effective balance
    Recovery --> ConsensusHealthy: repaired observation
    ConsensusHealthy --> ObservationQuarantined: malformed/conflict
    Warning --> StopLoss: slashing/ejection/critical balance
    Recovery --> StopLoss
    StopLoss --> Exiting: exit requested
    ConsensusHealthy --> Exiting: planned exit
    Exiting --> Settlement
    Settlement --> Settled
    ObservationQuarantined --> ConsensusHealthy: valid evidence replaces hold

Data Sources¶

Economic state is fed by updateRiskObservationFinalModel, receipt records, reserve coverage proofs, safe epoch updates, network phase, source ledger ids, and settlement events.

Transition Controls¶

Same-epoch replay is ignored only when hash matches.
Same-epoch conflict moves to a closed/conflict state.
Source ids and source groups prevent duplicate economic accounting.
Stale observations fail closed for claim enablement.
Reserve-backed smoothing is capped by vault and aggregate exposure.

Operator Implications¶

Backend/oracle engineers must provide ordered, finalized, source-unique evidence. Operations must not manually “fix” state by changing reserve or trigger controls without reconciling source ids and receipt ledgers.

Contract References¶

CenturionEconomicController.updateRiskObservationFinalModel
recordVaultReceiptFinalModel
setReserveCoverage
setClearedSafeEpoch
hardenNetworkPhase
CenturionClaimGatekeeper.deriveRiskState
deriveClaimState

Expanded State Model¶

State List¶

Uninitialized.
ObservedHealthy.
HealthyWithDust.
Deficit.
Recovery.
ExitOrSlashing.
Settlement.

Transition Table¶

From	To	Transition trigger	Actor or data source	Fail-closed behavior
`Uninitialized`	`ObservedHealthy`	Source event/function evidence	Operator or controller data source	Fail closed if evidence missing
`ObservedHealthy`	`HealthyWithDust`	Source event/function evidence	Operator or controller data source	Fail closed if evidence missing
`HealthyWithDust`	`Deficit`	Source event/function evidence	Operator or controller data source	Fail closed if evidence missing
`Deficit`	`Recovery`	Source event/function evidence	Operator or controller data source	Fail closed if evidence missing
`Any live state`	`ExitOrSlashing`	Source event/function evidence	Operator or controller data source	Fail closed if evidence missing
`ExitOrSlashing`	`Settlement`	Source event/function evidence	Operator or controller data source	Fail closed if evidence missing

Contract And Function References¶

Use the generated Solidity inventory to reconcile each transition with the current contract functions and events before relying on the state machine for production. For economic state transitions, source-grounded references must include the relevant controller, deposit, governor, gatekeeper, factory, or vault function named by the page.

Operational Impact¶

Every transition changes what an operator is allowed to do next. A transition into a blocked, cancelled, slashed, unsafe, or final state must stop routine automation until an independent reviewer confirms the next runbook.

Incident Implications¶

Unexpected transitions are incident evidence. Archive block number, transaction hash, decoded events, current state reads, and offchain source data. If the transition cannot be traced to a known runbook or approved automation, escalate before retrying dependent actions.