Encyclopedia Astrophysics Astrophysics Galaxy Morphology Types From Config Dim Galaxy Morphology Cert

ARTICLE 3 claims 2 theorems 1 model

Astrophysics Galaxy Morphology Types From Config Dim Galaxy Morphology Cert

A machine-checked certificate counts the five classic galaxy shapes and ties them to a deeper counting principle, without claiming any galaxy obeys the scheme.

The morphology certificate

Astronomers sort galaxies by visual appearance into a handful of broad classes. The Hubble sequence, introduced by Edwin Hubble in 1926, runs from elliptical galaxies through lenticular and spiral forms to barred spirals, with irregular galaxies as the catch-all remainder. The scheme is descriptive: a galaxy is what it looks like through the telescope, not what a theory says it must be.

Within the Recognition Science framework, a machine-checked library of formal theorems encodes this familiar five-type scheme as a small inductive type named GalaxyMorphology. The type has exactly five constructors: elliptical, lenticular, spiral, barredSpiral, and irregular. A theorem in the library, galaxyMorphology_count, proves by direct computation that the number of distinct values of this type is five. The proof is a finite case check, so it carries no hidden assumptions beyond the standard logical axioms of the ambient type theory.

The declaration GalaxyMorphologyCert packages that counting result as a certificate: a structure whose single field five_types asserts the cardinality statement. A definition galaxyMorphologyCert supplies the proof term, so the certificate is inhabited, meaning the statement is established. In plain terms, the framework has a checked object that says the five canonical morphology types form a set of size five.

In Recognition Science, this count is not an arbitrary astronomical convention. The framework derives the number three for spatial dimensions from a forcing chain rooted in a cost function, and it treats other structural counts as expressions of the same underlying ledger of recognition events. Here the count five for galaxy morphology types is presented as an instance of that pattern, tied to the configurational dimension D = 5. The certificate records the match between the astronomical taxonomy and the framework's counting scheme.

The certificate does not claim that real galaxies fall into exactly five clean bins. It does not assert that the Hubble sequence is physically fundamental, that the five types are exhaustive in nature, or that any particular galaxy has been classified correctly. It only establishes that the framework's formal object for galaxy morphology has five distinct values, matching the classical taxonomy's five canonical classes. The astronomy remains descriptive; the certificate is a statement about the formal encoding.

THEOREM galaxyMorphology_count · IndisputableMonolith/Astrophysics/GalaxyMorphologyTypesFromConfigDim.lean
theorem galaxyMorphology_count :
    Fintype.card GalaxyMorphology = 5 := by decide
MODEL GalaxyMorphologyCert · IndisputableMonolith/Astrophysics/GalaxyMorphologyTypesFromConfigDim.lean
structure GalaxyMorphologyCert where
  five_types : Fintype.card GalaxyMorphology = 5
THEOREM galaxyMorphologyCert · IndisputableMonolith/Astrophysics/GalaxyMorphologyTypesFromConfigDim.lean
def galaxyMorphologyCert : GalaxyMorphologyCert where
  five_types := galaxyMorphology_count

What this page does not claim

The certificate does not claim any real galaxy has been classified correctly. It does not assert the Hubble sequence is physically fundamental or exhaustive in nature. It does not claim the five-type count is derived from the forcing chain; only that it matches the framework's configurational dimension.

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