Astrophysics Pulsar Timing3 From Jcost Pulsar Timing3 Cert

What the certificate proves

Pulsar timing is the practice of predicting the arrival times of a pulsar's radio pulses and comparing those predictions against observations. The differences, called timing residuals, are a sensitive probe of everything from the pulsar's own spin noise to the passage of gravitational waves. For millisecond pulsars, the most stable natural clocks known, residuals are measured at the level of about 100 nanoseconds.

In the Recognition Science framework, a declaration named PulsarTiming3Cert is a machine-checked certificate: a small bundle of formal theorems that are verified by a computer. The certificate proves three facts about a function called domainCost, which is defined as J(m/e), where J is the framework's forced cost function and m and e are real numbers. The three facts are that domainCost equals zero when its two inputs are equal, that it is never negative when both inputs are positive, and that the number phi minus 3/2 is positive. Here phi is the golden ratio, about 1.618, so the third fact simply states that 1.618 minus 1.5 is greater than zero, which is true.

These three facts are general properties of the cost function. They hold for any positive real numbers m and e, and they make no reference to pulsars, timing, or astrophysics. The certificate's name comes from a research note attached to the module, which records an intention: that the framework's cost function might model pulsar timing noise. The note compares a predicted residual of about 118 microseconds against the measured residual of about 100 nanoseconds for a millisecond pulsar, and it reports that the prediction is off by a factor of 1000. That comparison is a research note, not a theorem.

In Recognition Science, the framework's library is a machine-checked collection of formal theorems. The library proves the three general facts, and the certificate packages them. What would turn this into a theorem about pulsar timing is a definition of m and e in terms of pulsar properties, such as spin period or timing noise. No such definition appears in the module. The certificate therefore establishes a general mathematical fact about the cost function, and it does not establish any claim about pulsars.

theorem domainCost_at_eq (r : ℝ) (h : r ≠ 0) : domainCost r r = 0 := by
  unfold domainCost; rw [div_self h]; exact Jcost_unit0

theorem domainCost_nonneg (m e : ℝ) (hm : 0 < m) (he : 0 < e) : 0 ≤ domainCost m e := by
  unfold domainCost; exact Jcost_nonneg (div_pos hm he)

theorem canonicalThreshold_pos : 0 < canonicalThreshold := by
  unfold canonicalThreshold; linarith [phi_gt_onePointFive]

theorem domainCost_nonneg (m e : ℝ) (hm : 0 < m) (he : 0 < e) : 0 ≤ domainCost m e := by
  unfold domainCost; exact Jcost_nonneg (div_pos hm he)

def domainCost (m e : ℝ) : ℝ := Jcost (m / e)

What this page does not claim

The certificate does not claim that pulsar timing residuals equal J(phi) times spin period. The certificate does not claim that the framework's cost function models any astrophysical process. The certificate does not claim that the factor-of-1000 discrepancy is resolved or explained.

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/Pulsar_Timing3_FromJCost.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: