Struct StatusWorkflow 

pub struct StatusWorkflow;

Status rules for reporting Auths state.

The consumed surface is StatusWorkflow::compute_readiness (per-device readiness from expiry/revocation) and StatusWorkflow::next_steps_from_readiness (the next-step rules). The CLI (auths status) loads identity/devices/agent itself and calls these — they are the single source of truth for the rules.

Implementations

impl StatusWorkflow

pub fn next_steps_from_readiness( identity_present: bool, readinesses: &[DeviceReadiness], agent_running: bool, ) -> Vec<NextStep>

The next-step rules, keyed on the minimal facts they need — identity presence, each device’s readiness, and whether the signing agent is live. The single source of truth for these rules, including the recovery single-point-of-failure signpost, so any presentation layer (the CLI) shares them rather than re-deriving its own.

Args:

• identity_present: whether an identity is initialized.
• readinesses: the readiness of each device in the roster.
• agent_running: whether the signing agent is live.

pub fn compute_readiness( expires_at: Option<DateTime<Utc>>, revoked_at: Option<DateTime<Utc>>, now: DateTime<Utc>, ) -> DeviceReadiness

Determine device readiness given expiration timestamps.