Encyclopedia Chemistry Chemistry Oxidation State From Config Dim Oxidation State Cost At Expected

ARTICLE 3 claims 1 theorem 2 models

Chemistry Oxidation State From Config Dim Oxidation State Cost At Expected

When a measured oxidation state equals the expected one, the framework's recognition cost drops to zero.

The cost of a match

In chemistry, an oxidation state is a bookkeeping number that tracks how many electrons an atom appears to have gained or lost when it forms compounds. Manganese can take many of them, from -3 to +7, but chemists often care about the most common ones. The Recognition Science framework models this with a ledger, a discrete record of recognition events, where the cost of recognizing a state is forced by a proved mathematical law.

The declaration oxidationStateCost_at_expected proves a small but precise fact: when the measured oxidation state equals the expected one, the cost of recognition is exactly zero. The cost function is J(x) = (x + 1/x)/2 - 1, applied to the ratio of measured to expected state. If the ratio is 1, the cost vanishes. This is a theorem in the framework's machine-checked library of formal theorems, with no unproved assumptions.

The same library also defines the canonical count of oxidation states for d-block transition metals as 2^3 - 1 = 7, a structural claim that matches the common range for elements like manganese, chromium, and iron. The zero-cost theorem is a consistency check: it says the framework's measure of deviation behaves as a measure should, giving no penalty when there is no deviation.

What the declaration does not claim is more important than what it does. It does not predict which specific oxidation states an element will exhibit, nor does it derive the count of 7 from first principles. The count is a definitional choice, a model, not a proved consequence. The theorem only establishes the behavior of the cost function at the point of agreement.

For a chemist, the practical meaning is simple: the framework's cost function is calibrated so that a perfect match costs nothing. This is the foundation on which any comparison of predicted versus observed states must rest, and it is the part that is rigorously proved.

THEOREM oxidationStateCost_at_expected · IndisputableMonolith/Chemistry/OxidationStateFromConfigDim.lean
theorem oxidationStateCost_at_expected (s : ℝ) (h : s ≠ 0) :
    oxidationStateCost s s = 0 := by
  unfold oxidationStateCost; rw [div_self h]; exact Cost.Jcost_unit0
MODEL oxidationStateCost · IndisputableMonolith/Chemistry/OxidationStateFromConfigDim.lean
/-- J-cost on oxidation state ratio: deviation from the expected state. -/
def oxidationStateCost (measured expected : ℝ) : ℝ :=
  Cost.Jcost (measured / expected)
MODEL canonicalOxidationStateCount · IndisputableMonolith/Chemistry/OxidationStateFromConfigDim.lean
/-- Count Law at D = 3: 2^3 - 1 = 7 canonical oxidation states. -/
def canonicalOxidationStateCount : ℕ := 2 ^ 3 - 1

What this page does not claim

The theorem does not predict which oxidation states an element will exhibit. The count of seven is a definitional choice, not a proved consequence. The framework does not derive the existence of oxidation states from physics.

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/Chemistry/OxidationStateFromConfigDim.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