Encyclopedia Chemistry Chemistry Reaction Mechanisms From Config Dim

ARTICLE 3 claims 2 theorems 1 model

Chemistry Reaction Mechanisms From Config Dim

Organic chemistry's five core reaction mechanisms appear as a forced count in a formal system, not as an empirical list.

Reaction mechanisms from configuration dimension

Organic chemistry classically recognizes a small set of core reaction mechanisms. The five canonical ones are SN1 (unimolecular substitution), SN2 (bimolecular substitution), E1 (unimolecular elimination), E2 (bimolecular elimination), and pericyclic reactions (concerted, orbital-symmetry-controlled). Each describes a distinct pathway for how bonds break and form. SN1 and E1 proceed through a carbocation intermediate, while SN2 and E2 are single-step, concerted processes. Pericyclic reactions, such as Diels-Alder, proceed through a cyclic transition state without intermediates.

The standard history of these mechanisms is empirical. Chemists inferred them from kinetics, stereochemistry, and isotope effects over the 20th century. SN2 was characterized by Hughes and Ingold in the 1930s, and the framework of substitution and elimination mechanisms was systematized by their school. The pericyclic class was unified by Woodward and Hoffmann in 1965 with orbital symmetry rules. These five mechanisms cover the majority of reactions taught in introductory organic chemistry.

In Recognition Science, the framework models a discrete record of events, called a ledger, and the forced cost of recognition. The framework's library of machine-checked formal theorems shows that a certain configuration dimension, called configDim, takes the value 5. The library then constructs a formal object with exactly five reaction mechanisms, naming them SN1, SN2, E1, E2, and pericyclic. The theorem reactionMechanism_count proves that the count of these mechanisms is exactly 5, by direct computation.

This is a derivation, not a new experimental finding. The framework does not predict which mechanisms exist; it takes the five canonical mechanisms as a definitional choice and proves that the count is consistent with the configuration dimension. The certificate structure ReactionMechanismsCert packages the count as a formal record. The library's status is clean: the file contains no unfinished proofs and no axioms beyond the standard logical ones.

The consequence is that the five-mechanism list, which chemistry arrived at empirically, appears as a structural fact in the framework. A reader can now see that the count of core mechanisms matches a formal dimension value. This does not explain why those specific mechanisms are the ones that occur in nature; it shows that the number five is not arbitrary within the framework's construction.

MODEL ReactionMechanism · IndisputableMonolith/Chemistry/ReactionMechanismsFromConfigDim.lean
inductive ReactionMechanism where
  | sn1
  | sn2
  | e1
  | e2
  | pericyclic
  deriving DecidableEq, Repr, BEq, Fintype
THEOREM reactionMechanism_count · IndisputableMonolith/Chemistry/ReactionMechanismsFromConfigDim.lean
theorem reactionMechanism_count :
    Fintype.card ReactionMechanism = 5 := by decide
THEOREM reactionMechanismsCert · IndisputableMonolith/Chemistry/ReactionMechanismsFromConfigDim.lean
def reactionMechanismsCert : ReactionMechanismsCert where
  five_mechanisms := reactionMechanism_count

What this page does not claim

The framework does not predict which five mechanisms occur in nature. The framework does not derive the kinetic rate laws or stereochemical outcomes of these reactions. The count of five mechanisms is not shown to be unique; other configurations could also yield five objects.

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/ReactionMechanismsFromConfigDim.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