Encyclopedia Astrophysics Astrophysics Stellar Evolution Phases From Config Dim Stellar Phase

ARTICLE 3 claims 3 theorems

Astrophysics Stellar Evolution Phases From Config Dim Stellar Phase

A machine-checked list names the five classic stages of a sun-like star, but does not itself describe the physics that moves a star between them.

The five phases

Stellar evolution is the sequence of changes a star undergoes over its lifetime. For a star like the Sun, astronomers classically recognize five main phases: protostar, main sequence, red giant branch, asymptotic giant branch, and white dwarf (or supernova remnant for a more massive star). The recognition framework, which treats reality as maintaining a discrete record of events, encodes this familiar list as a formal object named StellarPhase. The declaration is an inductive type, a way of saying there are exactly five named possibilities and nothing else.

The machine-checked library of formal theorems proves a simple fact about this list: the number of phases is exactly five. The theorem stellarPhase_count states that the cardinality of StellarPhase equals 5, and the proof is by direct computation. A certificate structure packages this count as a reusable fact. The entire file contains zero unproved assumptions and zero axioms, meaning the five-phase count is fully verified within the framework's logic.

What the declaration does not do is more interesting. StellarPhase is only a list of names. It does not define the physical conditions of each phase, the temperatures or luminosities, the nuclear reactions that power a main-sequence star, or the instabilities that drive a red giant up the branch. It does not state that a star must pass through these phases in order, nor how long each phase lasts. The framework here contributes a count, not a theory of stellar structure or evolution.

In Recognition Science, the number five connects to a deeper structural claim: the framework derives that recognition events organize into an eight-tick cycle and that three spatial dimensions are forced. The five stellar phases are presented as an instance of a configuration dimension, a count that the framework's broader mathematics predicts. But the astrophysical content, the actual physics of why a star leaves the main sequence, is external to this declaration. The file establishes a labeled set of five phases and proves the set has five elements. That is the whole of its claim.

The practical value is organizational. A formal list with a verified count gives a shared vocabulary for later work: any theorem about stellar evolution can now refer to protostar or whiteDwarfOrRemnant as a named, machine-checked object. The count being proven means no future proof can silently add a sixth phase or drop a fifth. The physics of the phases remains a separate question, one this declaration does not touch.

THEOREM StellarPhase · IndisputableMonolith/Astrophysics/StellarEvolutionPhasesFromConfigDim.lean
inductive StellarPhase where
  | protostar
  | mainSequence
  | redGiantBranch
  | asymptoticGiantBranch
  | whiteDwarfOrRemnant
  deriving DecidableEq, Repr, BEq, Fintype
THEOREM stellarPhase_count · IndisputableMonolith/Astrophysics/StellarEvolutionPhasesFromConfigDim.lean
theorem stellarPhase_count : Fintype.card StellarPhase = 5 := by decide
THEOREM StellarEvolutionCert · IndisputableMonolith/Astrophysics/StellarEvolutionPhasesFromConfigDim.lean
structure StellarEvolutionCert where
  five_phases : Fintype.card StellarPhase = 5

What this page does not claim

The declaration does not define any physical property of the phases, such as temperature, luminosity, or nuclear processes. The declaration does not state that a star must pass through the phases in order, nor does it give timescales for any phase. The five-phase count is not derived from stellar physics within this file; it is presented as a list with a verified cardinality.

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/Astrophysics/StellarEvolutionPhasesFromConfigDim.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