Chemistry Oxidation State From Config Dim Oxidation State Cert

The oxidation state certificate

An oxidation state is the charge an atom would have if all its bonds were purely ionic, a bookkeeping number chemists use to track electron transfer. Transition metals are famous for taking on many of these states: manganese, for instance, is found in formal states from -3 to +7, though only a handful appear in common compounds. The Recognition Science framework's ledger, a discrete record of events, models this variety with a counting rule. Its declaration OxidationStateCert packages four machine-checked facts about that rule, and the central one is a count: the canonical number of oxidation states for a d-block transition metal is 2^3 - 1, which is 7.

The number 7 comes from a structural claim about three binary axes, each offering two choices: charge positive or negative, d-electron count above or below half-fill, and ligand-field strength above or below a reference. The framework's Count Law at dimension 3 says these three axes yield 2^3 possibilities, and subtracting 1 for the neutral state leaves 7. The declaration also packages three supporting facts about the framework's cost function, which measures deviation from an expected oxidation state: the cost is zero when the measured state equals the expected one, and the cost is never negative for positive inputs. All four statements are proved in the machine-checked library of formal theorems, with no axioms beyond the standard logical ones.

The certificate is a proof of arithmetic and of properties of a defined cost function, not a proof about real chemistry. The prediction that d-block elements have 7 common oxidation states is a hypothesis with a named falsifier: any d-block element with a confirmed, stable oxidation state count different from 7 ± 2 in standard inorganic chemistry conditions would refute it. The framework's own library does not claim to have verified this against all measured data; the match with manganese's common states and the IUPAC golden-7 list is an empirical check, not a theorem.

What the certificate does give a reader is a precise, checkable statement of what the framework expects, and a clear target for testing. It turns a vague observation about transition metal variety into a specific number, 7, with a defined counting rule and a falsifier. That is a useful step: it makes the framework's claim about chemistry concrete enough to be wrong, which is exactly what a scientific prediction should be.

theorem canonicalOxidationStateCount_eq : canonicalOxidationStateCount = 7 := by
  unfold canonicalOxidationStateCount; norm_num

theorem oxidationStateCost_at_expected (s : ℝ) (h : s ≠ 0) :
    oxidationStateCost s s = 0 := by
  unfold oxidationStateCost; rw [div_self h]; exact Cost.Jcost_unit0

theorem oxidationStateCost_nonneg (m e : ℝ) (hm : 0 < m) (he : 0 < e) :
    0 ≤ oxidationStateCost m e := by
  unfold oxidationStateCost; exact Cost.Jcost_nonneg (div_pos hm he)

structure OxidationStateCert where
  count_eq : canonicalOxidationStateCount = 7
  count_pos : 0 < canonicalOxidationStateCount
  cost_at_expected : ∀ s : ℝ, s ≠ 0 → oxidationStateCost s s = 0
  cost_nonneg : ∀ m e : ℝ, 0 < m → 0 < e → 0 ≤ oxidationStateCost m e

What this page does not claim

The certificate does not prove that any real element has exactly 7 oxidation states. The certificate does not derive the value 7 from first principles of physics. The certificate does not claim the framework's cost function is the only possible measure of oxidation state deviation.

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: