Struct MonitorResolverConfig 

pub struct MonitorResolverConfig {
    pub enabled: bool,
    pub model: Option<String>,
}

Whether the durable monitor may ask a model what to do about a terminal failure the structured rules did not settle.

Off by default, and not merely as a courtesy: enabling it lets a background daemon send monitor context to a model on its own schedule, with no one watching. Nobody watching is not permission, so this is a decision a user makes once, explicitly, rather than something an upgrade makes for them.

The bound on how often it may ask is NOT here: one proposal per observation cycle is an invariant of the design, not a knob (see mur_core::monitor::resolver). A tunable would let a user turn a bounded feature into an unbounded one.

Fields

enabled: bool

Opt-in. While false, nothing in the resolver path runs and no request leaves the machine.

model: Option<String>

Which model to ask. None uses the same backend mur chat resolves, so a user who has already configured one does not configure it twice.

Trait Implementations

impl Clone for MonitorResolverConfig

fn clone(&self) -> Self

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for MonitorResolverConfig

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

Formats the value using the given formatter.

impl Default for MonitorResolverConfig

fn default() -> Self

Returns the “default value” for a type.

impl<'de> Deserialize<'de> for MonitorResolverConfig

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl Serialize for MonitorResolverConfig

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.