Foundation Pair Kernel Physical Posting Semantics S11 Source Magnitude Does Not

The boundary of charge

In physics, the magnitude of a source, such as the strength of a field or the amount of something, is often assumed to determine the charge it carries. The Recognition Science framework, which builds physical structure from a discrete record of events, examines this assumption through a machine-checked library of formal theorems. Its declaration sourceMagnitude establishes a precise boundary: a source's magnitude alone does not force a specific electromagnetic charge attachment.

The theorem proves that there exists a realized posting pair, an event in the framework's ledger of discrete events, where the source magnitude is constant but the electromagnetic charge attachment is not equal to it. In plainer terms, two events can have the same source strength yet carry different charges. This is a countermodel, a concrete example showing that the relationship between source magnitude and charge is not automatic.

What the declaration does not claim is equally important. It does not say that charge is arbitrary or unrelated to the source. The framework proves that when a field carries the native action quantum, the source magnitude takes the value phi to the fifth power, a specific constant. The boundary is narrower: without additional structure, such as the field carrying the action, source magnitude alone is insufficient to determine charge.

This result matters because it separates what the framework forces from what remains open. It shows that the link between source and charge requires an explicit mechanism, not just a magnitude. The theorem is a precise statement about the limits of inference in this model, and it invites a reader to see that in the framework, physical properties are not free-floating but are tied to specific structural conditions.

/-- A source assignment alone does not identify electromagnetic charge: the
same realized event admits distinct explicit charge readouts. -/
theorem sourceMagnitude_does_not_force_electromagneticCharge :
    ∃ event : PostingPair3 3,
      event ∈ realizedPrimitivePostingPairs3 3 ∧
        ¬ ElectromagneticChargeAttachment3
          (fun _ : PostingPair3 3 => 1)
          (fun _ : PostingPair3 3 => 2) := by
  obtain ⟨event, hevent, _hcert⟩ :=
    canonicalGeneratorSource_consumer_exists
      (N := 3) (by norm_num) (Equiv.refl (Fin 3))
  refine ⟨event, hevent, ?_⟩
  intro hcharge
  have := hcharge event hevent
  norm_num at this

/-- A source assignment alone does not identify electromagnetic charge: the
same realized event admits distinct explicit charge readouts. -/
theorem sourceMagnitude_does_not_force_electromagneticCharge :
    ∃ event : PostingPair3 3,
      event ∈ realizedPrimitivePostingPairs3 3 ∧
        ¬ ElectromagneticChargeAttachment3
          (fun _ : PostingPair3 3 => 1)
          (fun _ : PostingPair3 3 => 2) := by
  obtain ⟨event, hevent, _hcert⟩ :=
    canonicalGeneratorSource_consumer_exists
      (N := 3) (by norm_num) (Equiv.refl (Fin 3))
  refine ⟨event, hevent, ?_⟩
  intro hcharge
  have := hcharge event hevent
  norm_num at this

What this page does not claim

This does not claim that electromagnetic charge is arbitrary or unrelated to source properties in general. This does not claim that source magnitude never determines charge when additional structure, such as a field carrying the native action, is present.

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/PairKernelPhysicalPostingSemanticsS11.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: