Skip to content

Glimm-Jaffe Axioms - #2093

Open
annamei1 wants to merge 11 commits into
leanprover-community:masterfrom
annamei1:feat/glimm-jaffe-axioms
Open

annamei1 wants to merge 11 commits into
leanprover-community:masterfrom
annamei1:feat/glimm-jaffe-axioms

Conversation

@annamei1

Copy link
Copy Markdown

Definitions of Glimm-Jaffe Axioms (axioms for Euclidean QFT) ported from OSforGFF.

annamei1 and others added 5 commits November 14, 2026 12:13
Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
@github-actions

github-actions Bot commented Nov 14, 2026 •

Copy link
Copy Markdown
Contributor

Thank you for this pull-request (PR). If this is your first PR, welcome to the community!

While you wait for a review, note that you can review PRs too; reviewing is not restricted to maintainers. Our review guidelines explain what to look for.

Over time, contributions such as reviews, maintenance and documentation are recorded on contributions.physlib.io.

Three main points:

  • Comment -awaiting-author on its own line to remove that label from your PR.
  • Comment blocked-by-PR or -blocked-by-PR on its own line to add or remove that label, respectively.
  • The first review might take several days to arrive. If in doubt message on the Zulip.

For the author: Please read

Below is what will happen next. Please read carefully if you are not familiar with the process. You may open other PRs while this one is being reviewed, and can stack PRs on top of each other, so don't let these steps slow you down.

  1. Some automated checks will be run on your PR. You can see the results of these checks at the buttom of your PR page. If any of these checks fail, you will need to fix the issues before your PR can be merged. You can learn more about these here, including how to run them locally, which is sometimes quicker than relying on the GitHub Actions. If you have never had a PR merged before, you may have to wait for a reviewer to manually start these checks (this is for security).

  2. A reviewer will look at your PR and may ask you to make changes. This may happen a couple of days after you submit your PR, so you may need to be patient. But it should not be longer than that - if it is please bring it to the attention of the community on the Zulip. The level of review will depend on where your PR is submitted. If it is submitted to ./Physlib or ./QuantumInfo, the review will be more thorough than if it is submitted to ./PhyslibAlpha. You can find out more about what the review process is looking for in our review guidelines. If a reviewer adds an awaiting-author label to your PR, address the review comments, then please remove that label by adding a comment with -awaiting-author. This helps us keep track of reviews.

  3. The reviewer will either approve your PR, or request more changes (in which case we return to step 2). Once your PR is approved, it will be merged by a maintainer, this should happen shortly after approval, though you may get more comments at this stage.

Tip: The easiest way to get a fast review is to submit a PR that is small and self-contained, and has clear documentation explaining why things are the way they are in your changes.

If you have any problems or questions, please reach out to the community on the Zulip.

For reviewers: Summary of your PR

Found differences:
@@ Physlib.QFT.Euclidean.GlimmJaffe.Axioms @@
+ module added Physlib.QFT.Euclidean.GlimmJaffe.Axioms (+135 -0)
  namespaces GlimmJaffe
+ added def OS0Analyticity
+ added def OS1Regularity
+ added def OS2EuclideanInvariance
+ added def OS3ReflectionPositivity
+ added def OS4Ergodicity
+ added def TwoPointIntegrable
+ added structure GlimmJaffeAxioms
@@ Physlib.QFT.Euclidean.GlimmJaffe.Basic @@
+ module added Physlib.QFT.Euclidean.GlimmJaffe.Basic (+230 -0)
  namespaces GlimmJaffe, GlimmJaffe.FieldConfiguration
+ added abbrev FieldConfiguration
+ added abbrev PositiveTimeTestFunction
+ added def SchwingerFunction
+ added def SchwingerFunction₂
+ added def SmearedTwoPointFunction
+ added def bumpToSchwartz
+ added def euclideanAction
+ added def generatingFunctional
+ added def generatingFunctionalReal
+ added def pairing
+ added def reflectedConjugate
+ added def standardBumpSequence
+ added def timeTranslation
+ added def translateSchwartz
+ added instance fieldConfigurationMeasurableSpace
+ added lemma euclideanAction_apply
+ added lemma integral_bumpToSchwartz
+ added lemma reflectedConjugate_apply
+ added lemma reflectedConjugate_involutive
@@ Physlib @@
! module modified Physlib (+2 -0)
@@ Physlib.SpaceAndTime.TimeAndSpace.Basic @@
! module modified Physlib.SpaceAndTime.TimeAndSpace.Basic (+51 -0)
  namespaces TimeAndSpace, Space
