Struct StewardEngine 

pub struct StewardEngine { /* private fields */ }

Implementations

impl StewardEngine

pub fn new( profile: StewardProfile, config: StewardConfig, handle: Arc<dyn StewardClientHandle>, store: Arc<SqliteAgentMemoryStore>, transcripts: Arc<dyn TranscriptSource>, realm: impl Into<String>, ) -> Self

pub fn with_gating(self, gating: Arc<dyn MemoryGatingBridge>) -> Self

pub fn with_conflicts(self, conflicts: Arc<dyn MemoryConflictBridge>) -> Self

pub fn with_events(self, events: Arc<dyn MemoryEventSink>) -> Self

pub fn with_mob_context(self, source: Arc<dyn MobPurposeSource>) -> Self

pub fn with_operator_routing(self, active: bool) -> Self

Activate §7.2 operator-scope routing (P4, operator_scope = "provisional"): the op mapper accepts operator-scope creates, and held operator-scope proposals become acceptable on this and every later dream (the §7.2 un-hold — held verdicts re-enter each dream’s signals by construction).

pub fn config(&self) -> &StewardConfig

pub fn realm(&self) -> &str

pub fn note_session_completed(&self)

Event-gate signal: one completed session/interaction.

pub async fn note_identity_retired( &self, identity: &str, session_key: Option<&str>, cause: &str, )

Retire/delete hook (§8.5 exit interviews): record the identity for the next dream’s harvest sub-phase. Best-effort; rotation never fails on this.

pub fn dream_cadence(&self) -> Duration

The configured dream cadence as a concrete interval. The durable schedule host (§ ask 7 / P5) uses this to drive the dream runnable; falls back to the same 6h default the in-process loop uses when the cadence marker is malformed.

pub fn spawn_dream_loop(self: &Arc<Self>) -> JoinHandle<()>

The guarded interval loop — the in-process fallback used only on gateways with no schedule host. When a schedule host is present the dream is driven as a durable, misfire-aware host-runnable occurrence instead (see schedule_wiring::steward_dream_runnable_host / ensure_steward_dream_schedule).

pub async fn dream_now(self: &Arc<Self>) -> DreamOutcome

One dream attempt: cheap event gates (CC-style ordering — counter first, one store stat only when the counter alone is short), then the budget (lock + window), then the pipeline.

impl StewardEngine

pub async fn resolve_gating_notice(&self, notice: GatingResolutionNotice)

Resolve a gating decision for one of this realm’s staged promotions. Called by PromotionGateResolver; unknown pending ids are not ours and are ignored.