Learning.IT.hasLaw_action_zero
No docstring.
Learning.IT.hasLaw_action_zero.{u_1, u_2} {๐ : Type u_1} {๐จ : Type u_2} {m๐ : MeasurableSpace ๐} {m๐จ : MeasurableSpace ๐จ} (alg : Algorithm ๐ ๐จ) (env : Environment ๐ ๐จ) : ProbabilityTheory.HasLaw (action 0) (Algorithm.p0 alg) (trajMeasure alg env)Learning.IT.hasLaw_action_zero.{u_1, u_2} {๐ : Type u_1} {๐จ : Type u_2} {m๐ : MeasurableSpace ๐} {m๐จ : MeasurableSpace ๐จ} (alg : Algorithm ๐ ๐จ) (env : Environment ๐ ๐จ) : ProbabilityTheory.HasLaw (action 0) (Algorithm.p0 alg) (trajMeasure alg env)
Code
lemma hasLaw_action_zero (alg : Algorithm ๐ ๐จ) (env : Environment ๐ ๐จ) :
HasLaw (action 0) alg.p0 (trajMeasure alg env) where
map_eqProof
by
rw [โ fst_comp_step, โ Measure.map_map (by fun_prop) (by fun_prop),
(hasLaw_step_zero alg env).map_eq, โ Measure.fst, Measure.fst_compProd]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: 5 project declarations, 26 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.