Enum SeveritySource 

pub enum SeveritySource {
    AuthorJudgment {
        rationale: String,
    },
    DerivedFromEvidence {
        rationale: String,
    },
}

How the rule arrived at its severity rank.

Today every rule reports AuthorJudgment because the diagnoser has no visibility into per-customer blast radius — it can only see one transaction at a time. The variant exists so the provenance is explicit in every rendered prompt and report; a reader cannot mistake a hand-assigned rank for a measured impact.

DerivedFromEvidence is reserved for a future variant that would derive severity from evidence values (e.g. RetryAfterSecs > 60 upgrading rate-limit to High, or a sustained ConnectionTimeout count upgrading to Critical). When that variant gets used, the rendered label will say “derived from evidence” instead of “author judgment” — no caller code needs to change.

Variants

AuthorJudgment

Fields

rationale: String

DerivedFromEvidence

Fields

rationale: String

Implementations

impl SeveritySource

pub fn rationale(&self) -> &str

The human-readable rationale, regardless of variant.

pub fn label(&self) -> &'static str

Short label distinguishing the two provenance kinds; rendered next to the severity rank in every output.

Trait Implementations

impl Clone for SeveritySource

fn clone(&self) -> SeveritySource

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for SeveritySource

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

Formats the value using the given formatter.

impl Serialize for SeveritySource

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

where __S: Serializer,

Serialize this value into the given Serde serializer.