Encyclopedia Foundation Foundation Pair Kernel Onsite Exclusion Exact Jcost As General Ledger Cost Onsit

ARTICLE 4 claims 3 theorems 1 hypothesis

Foundation Pair Kernel Onsite Exclusion Exact Jcost As General Ledger Cost Onsit

A machine-checked theorem shows that the framework's fundamental cost function has no absolute per-site term, while a separate hypothesis is needed to rule out non-local interactions.

The zero on-site term

The declaration exactJCostAsGeneralLedgerCost_onsite_zero is a consistency check inside the Recognition Science framework. It re-expresses the framework's exact cost function, exactJCostAction, as a general ledger cost and then proves that the per-site term in that re-expression is identically zero. In plain terms: the cost of a configuration depends only on the differences between neighboring sites, never on the absolute value at any single site. The proof is a theorem in the machine-checked library of formal theorems, with no gaps and no extra assumptions beyond the standard ones.

The interesting part is what this theorem does not do. The general ledger cost structure allows an arbitrary per-site term, and the framework's own forcing theorem, l1_onsite_forced_constant, shows that a global shift-invariance hypothesis forces that term to be constant. The re-expression theorem is a sanity check that the exact cost function already sits in the zero slice of that structure. It does not by itself prove that no on-site term is writable; that requires the shift-invariance hypothesis, which is a named assumption, not a derived consequence. The zero on-site term is a property of the definition, not a result of the forcing chain.

The framework is careful to separate what is forced from what is assumed. The shift-invariance hypothesis is not derived from the framework's founding principle; it is a stated premise. The theorem l1_onsite_forced_constant then shows that, given that premise, the on-site term must be constant. The re-expression theorem merely confirms that the exact cost function already satisfies that conclusion trivially, because its on-site term was defined to be zero. This is a consistency anchor, not new content.

What the framework does not claim here is equally precise. The theorem does not rule out non-local interactions. A separate mean-field example in the same module is shift-invariant and admissible, yet it couples every pair of sites, including maximally separated ones. Excluding that kind of all-to-all coupling would require a separate locality hypothesis, which is not part of this theorem and is not yet anywhere in the framework's Lean surface. The on-site exclusion is real, but it is only one branch of a larger question.

THEOREM exactJCostAsGeneralLedgerCost_onsite_zero · IndisputableMonolith/Foundation/PairKernelOnsiteExclusion.lean
exactJCostAsGeneralLedgerCost_onsite_zero · IndisputableMonolith/Foundation/PairKernelOnsiteExclusion.lean:269
/-- Sanity corollary: applying the general forcing theorem to the `exactJCostAction`
    slice recovers `k = 0` (the onsite term was already zero, not merely forced to be
    some unknown constant). Consistency check, not new content. -/
theorem exactJCostAsGeneralLedgerCost_onsite_zero {n : ℕ} (G : WeightedLedgerGraph n)
    (_hn : 0 < n) :
    ∃ k : ℝ, k = 0 ∧ ∀ u : ℝ, (exactJCostAsGeneralLedgerCost G).onsite u = k := by
  refine ⟨0, rfl, fun u => rfl⟩
THEOREM l1_onsite_forced_constant · IndisputableMonolith/Foundation/PairKernelOnsiteExclusion.lean
/-- **L1-FORCE (`l1_onsite_forced_constant`).** Under `ShiftInvariant` and `n ≥ 1`, the
    onsite part of an admissible `GeneralLedgerCost` is forced to be a constant
    function of its real argument — i.e. no on-site mass/absolute term is writable.

    Non-vacuity: this is FALSE without `ShiftInvariant`. Take `onsite u = u²` (the exact
    shape of the L2 decoy `+m² Σ φᵢ²`, which the numeric harness correctly flagged
    Yukawa): `yukawaOnsiteDecoy_not_shift_invariant` below shows this instance fails
    the hypothesis, so deleting `hR1` lets it stand as a live counterexample to the
    conclusion. -/
