LeanMachineLearning

Learning.IT.isAlgEnvSeq_trajMeasureπŸ”—

Lemma

No docstring.

πŸ”—theorem
Learning.IT.isAlgEnvSeq_trajMeasure.{u_1, u_2} {𝓐 : Type u_1}
  {𝓨 : Type u_2} {m𝓐 : MeasurableSpace 𝓐} {m𝓨 : MeasurableSpace 𝓨}
  (alg : Algorithm 𝓐 𝓨) (env : Environment 𝓐 𝓨) :
  IsAlgEnvSeq action feedback alg env (trajMeasure alg env)
Learning.IT.isAlgEnvSeq_trajMeasure.{u_1,
    u_2}
  {𝓐 : Type u_1} {𝓨 : Type u_2}
  {m𝓐 : MeasurableSpace 𝓐}
  {m𝓨 : MeasurableSpace 𝓨}
  (alg : Algorithm 𝓐 𝓨)
  (env : Environment 𝓐 𝓨) :
  IsAlgEnvSeq action feedback alg env
    (trajMeasure alg env)

Code

lemma isAlgEnvSeq_trajMeasure (alg : Algorithm 𝓐 𝓨) (env : Environment 𝓐 𝓨) :
    IsAlgEnvSeq action feedback alg env (trajMeasure alg env) where
  hasLaw_action_zero
Proof
hasLaw_action_zero alg env
  hasCondDistrib_feedback_zero := hasCondDistrib_feedback_zero alg env
  hasCondDistrib_action n := hasCondDistrib_action alg env n
  hasCondDistrib_feedback n := hasCondDistrib_feedback alg env n

Actions: Source Β· Open Issue

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: 14 project declarations, 49 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.