Encyclopedia Masses Masses Mass Genesis T10 Posting Rate Verdict
ARTICLE 5 claims 4 theorems 1 open
Masses Mass Genesis T10 Posting Rate Verdict
A proposed limit on how fast a ledger can change turns out to be true for one kind of count and false for another, and the framework has already chosen which one it means.
The posting rate verdict
A ledger, a discrete record of events, was being asked to obey a simple rule: its standing count changes by at most one unit from one tick to the next. The question was whether this rule, called one posting per tick, could be derived from the framework's settled eight-tick cycle. The answer, proved in the machine-checked library of formal theorems, is that the rule splits in two. It holds automatically for the two-valued readout the theory actually uses, and it fails for any count that faithfully registers every posting.
The two-valued readout is the occupancy indicator, which records only whether a given phase is occupied (1) or not (0). Since it has only two possible values, its change from tick to tick is always in {0, +1, -1}, with no premise needed. The theorem parityPhaseOccupation_onePostingPerTick proves this for every run, settled or not. The rule excludes nothing here, because the readout already only ever moves by one.
The faithful count is different. A faithful count readout, which registers every posting by increasing by one, rises by eight over the eight-tick cycle. The wrap from tick 7 back to tick 0 therefore moves it by seven units, not one. The theorem no_faithfulCountReadout_onePostingPerTick proves no such count can satisfy the one-per-tick bound on any run. The concrete balance readout of the canonical settled octave violates it by computation: |p 7 - p 0| = 4. Per step the balance moves at most one, so only the cyclic wrap fails.
The verdict is that the missing piece was never a rate law. It is the identification of the state space: the ledger's standing count in the mass line can only be the two-valued parity-phase occupation, under which the bound is automatic, or a faithful count, under which it is false. The framework made this identification for photon and settlement windows, but for matter windows it remains open, recorded as a single gap. What is positively derived is the exact shape the mass line consumes: each commit settlement window is the integer coboundary of a two-valued occupancy at unit posting rate, which re-derives the boolean difference settlement window for every carried posted window of every settled octave.
This settles a wall that was previously marked as assumed. The bound is not a new constraint; it is a consequence of the two-valued readout already in use. The real work left is identifying the matter-window occupancy, a model choice, not a rate derivation.
THEOREM parityPhaseOccupation_onePostingPerTick · IndisputableMonolith/Masses/MassGenesis/T10PostingRateVerdict.lean
/-- **The committed occupation satisfies the rate bound on every run, with no
premise.** Legality is never used: an indicator is two-valued, so its change
across any tick, including the cyclic wrap, is at most one. The theorem is
DERIVED in form and DEFINITIONAL in content. -/
theorem parityPhaseOccupation_onePostingPerTick (initial : LedgerState 3)
(schedule : ℕ → PostInstr 3) (phase : Fin 8) :
OnePostingPerTick (parityPhaseOccupation initial schedule phase) :=
onePostingPerTick_of_twoValued (a := 0) (b := 1) (by decide)
(parityPhaseOccupation_twoValued initial schedule phase)
THEOREM no_faithfulCountReadout_onePostingPerTick · IndisputableMonolith/Masses/MassGenesis/T10PostingRateVerdict.lean
/-- **No faithful standing count satisfies the cyclic rate bound.** Over seven
steps the count rises by seven, so the wrap tick alone moves seven units. This
is the sharp half of the verdict: the bound is not merely underived for
counts, it is false. -/
theorem no_faithfulCountReadout_onePostingPerTick (r : LedgerState 3 → ℤ)
(hf : FaithfulCountReadout r) (initial : LedgerState 3) (sched : ℕ → PostInstr 3) :
¬ OnePostingPerTick (fun t : Fin 8 => r (run initial sched t.val)) := by
intro hrate
have hstep : (r (run initial sched (7 : Fin 8).val) -
r (run initial sched ((7 : Fin 8) + 1).val)).natAbs ≤ 1 := hrate (7 : Fin 8)
have hwrapval : ((7 : Fin 8) + 1).val = 0 := by decide
have hv7 : (7 : Fin 8).val = 7 := by decide
rw [hwrapval, hv7] at hstep
rw [faithfulCountReadout_run r hf initial sched 7,
faithfulCountReadout_run r hf initial sched 0] at hstep
have hdiff : r initial + ((7 : ℕ) : ℤ) - (r initial + ((0 : ℕ) : ℤ)) = 7 := by
push_cast
ring
rw [hdiff] at hstep
exact (by decide : ¬ ((7 : ℤ).natAbs ≤ 1)) hstep
THEOREM canonicalOctave_axisBalance_violates_onePostingPerTick · IndisputableMonolith/Masses/MassGenesis/T10PostingRateVerdict.lean
/-- **The countermodel.** The library's canonical settled legal octave, read
by the standing balance of axis zero, violates the cyclic posting-rate bound:
the wrap tick compares a balance of `4` against a balance of `0`. So the bound
is false, not merely underived, for the integer "standing count" reading,
already on the one settled octave the library exhibits. -/
theorem canonicalOctave_axisBalance_violates_onePostingPerTick :
¬ OnePostingPerTick (axisBalanceOccupation q3ZeroLedger q3GrayPostingSchedule 0) := by
intro hrate
have hstep : (phiVec (run q3ZeroLedger q3GrayPostingSchedule (7 : Fin 8).val) 0 -
phiVec (run q3ZeroLedger q3GrayPostingSchedule ((7 : Fin 8) + 1).val) 0).natAbs ≤ 1 :=
hrate (7 : Fin 8)
have hwrapval : ((7 : Fin 8) + 1).val = 0 := by decide
have hv7 : (7 : Fin 8).val = 7 := by decide
rw [hwrapval, hv7, canonicalOctave_axisBalance_seven,
canonicalOctave_axisBalance_zero] at hstep
exact (by decide : ¬ ((4 : ℤ) - 0).natAbs ≤ 1) hstep
THEOREM commitSettlementWindow_is_unitRateIntCoboundary · IndisputableMonolith/Masses/MassGenesis/T10PostingRateVerdict.lean
/-- **The bridge in the mass line's own vocabulary.** Each commit settlement
window is the integer coboundary of a two-valued occupancy whose posting rate
is one, with no premise: the occupancy takes values in `{0, -1}`. This is the
shape `DoubleEntrySettledPattern` and `booleanWindow_of_onePostingPerTick`
consume. -/
theorem commitSettlementWindow_is_unitRateIntCoboundary (phase : Fin 8) :
∃ p : Fin 8 → ℤ,
(∀ t : Fin 8, commitSettlementWindow phase t = ((p t - p (t + 1) : ℤ) : ℂ)) ∧
OnePostingPerTick p := by
refine ⟨fun t => -(commitIntOccupation phase (t - 1)), fun t => ?_, ?_⟩
· have h1 : t + 1 - 1 = t := sub_eq_iff_eq_add.mpr rfl
show commitSettlementWindow phase t =
((-commitIntOccupation phase (t - 1) - -commitIntOccupation phase (t + 1 - 1) : ℤ) : ℂ)
unfold commitSettlementWindow
rw [← commitIntOccupation_cast phase t, ← commitIntOccupation_cast phase (t - 1),
h1]
push_cast
ring
· refine onePostingPerTick_of_twoValued (a := 0) (b := -1) (by decide) fun t => ?_
show -(commitIntOccupation phase (t - 1)) = 0 ∨
-(commitIntOccupation phase (t - 1)) = -1
unfold commitIntOccupation
by_cases h : t - 1 = phase <;> simp [h]
What this page does not claim
This does not derive a new rate law or a new physical constraint. This does not prove that the matter-window occupancy identification is forced. This does not close Phase B or Workstream B entirely. This does not claim the one-posting-per-tick bound applies to the faithful count readout.
Verify this page
Every tagged claim above names its theorem. To check one yourself rather than trust this page, elaborate the source module with Lean 4 and audit its axiom basis:
$ lake env lean IndisputableMonolith/Masses/MassGenesis/T10PostingRateVerdict.lean
expected axiom basis: [propext, Classical.choice, Quot.sound] (the Lean kernel's standard three; no RS-specific axioms)
A page whose claims cannot be reproduced this way does not ship. In production, every anchor links to the exact declaration in the public source release, and this block carries the build receipt for the page itself.
Derived articles
This page is generated by a question-recursion engine: the questions its answers raise become the next pages. The current agenda, with open targets marked red:
- What exactly is the matter-window identification that remains open?
- How does the two-valued occupancy readout relate to the physical photon support?
- What would a faithful count readout imply for the mass line if it were chosen?
- How does the posting rate verdict connect to the broader mass genesis derivation?
- What is the status of the posting-to-photon-support field in the settled raw mode source data?
MACHINE LAYER · GROUNDED CLAIM TABLE · CLICK TO EXPAND
THEOREM parityPhaseOccupation_onePostingPerTick · IndisputableMonolith/Masses/MassGenesis/T10PostingRateVerdict.lean
/-- **The committed occupation satisfies the rate bound on every run, with no premise.** Legality is never used: an indicator is two-valued, so its change across any tick, including the cyclic wrap, is at most one. The theorem is DERIVED in form and DEFINITIONAL in content. -/ theorem parityPhaseOccupation_onePostingPerTick (initial : LedgerState 3) (schedule : ℕ → PostInstr 3) (phase : Fin 8) : OnePostingPerTick (parityPhaseOccupation initial schedule phase) := onePostingPerTick_of_twoValued (a := 0) (b := 1) (by decide) (parityPhaseOccupation_twoValued initial schedule phase)The two-valued readout satisfies the one-posting-per-tick bound with no premise. parityPhaseOccupation_onePostingPerTick · IndisputableMonolith/Masses/MassGenesis/T10PostingRateVerdict.leanTHEOREM no_faithfulCountReadout_onePostingPerTick · IndisputableMonolith/Masses/MassGenesis/T10PostingRateVerdict.lean
/-- **No faithful standing count satisfies the cyclic rate bound.** Over seven steps the count rises by seven, so the wrap tick alone moves seven units. This is the sharp half of the verdict: the bound is not merely underived for counts, it is false. -/ theorem no_faithfulCountReadout_onePostingPerTick (r : LedgerState 3 → ℤ) (hf : FaithfulCountReadout r) (initial : LedgerState 3) (sched : ℕ → PostInstr 3) : ¬ OnePostingPerTick (fun t : Fin 8 => r (run initial sched t.val)) := by intro hrate have hstep : (r (run initial sched (7 : Fin 8).val) - r (run initial sched ((7 : Fin 8) + 1).val)).natAbs ≤ 1 := hrate (7 : Fin 8) have hwrapval : ((7 : Fin 8) + 1).val = 0 := by decide have hv7 : (7 : Fin 8).val = 7 := by decide rw [hwrapval, hv7] at hstep rw [faithfulCountReadout_run r hf initial sched 7, faithfulCountReadout_run r hf initial sched 0] at hstep have hdiff : r initial + ((7 : ℕ) : ℤ) - (r initial + ((0 : ℕ) : ℤ)) = 7 := by push_cast ring rw [hdiff] at hstep exact (by decide : ¬ ((7 : ℤ).natAbs ≤ 1)) hstepNo faithful count readout satisfies the one-posting-per-tick bound on any run of the eight-cycle. no_faithfulCountReadout_onePostingPerTick · IndisputableMonolith/Masses/MassGenesis/T10PostingRateVerdict.leanTHEOREM canonicalOctave_axisBalance_violates_onePostingPerTick · IndisputableMonolith/Masses/MassGenesis/T10PostingRateVerdict.lean
/-- **The countermodel.** The library's canonical settled legal octave, read by the standing balance of axis zero, violates the cyclic posting-rate bound: the wrap tick compares a balance of `4` against a balance of `0`. So the bound is false, not merely underived, for the integer "standing count" reading, already on the one settled octave the library exhibits. -/ theorem canonicalOctave_axisBalance_violates_onePostingPerTick : ¬ OnePostingPerTick (axisBalanceOccupation q3ZeroLedger q3GrayPostingSchedule 0) := by intro hrate have hstep : (phiVec (run q3ZeroLedger q3GrayPostingSchedule (7 : Fin 8).val) 0 - phiVec (run q3ZeroLedger q3GrayPostingSchedule ((7 : Fin 8) + 1).val) 0).natAbs ≤ 1 := hrate (7 : Fin 8) have hwrapval : ((7 : Fin 8) + 1).val = 0 := by decide have hv7 : (7 : Fin 8).val = 7 := by decide rw [hwrapval, hv7, canonicalOctave_axisBalance_seven, canonicalOctave_axisBalance_zero] at hstep exact (by decide : ¬ ((4 : ℤ) - 0).natAbs ≤ 1) hstepThe canonical balance readout violates the one-posting-per-tick bound at the cyclic wrap. canonicalOctave_axisBalance_violates_onePostingPerTick · IndisputableMonolith/Masses/MassGenesis/T10PostingRateVerdict.leanTHEOREM commitSettlementWindow_is_unitRateIntCoboundary · IndisputableMonolith/Masses/MassGenesis/T10PostingRateVerdict.lean
/-- **The bridge in the mass line's own vocabulary.** Each commit settlement window is the integer coboundary of a two-valued occupancy whose posting rate is one, with no premise: the occupancy takes values in `{0, -1}`. This is the shape `DoubleEntrySettledPattern` and `booleanWindow_of_onePostingPerTick` consume. -/ theorem commitSettlementWindow_is_unitRateIntCoboundary (phase : Fin 8) : ∃ p : Fin 8 → ℤ, (∀ t : Fin 8, commitSettlementWindow phase t = ((p t - p (t + 1) : ℤ) : ℂ)) ∧ OnePostingPerTick p := by refine ⟨fun t => -(commitIntOccupation phase (t - 1)), fun t => ?_, ?_⟩ · have h1 : t + 1 - 1 = t := sub_eq_iff_eq_add.mpr rfl show commitSettlementWindow phase t = ((-commitIntOccupation phase (t - 1) - -commitIntOccupation phase (t + 1 - 1) : ℤ) : ℂ) unfold commitSettlementWindow rw [← commitIntOccupation_cast phase t, ← commitIntOccupation_cast phase (t - 1), h1] push_cast ring · refine onePostingPerTick_of_twoValued (a := 0) (b := -1) (by decide) fun t => ?_ show -(commitIntOccupation phase (t - 1)) = 0 ∨ -(commitIntOccupation phase (t - 1)) = -1 unfold commitIntOccupation by_cases h : t - 1 = phase <;> simp [h]Each commit settlement window is the integer coboundary of a two-valued occupancy at unit posting rate. commitSettlementWindow_is_unitRateIntCoboundary · IndisputableMonolith/Masses/MassGenesis/T10PostingRateVerdict.lean- OPENThe matter-window identification of the occupancy readout remains open.