Skip to main content

RungAnswer

Type Alias RungAnswer 

Source
pub type RungAnswer = Judgement;
Expand description

One rung’s answer — the Judgement core (RFC 13, v1.24; RFC 09 §5.1 pre-v1.24), carried directly: since v1.24 the ladder’s three shipped states are three of the core’s four poles, and this alias is the fold. The serde tags are byte-identical to what #214 shipped (established / not_established + reason / not_asked).

A rung’s judgement is over its own question (the rung’s fact), not over “is there a finding?” — which of its poles constitutes a finding is per-rung policy, and is_cause is where that policy lives. The rungs currently never answer Unobservable: an observation the ladder could not obtain degrades the rung to NotAsked and rides WhyReport::impairments instead.

A rung whose input was not fetched says NotAsked, never NotEstablished (RFC 09 §5.1 O4).

Aliased Type§

pub enum RungAnswer {
    Established,
    NotEstablished {
        reason: String,
    },
    NotAsked,
    Unobservable {
        reason: String,
    },
}

Variants§

§

Established

Established(yes): the question was put and the claim holds — positive evidence, conclusive.

§

NotEstablished

Established(no): the question was put and the claim conclusively does not hold — with the reason, which is where the honesty lives.

Fields

§reason: String
§

NotAsked

Unestablished: the question was not put — the input was not fetched, was not requested, or does not exist for this subject. Not asked is not answered no (RFC 09 §5.1 O4).

§

Unobservable

Unestablished: the question was put and the observation cannot carry the claim — a drop under a completeness claim, a window shorter than the claim’s span, or an ask that failed (RFC 09 §5.1 O6).

Fields

§reason: String