Encyclopedia Foundation Foundation Pair Kernel Event Metric Pricing S16 Parent Derived Configuration Has
ARTICLE 4 claims 4 theorems
Foundation Pair Kernel Event Metric Pricing S16 Parent Derived Configuration Has
A machine-checked theorem shows that a certain way of counting a posting's parent degrees forces a specific configuration dimension, but it does not prove that this dimension is the physical one.
The forced dimension
In the Recognition Science framework, a posting is a discrete record of an event, and every posting carries a configuration: the list of facts attached to it, such as where it happened and what came before it. The framework's library, a machine-checked collection of formal theorems, proves a statement about one particular way of deriving that configuration from the posting's parent degrees. The theorem, named parentDerivedConfiguration_has_forcedDimension, says that if you build a posting's configuration by reading off exactly how many parent degrees it has, then that configuration is forced to have a dimension equal to D + 2, where D is a constant from the framework's own derivation of spatial degrees.
The proof is short and direct. The library first proves that the parent-derived configuration does read the parent degrees, which is true by definition. It then proves a general lemma: any configuration that reads parent degrees must have the forced dimension, because the carrier of those degrees has cardinality D + 2. The theorem is a formal consequence of these two facts. It is not a physical claim about the universe; it is a mathematical statement about a specific construction inside the framework. The library itself marks this distinction: the canonical witnesses for the configuration are models, not physical selection theorems.
What the theorem does not claim is just as important. It does not say that the physical universe has three spatial dimensions. The framework's broader argument for three dimensions is a separate chain of theorems, and the bridge from recognition events to physical linking is explicitly left open. The theorem also does not say that energy readouts work; the library contains a separate theorem stating that the ledger cost energy does not read the recognition price. Finally, the theorem does not claim that the parent-derived configuration is the only one, or the correct one. It establishes a conditional fact: if a configuration reads parent degrees, then it has the forced dimension. The converse, that the forced dimension implies the physical one, is not part of this declaration.
THEOREM parentDerivedConfiguration_has_forcedDimension · IndisputableMonolith/Foundation/PairKernelEventMetricPricingS16.lean
theorem parentDerivedConfiguration_has_forcedDimension
{N : ℕ} [NeZero N] :
PostingEventHasForcedConfigurationDimension3
(@parentDerivedPostingConfigurationDimension3 N _) :=
parentDegreeReadout_implies_forcedConfiguration
parentDerivedConfiguration_readsParentDegrees
THEOREM parentDerivedConfiguration_readsParentDegrees · IndisputableMonolith/Foundation/PairKernelEventMetricPricingS16.lean
theorem parentDerivedConfiguration_readsParentDegrees
{N : ℕ} [NeZero N] :
PostingConfigurationReadsParentDegrees3
(@parentDerivedPostingConfigurationDimension3 N _) := by
intro event
rfl
THEOREM parentDegreeReadout_implies_forcedConfiguration · postingConfigurationDegreeCarrier_card · IndisputableMonolith/Foundation/PairKernelEventMetricPricingS16.lean
/-- Reading the event-local parent carrier derives S15's configuration join. -/
theorem parentDegreeReadout_implies_forcedConfiguration
{N : ℕ} [NeZero N]
{dimension : PostingConfigurationDimension3 N}
(hread :
PostingConfigurationReadsParentDegrees3 dimension) :
PostingEventHasForcedConfigurationDimension3 dimension := by
intro event
rw [hread event,
postingConfigurationDegreeCarrier_card]
theorem postingConfigurationDegreeCarrier_card
{N : ℕ} [NeZero N]
(configuration : PostingRecognitionConfiguration3 N) :
Fintype.card
(PostingConfigurationDegreeCarrier3 configuration) =
GapDerivation.configDim GapDerivation.D := by
simp [PostingConfigurationDegreeCarrier3,
GapDerivation.configDim]
THEOREM ledgerCostEnergy_does_not_read_recognitionPrice · IndisputableMonolith/Foundation/PairKernelEventMetricPricingS16.lean
theorem ledgerCostEnergy_does_not_read_recognitionPrice :
¬ PostingEnergyReadsRecognitionConfigurationPrice3
canonicalChannel
(@parentDerivedPostingConfigurationDimension3 3 _)
(ledgerCostEventKinematics3 3) := by
intro hread
obtain ⟨pair, hpair⟩ :=
realizedPrimitivePostingPair3_exists
let event : RealizedPostingEvent3 3 :=
⟨pair, hpair⟩
have h := hread event
change
Cost.Jlog 1 =
recognitionConfigurationPrice canonicalChannel
(parentDerivedPostingConfigurationDimension3 event) at h
rw [recognitionConfigurationPrice_eq_phi_zpow_neg] at h
rw [show
parentDerivedPostingConfigurationDimension3 event =
GapDerivation.configDim GapDerivation.D by
exact
parentDerivedConfiguration_has_forcedDimension
event] at h
exact ledgerJlogUnitCost_ne_constants_hbar
(h.trans GapDerivation.hbar_exponent_eq_configDim.symm)
What this page does not claim
The theorem does not claim that the physical universe has three spatial dimensions. The theorem does not claim that the parent-derived configuration is the only possible one. The theorem does not claim that energy readouts work; the library explicitly proves the opposite for the ledger cost energy.
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/Foundation/PairKernelEventMetricPricingS16.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:
- What is the physical interpretation of the constant D, and how is it derived?
- How does the framework's separate chain of theorems force three spatial dimensions from recognition events?
- What would it mean for a configuration to read parent degrees in a way that is not the parent-derived one?
- What is the status of the energy readout statement, given that the ledger cost does not read the recognition price?
- How does the framework define the physical linking bridge that connects recognition events to the spatial dimensions of the universe?
MACHINE LAYER · GROUNDED CLAIM TABLE · CLICK TO EXPAND
THEOREM parentDerivedConfiguration_has_forcedDimension · IndisputableMonolith/Foundation/PairKernelEventMetricPricingS16.lean
theorem parentDerivedConfiguration_has_forcedDimension {N : ℕ} [NeZero N] : PostingEventHasForcedConfigurationDimension3 (@parentDerivedPostingConfigurationDimension3 N _) := parentDegreeReadout_implies_forcedConfiguration parentDerivedConfiguration_readsParentDegreesThe theorem says that if you build a posting's configuration by reading off exactly how many parent degrees it has, then that configuration is forced to have a dimension equal to D + 2. parentDerivedConfiguration_has_forcedDimension · IndisputableMonolith/Foundation/PairKernelEventMetricPricingS16.leanTHEOREM parentDerivedConfiguration_readsParentDegrees · IndisputableMonolith/Foundation/PairKernelEventMetricPricingS16.lean
theorem parentDerivedConfiguration_readsParentDegrees {N : ℕ} [NeZero N] : PostingConfigurationReadsParentDegrees3 (@parentDerivedPostingConfigurationDimension3 N _) := by intro event rflThe proof first proves that the parent-derived configuration does read the parent degrees, which is true by definition. parentDerivedConfiguration_readsParentDegrees · IndisputableMonolith/Foundation/PairKernelEventMetricPricingS16.leanTHEOREM parentDegreeReadout_implies_forcedConfiguration · postingConfigurationDegreeCarrier_card · IndisputableMonolith/Foundation/PairKernelEventMetricPricingS16.lean
/-- Reading the event-local parent carrier derives S15's configuration join. -/ theorem parentDegreeReadout_implies_forcedConfiguration {N : ℕ} [NeZero N] {dimension : PostingConfigurationDimension3 N} (hread : PostingConfigurationReadsParentDegrees3 dimension) : PostingEventHasForcedConfigurationDimension3 dimension := by intro event rw [hread event, postingConfigurationDegreeCarrier_card]theorem postingConfigurationDegreeCarrier_card {N : ℕ} [NeZero N] (configuration : PostingRecognitionConfiguration3 N) : Fintype.card (PostingConfigurationDegreeCarrier3 configuration) = GapDerivation.configDim GapDerivation.D := by simp [PostingConfigurationDegreeCarrier3, GapDerivation.configDim]It then proves a general lemma: any configuration that reads parent degrees must have the forced dimension, because the carrier of those degrees has cardinality D + 2. parentDegreeReadout_implies_forcedConfiguration · postingConfigurationDegreeCarrier_card · IndisputableMonolith/Foundation/PairKernelEventMetricPricingS16.leanTHEOREM ledgerCostEnergy_does_not_read_recognitionPrice · IndisputableMonolith/Foundation/PairKernelEventMetricPricingS16.lean
theorem ledgerCostEnergy_does_not_read_recognitionPrice : ¬ PostingEnergyReadsRecognitionConfigurationPrice3 canonicalChannel (@parentDerivedPostingConfigurationDimension3 3 _) (ledgerCostEventKinematics3 3) := by intro hread obtain ⟨pair, hpair⟩ := realizedPrimitivePostingPair3_exists let event : RealizedPostingEvent3 3 := ⟨pair, hpair⟩ have h := hread event change Cost.Jlog 1 = recognitionConfigurationPrice canonicalChannel (parentDerivedPostingConfigurationDimension3 event) at h rw [recognitionConfigurationPrice_eq_phi_zpow_neg] at h rw [show parentDerivedPostingConfigurationDimension3 event = GapDerivation.configDim GapDerivation.D by exact parentDerivedConfiguration_has_forcedDimension event] at h exact ledgerJlogUnitCost_ne_constants_hbar (h.trans GapDerivation.hbar_exponent_eq_configDim.symm)The library contains a separate theorem stating that the ledger cost energy does not read the recognition price. ledgerCostEnergy_does_not_read_recognitionPrice · IndisputableMonolith/Foundation/PairKernelEventMetricPricingS16.lean