Skip to content

StandardModel: Formalize 6V2NX: characterize local Higgs gauge orbits - #2095

Open
kastch wants to merge 1 commit into
leanprover-community:masterfrom
kastch:feat/6V2NX
Open

kastch wants to merge 1 commit into
leanprover-community:masterfrom
kastch:feat/6V2NX

Conversation

@kastch

@kastch kastch commented Nov 15, 2026

Copy link
Copy Markdown
Contributor

Formalizes Higgs gauge orbit TODO 6V2NX
on regions where the Higgs doublet does not vanish.

HiggsVec.exists_contDiffOn_su2_rep_eq_iff_norm_sq_eq gives the local orbit criterion:
where the first doublet is nonzero, the pointwise squared norms agree exactly when one weak SU(2) transformation relates the two doublets throughout the region, with matrix entries of the same regularity as the fields.
The rotation to the neutral representative also works when the norm varies over spacetime.
These results concern the scalar part of unitary gauge.

The Higgs API map now records the nonvanishing condition. The module documents why equal norms may not give a continuous transformation at a common zero.

Validation. lake build, lake build PhyslibAlpha, and the auxiliary
script tests passed. Lean examples checked the zero-quartic cases through
import Physlib and reused the boundedness criterion in a one-doublet
limit of the 2HDM.
Linter, theorem and documentation checks passed.

AI assistance. Codex assisted with the local validation and proofs details.

Replace TODO 6V2NX with a local orbit criterion for Higgs doublets:
away from zeros, equality of pointwise squared norms is equivalent
to a weak SU(2) transformation with the same regularity as the fields.
Document why the criterion cannot be extended across arbitrary zeros.
@github-actions

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/Particles/StandardModel/HiggsBoson/API-map.md @@
! file modified Physlib/Particles/StandardModel/HiggsBoson/API-map.md (+20 -14)
@@ Physlib.Particles.StandardModel.HiggsBoson.Basic @@
! module modified Physlib.Particles.StandardModel.HiggsBoson.Basic (+140 -17)
  namespaces StandardModel, StandardModel.HiggsVec, StandardModel.HiggsField
+ added lemma contDiffOn_toRealGroupElem_toSU2
+ added lemma contDiffOn_weakAlignment
+ added lemma exists_analytic_su2_rep_eq_iff_normSq_eq
+ added lemma exists_contDiffOn_su2_rep_eq_iff_norm_sq_eq
+ added lemma toRealGroupElem_eq_toSU2
+ added lemma toRealGroupElem_toSU2_apply_self
+ added lemma toRealGroupElem_toSU2_of_ne_zero
- removed informal_lemma guage_orbit
10 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 c7f70d5, remade whenever a commit is pushed.

@kastch kastch changed the title feat(StandardModel): characterize local Higgs gauge orbits feat(StandardModel 6V2NX): characterize local Higgs gauge orbits Nov 15, 2026
@kastch kastch changed the title feat(StandardModel 6V2NX): characterize local Higgs gauge orbits StandardModel: Formalize 6V2NX: characterize local Higgs gauge orbits Nov 15, 2026
A Higgs field is a smooth section of the Higgs bundle over spacetime, on which the global Standard
Model gauge group acts; for now the bundle is the trivial one, whose fibre is the two-dimensional
complex vector space of pointwise Higgs values. The pointwise values carry an orthonormal basis,
A Higgs field in this module is a real analytic section of the Higgs bundle over spacetime. The

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.

This should not refer to in this module.

rw [h0']
ring

private lemma toRealGroupElem_toSU2_of_ne_zero (v : HiggsVec) (hv : v ≠ 0) :

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 make this non private

transformation. [13]

The general gauge action on sections and the characterization of possible squared norm functions
are separate formalization tasks. [13][TODO]

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.

separate formalization tasks would not use language like this in an API-map. Should just indicate such things with TODOs


-/

private lemma contDiffOn_weakAlignment {E : Type*} [NormedAddCommGroup E] [NormedSpace ℝ E]

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 move up to `toRealGroupElem

doublets `(x + iy, 0)` and `(x - iy, 0)` require the transforming matrix to act with opposite
signs on the first basis vector along the two axes, so the matrix cannot be continuous at
their intersection. -/
lemma exists_contDiffOn_su2_rep_eq_iff_norm_sq_eq {E : Type*}

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 make this doc string more concise.

@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 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

awaiting-author A reviewer has asked the author a question or requested changes medium t-particles Particles

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants