Struct ReadinessGate 

pub struct ReadinessGate { /* private fields */ }

Readiness gate: tracks two subsystems (state store, engine) and exposes a single is_ready() that returns true when the daemon can safely serve protected API routes.

Implementations

impl ReadinessGate

pub fn new(deadline_secs: u64) -> Self

Create a new gate in Warming state for both subsystems. deadline_secs is the wall-clock (Unix epoch) at which any still-Warming subsystem is force-promoted to Degraded. Pass 0 to disable the deadline.

pub fn set_deadline_secs(&self, secs: u64)

Update the wall-clock deadline for force-promoting Warming → Degraded. Pass 0 to disable enforcement.

pub fn deadline_secs(&self) -> u64

Read the current deadline (Unix-epoch seconds, or 0 if disabled).

pub fn set_state_store(&self, s: SubsystemState)

Update the state-store readiness.

pub fn set_engine(&self, s: SubsystemState)

Update the engine readiness.

pub fn state_store_state(&self) -> SubsystemState

Read the current state-store state.

pub fn engine_state(&self) -> SubsystemState

Read the current engine state.

pub fn is_ready(&self) -> bool

true when the gate is open: both subsystems are Ready or Degraded. A Failed (or still-Warming) subsystem keeps the gate closed. Degraded counts as ready so a missing API key (engine) or a slow-but-functional state store does not lock the user out after the deadline elapses (RFC-024 SP4).

pub fn enforce_deadline(&self)

Force-promote any still-Warming subsystem to Degraded once the deadline elapses. Idempotent. Should be called by the kernel during init and by the readiness middleware to enforce a ceiling on how long a misconfigured engine can lock the gate.

Trait Implementations

impl Debug for ReadinessGate

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.