Why Three Fermion Generations

1. Setting

The existence of exactly three fermion generations is an input in the Standard Model. RS treats it as a count forced by the Q3 cube and the eight-tick cycle. The same D=3 structure that gives the recognition octave supplies three family slots. This page is empirical because LEP and cosmology strongly constrain any additional light chiral generation.

2. Equations

(E1)

$$ N_{\mathrm{gen}}=3 $$

RS generation count.

(E2)

$$ 2^D=8,\qquad D=3 $$

The eight-tick dimension identity feeding the family count.

3. Prediction or structural target

• Fermion generations: predicted 3 (count); empirical 3. Source: LEP Z-width and collider data

No fourth light generation is seen; LEP Z-width constraints are the sharpest classic bound.

4. Formal anchor

The primary anchor is Physics.ThreeGenerations..

5. What is inside the Lean module

Key theorems:

• bits_bijection
• three_generations
• dimensions_from_log
• mass_from_phi_ladder
• why_exactly_three
• no_fourth_generation
• ckm_from_phase_overlap
• neutrino_generations_match

Key definitions:

• tickToBits
• bitsToTick
• Generation
• dimensionsFromTicks
• dimensionToGeneration
• massRatio
• massHierarchyPattern
• CKMElement

6. Derivation chain

• Physics.ThreeGenerations - Three generations module
• Physics.ParticlePhysicsGenerationsFromRS - Generations from RS

7. Falsifier

Discovery of a fourth light chiral fermion generation with Standard-Model quantum numbers refutes the Q3 family-count prediction.

8. Where this derivation stops

Below this page the chain reduces to the RS forcing sequence: J-cost uniqueness, phi forcing, the eight-tick cycle, and the D=3 recognition substrate. If any upstream theorem changes, this page must be versioned rather than patched silently. The published URL is stable, but the version field is the contract.

9. Reading note

The minimal way to audit this page is to open the first Lean anchor and then walk the supporting declarations listed above. If the primary theorem is a module-level anchor, the key theorems section names the internal declarations that carry the mathematical load. This keeps the public derivation readable without severing it from the proof object.

10. Audit path

To audit three-generations, start with the primary Lean anchor Physics.ThreeGenerations. Then inspect the theorem names listed in the module-content section. The page is intentionally built so the public explanation is not a substitute for the proof object; it is a map into it. The mathematical dependency is the same in every case: reciprocal cost fixes J, J fixes the phi-ladder, the eight-tick cycle fixes the recognition clock, and the domain theorem listed above supplies the last step. If that last step is empirical, the falsifier section names what observation would break it. If that last step is formal, a Lean-checkable counterexample is the relevant failure mode.

11. Why this belongs in the derivations corpus

The corpus is organized around load-bearing consequences, not around file names. This entry is included because Physics.ThreeGenerations contributes a reusable theorem or definitional bridge that other pages can cite. Keeping the page public gives readers a stable URL, a JSON record, and a direct path into the Lean theorem page. If the entry becomes redundant with a stronger derivation later, the current slug should be retired rather than silently rewritten; the replacement should absorb its anchors and preserve the audit history.