Learning.IT.hasCondDistrib_feedback_zero🔗

Learning.IT.hasCondDistrib_feedback_zero.{u_1, u_2} {𝓐 : Type u_1}
  {𝓨 : Type u_2} {m𝓐 : MeasurableSpace 𝓐} {m𝓨 : MeasurableSpace 𝓨}
  (alg : Algorithm 𝓐 𝓨) (env : Environment 𝓐 𝓨) :
  ProbabilityTheory.HasCondDistrib (feedback 0) (action 0)
    (Environment.ν0 env) (trajMeasure alg env)
Learning.IT.hasCondDistrib_feedback_zero.{u_1,
    u_2}
  {𝓐 : Type u_1} {𝓨 : Type u_2}
  {m𝓐 : MeasurableSpace 𝓐}
  {m𝓨 : MeasurableSpace 𝓨}
  (alg : Algorithm 𝓐 𝓨)
  (env : Environment 𝓐 𝓨) :
  ProbabilityTheory.HasCondDistrib
    (feedback 0) (action 0)
    (Environment.ν0 env)
    (trajMeasure alg env)

lemma hasCondDistrib_feedback_zero (alg : Algorithm 𝓐 𝓨) (env : Environment 𝓐 𝓨) :
    HasCondDistrib (feedback 0) (action 0) env.ν0 (trajMeasure alg env)

by
  have h_step := (hasLaw_step_zero alg env).map_eq
  have h_action := (hasLaw_action_zero alg env).map_eq
  exact ⟨by fun_prop, by rwa [h_action]⟩

Meaning last changed in v4.34.0-rc2-1-g439785b (2026-08-23), the 4th recorded change.

Self-contained, with its dependencies inlined and proofs replaced by sorry: download the raw file · open it in the Lean web editor.

Dependency graph

Audit surface: 6 project declarations, 27 external constants

✓ Proved: no sorry anywhere in its closure

This is the tool's own reading of one build's recorded axioms, and it is not robust against an author who wants it to pass. Checking meant to be relied on should go through Comparator, which replays the proof through the kernel from an export against an explicit list of permitted axioms.