+ added def euclideanCoordinates
+ added def timeReflection
+ added lemma euclideanCoordinates_measurePreserving
+ added lemma timeReflection_apply
+ added lemma timeReflection_involutive
@@ docs/references.bib @@
! file modified docs/references.bib (+20 -0)
@@ scripts/lint/exemptions/spellingWords.txt @@
! file modified scripts/lint/exemptions/spellingWords.txt (+14 -0)
37 differences

The declarations are found by reading the diff as text, without regard for namespaces, so a declaration whose keyword and name are on different lines is missed, and two declarations of the same name in different namespaces are listed as one. A change to a proof, or to the body of a definition, does not appear. See scripts/alpha/github/pr_summary.lean.

Summary of commit 6ed0998, remade whenever a commit is pushed.

@jstoobysmith jstoobysmith left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi Anna!

Many thanks for this PR. I've added some (mainly style) comments. Generally this looks very good.

/-! ## A. Field configurations and generating functionals -/

/-- Euclidean spacetime with `d` total coordinates; coordinate zero is time. -/
abbrev EuclideanSpacetime (d : ℕ) := EuclideanSpace ℝ (Fin d)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So for things like this, I think it is better to use the definitions already in Physlib, so things remain connected. If this is Euclidean spacetime, not Minkowski it would be usual to use Time x Space d

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have a dedicated file called TimeAndSpace (to distinguish it from SpaceTime which is Minkowski)).

Comment on lines +2 to +3
Copyright (c) 2025 Michael R. Douglas, Sarah Hoback, Anna Mei, Ron Nissim. All rights reserved.
Copyright (c) 2026 Sergey A. Cherkis. All rights reserved.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is usual to only put one name in the copyright. somewhat flexiable on this I think, but I'm unsure if this will pass the linters

def timeIndex : Fin d := ⟨0, by have := Fact.out (p := 2 ≤ d); omega⟩

/-- Reflection of the time coordinate, as a continuous linear equivalence. -/
def timeReflection : EuclideanSpacetime d ≃L[ℝ] EuclideanSpacetime d :=

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Things like this should really go in the TimeAndSpace file.

variable {d : ℕ}

/-- The complex-linear extension of the pairing of a real field with a Schwartz test. -/
def pairing (ω : FieldConfiguration d) (f : 𝓢(EuclideanSpacetime d, ℂ)) : ℂ :=

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would maybe put this and the below in the FieldConfiguration namespace


## i. Overview

This is the measure-based setup used by `OSforGFF`, adapted to Mathlib and Physlib.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it be possible here to write a paragraph explaining the underling principles behind this theory e.g. what defines a QFT in this setting, what the fiels are etc.

@jstoobysmith

Copy link
Copy Markdown
Member

awaiting-author

@github-actions github-actions Bot added the awaiting-author A reviewer has asked the author a question or requested changes label Nov 15, 2026
annamei1 and others added 5 commits November 15, 2026 16:40
Add the time-first continuous linear coordinate equivalence, prove that it
preserves spacetime volume, and provide time reflection with its involution law.

Co-authored-by: Codex <noreply@openai.com>
Use the shared spacetime coordinates and FieldConfiguration namespace while
preserving full Euclidean invariance, dimension assumptions, and the original
Schwinger and mollifier formulas. Prove transported bumps retain integral one.

Consolidate the copyright notices and document the Chapter 6 source in
Glimm and Jaffe, Quantum Physics.

Co-authored-by: Codex <noreply@openai.com>
Retain the original Glimm-Jaffe domain with narrow unused-argument exemptions. Remove a redundant simp attribute and two redundant imports without changing executable bodies.

Co-authored-by: Codex <noreply@openai.com>
Reuse Mathlib conversions for real bumps and field configurations. Add the Euclidean action on complex distributions and prove its group laws and translation convention. Prove that the smeared two-point function and OS4 retain their original real formulations.

Co-authored-by: Codex <noreply@openai.com>
@jstoobysmith

Copy link
Copy Markdown
Member

@annamei1 Many thanks for updating this PR :). If you want it to be looked at again, would you mind commenting with -awaiting-author. It helps us keep track of things :).

@annamei1

Copy link
Copy Markdown
Author

I'm still updating things (unifying the complex vs real convention), will do once it's finalized!

Revert 0410dac at the user’s request, restoring the previous definitions and documentation.

Co-authored-by: Codex <noreply@openai.com>
@annamei1

Copy link
Copy Markdown
Author

All infrastructure (time translation, Euclidean actions, etc) should be defined on complex test functions and tempered distributions, while FieldConfiguration is real tempered distributions. Please check again and let me know if you would like to structure the conventions any other way!

@annamei1

Copy link
Copy Markdown
Author

-awaiting-author

@github-actions github-actions Bot removed the awaiting-author A reviewer has asked the author a question or requested changes label Nov 16, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants