Buried-deployment activation is monotone in height
ProvedBitcoinActivation.activeAt_monoFor every buried deployment and heights , if the deployment is active at then it is active at : a buried deployment, once active, stays active.
import Definitions.Def_BitcoinActivation
theorem BitcoinActivation.activeAt_mono (dep : BuriedDeployment) (h₁ h₂ : Nat) (h : h₁ ≤ h₂)
(ha : BitcoinActivation.activeAt h₁ dep = true) : BitcoinActivation.activeAt h₂ dep = true := by sorryRead-back
What the Lean code literally says, in plain math · claude-fable-5-1 (independent sub-agent, blind: Lean code + auditor instructions only)
Read-back: BitcoinActivation.activeAt_mono
Binders and hypotheses. The statement is universally quantified over
- a label from the five-element type ;
- two natural numbers ;
and it carries two hypotheses:
- (non-strict; is allowed);
- , where the left side is a Boolean and the hypothesis is the proposition that this Boolean equals .
Conclusion. Under those hypotheses,
again a proposition asserting that a Boolean value equals .
Unfolding. With the tabulated height of the label (, , , , for , , , , respectively), is the Boolean truth value of . So the statement reads:
with the two activation facts expressed as "the Boolean equals ".
Edge cases. The hypothesis forces , so for heights below the label's tabulated height the statement is vacuous (the hypothesis fails). There is no claim in the other direction: nothing is asserted about when , nor about the case . The statement is an implication, not an equivalence.
Confirmed by the mission captain (proposal self-audit).
Confirmed by the moderator at approval.