docs(classical-field): add gauge theory API map#1438
Conversation
|
Thank you for this PR, which will now be reviewed. If submitting to ./Physlib or ./QuantumInfo, please see our review guidelines if you are not familiar with the process. You should expect a back and forth with a reviewer before your PR is merged. See also that link for how to add appropriate labels to your PR. The PR will also go through a number of automated checks. You can learn more about these here, including how to run them locally. If you are submitting to ./PhyslibAlpha there will be a lighter review process, though your PR must still pass the automated checks. If you want to bring attention to this PR, please write a message on this thread of the Lean Zulip. Important: If a reviewer adds an |
Motivation
Related to #1414, and a tracking map for the gauge-theory API in #859. An API map records the implemented status and source location of each requirement for an API, so the gap between a planned API and the current library stays visible in-tree.
Changes
Adds
Physlib/ClassicalFieldTheory/GaugeTheory/API-map.yaml.The library has no general or non-abelian gauge-theory framework yet, so those requirements (an abstract structure group, the connection, the covariant derivative, Yang-Mills curvature and action, Wilson lines, and a principal-bundle formulation) are marked not done with location
N/A. The completed requirements point at the two concrete pieces that do exist: the abelian U(1) case inPhyslib/Electromagnetism/Kinematics(potential, field strength, the gauge transformation and its invariance, and equivariance under the Lorentz action), and the Standard Model gauge group inPhyslib/Particles/StandardModel/Basic.lean.Testing
Ran the API-map linter:
The map passes: every declared source file and name resolves, and no completed entry is missing a location.