theorem l1_onsite_forced_constant {n : ℕ} (C : GeneralLedgerCost n) (hn : 0 < n)
    (hR1 : ShiftInvariant C) :
    ∃ k : ℝ, ∀ u : ℝ, C.onsite u = k := by
  refine ⟨C.onsite 0, fun u => ?_⟩
  have honsite := (shiftInvariant_iff_onsite_sum C).mp hR1 (fun _ => (0 : ℝ)) u
  simp only [zero_add] at honsite
  have hL : (∑ _i : Fin n, C.onsite u) = (n : ℝ) * C.onsite u := by
    rw [Finset.sum_const, Finset.card_univ, Fintype.card_fin, nsmul_eq_mul]
  have hR : (∑ _i : Fin n, C.onsite 0) = (n : ℝ) * C.onsite 0 := by
    rw [Finset.sum_const, Finset.card_univ, Fintype.card_fin, nsmul_eq_mul]
  rw [hL, hR] at honsite
  have hnr : (n : ℝ) ≠ 0 := Nat.cast_ne_zero.mpr hn.ne'
  exact mul_left_cancel₀ hnr honsite
HYPOTHESIS ShiftInvariant · IndisputableMonolith/Foundation/PairKernelOnsiteExclusion.lean
/-- **R1 (global shift invariance).** Adding an arbitrary constant to every log-potential
    leaves the total ledger cost unchanged. This is the candidate double-entry gauge
    symmetry under investigation: absolute account *levels* carry no cost, only the
    *relations* between them do. It is stated here as a named hypothesis, not derived. -/
def ShiftInvariant {n : ℕ} (C : GeneralLedgerCost n) : Prop :=
  ∀ (ε : LogPotential n) (c : ℝ), C.eval (fun i => ε i + c) = C.eval ε
THEOREM meanFieldLedgerCost_shift_invariant · meanFieldWeight_full_support · IndisputableMonolith/Foundation/PairKernelOnsiteExclusion.lean
meanFieldLedgerCost_shift_invariant · IndisputableMonolith/Foundation/PairKernelOnsiteExclusion.lean:228
/-- **The honest negative.** The mean-field ledger cost is shift-invariant (it has no
    onsite term, so `ShiftInvariant` holds for the shape reason isolated in
    `shiftInvariant_iff_onsite_sum`, not because locality was ever assumed), yet its
    weight graph is non-local (`meanFieldWeight_full_support`). So `L1`
    (`l1_onsite_forced_constant`), even fully proved and even fully forced from
    first principles, does NOT by itself exclude a screened kernel: excluding the
    mean-field / all-to-all route needs a SEPARATE locality hypothesis `L0`
    (finite-range weights), which is not addressed in this module and, per the panel
    audit, is currently nowhere in the Lean surface. This is the scoped, honest residual
    of Door 2 / L1-hard: on-site exclusion is real and forced (conditional on
    `ShiftInvariant`), but on-site exclusion alone is not the whole story. -/
theorem meanFieldLedgerCost_shift_invariant (n : ℕ) :
    ShiftInvariant (meanFieldLedgerCost n) := by
  rw [shiftInvariant_iff_onsite_sum]
  intro ε c
  simp [meanFieldLedgerCost]
/-- The mean-field weight has full support: every pair, including every distinct pair,
    is coupled with nonzero weight. This is the formal shape of "not finite-range" — a
    genuinely local weight graph must vanish outside a bounded neighborhood as `n`
    grows, and this one never does. -/
theorem meanFieldWeight_full_support (n : ℕ) (i j : Fin n) :
    (meanFieldWeight n).weight i j ≠ 0 := by
  simp [meanFieldWeight]

What this page does not claim

This theorem does not prove that shift invariance is a derived consequence of the framework's founding principle. This theorem does not exclude non-local, all-to-all interactions; that requires a separate locality hypothesis. This theorem does not establish any new content about the exact cost function beyond confirming its on-site term is zero by definition.

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/Foundation/PairKernelOnsiteExclusion.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:

MACHINE LAYER · GROUNDED CLAIM TABLE · CLICK TO EXPAND