Standard Model overview
The Standard Model is a highly tested quantum-field framework for the strong, electromagnetic, and weak interactions and the elementary fields that participate in them. It is not a complete “periodic table of everything,” and gravity is not part of the Standard Model.
Think like a programmer
Model checklist
- Inputs
- A versioned source, selected field or particle records, interaction type, and a scope statement.
- State
- A graph of typed nodes and labelled relationships.
- Rule
- Expose which fields participate in strong, electromagnetic, or weak interactions under the model.
- Output
- A queryable interaction map and a list of exclusions or open questions.
- Check
- No graph edge claims that gravity is part of the Standard Model; every relationship has a named interaction label.
A practical map
At an introductory level, group elementary fields into quarks, leptons, gauge bosons, and the Higgs field. Quarks carry colour charge and participate in the strong interaction; charged particles participate in electromagnetism; quarks and leptons participate in weak interactions. Gauge bosons represent the corresponding interactions in the framework.
type Interaction = "strong" | "electromagnetic" | "weak";
type Edge = { from: string; to: string; interaction: Interaction; sourceEdition: string };
const forbiddenClaim = edges.some((edge) => edge.interaction === ("gravity" as Interaction));
if (forbiddenClaim) throw new Error("gravity is outside this Standard Model map");
The type restriction is not a proof of physics. It is a guardrail against one common teaching error: silently placing gravity alongside the Standard Model gauge interactions as though it were already part of the same experimentally complete framework.
Feynman diagrams are another useful map, but they are not literal photographs of particles moving along tiny tracks. They organize terms in a calculation and show which interaction is being represented. A page should label the diagram's process, initial and final states, and approximation order before asking a learner to interpret it.
Use uncertainty and gaps honestly
The framework does not settle every question a visitor may associate with particle physics. It does not provide a quantum theory of gravity, and observed phenomena such as dark matter and the matter–antimatter asymmetry motivate work beyond its standard minimal form. An overview should distinguish “not included in this model” from “known to be impossible.”
Try this experiment
Prediction: A graph that names an interaction on every edge can be read without its color palette.
Make one quark–gluon relation, one charged-lepton–photon relation, and one lepton–W relation. Hide the colors and predict whether a reader can still identify the interaction from the text labels alone.Where this model breaks
Summary
Model the Standard Model as a sourced, labelled interaction graph. Separate elementary fields from composite particles, label every claimed force relation in words, and keep gravity and open problems visibly outside the framework's scope.
Glossary
- Quantum field: a field whose excitations are described as particles in quantum field theory.
- Gauge boson: a field quantum associated with a gauge interaction.
- Composite particle: a particle made from more elementary constituents, such as a proton.
Self-check
- Which interactions are included in this overview?
- Why is gravity not an edge in the Standard Model map?
- Why is a Feynman diagram not a literal trajectory picture?
Sources
- OpenStax, University Physics Volume 3, The Standard Model.
- Particle Data Group, Review of Particle Physics, Standard Model and particle-property reviews.
Model contract
Treat the lesson as a small function before treating it as a fact to memorize. Give every value a unit, keep only the state needed for the next step, and make the output easy to inspect.
\[\text{observable output} = f(\text{inputs},\,\text{state})\]- Inputs
- Quantities you set or measure, with units and useful bounds.
- State
- Values the program must retain to reproduce the next result.
- Rule
- The relationship or update that turns inputs and state into a result.
- Check
- A known limit, unit check, invariant, or measured result that can expose a bad model.
Implement the idea as a model
For Standard Model Overview, write down the quantities you can control, the values your program must retain, and the result a reader could inspect. In Nuclear and Particle Physics, the useful program is not the drawing: it is the smallest explicit model that makes a prediction you can test.
Guided experiment
Prediction: changing one declared input while holding the others fixed should change only the outputs that the model connects to that input. Choose one input, predict the direction of change, then check a limiting case such as zero, a symmetric arrangement, or a familiar low-speed or small-change approximation.
Where this model breaks
This lesson is a teaching model, not a complete simulator. Before using it outside the stated question, check which interactions, scales, uncertainties, boundary conditions, and measurement limits it leaves out.
Summary
Treat Standard Model Overview as a contract: named inputs and units enter a rule, the rule produces an observable result, and a known limit or invariant checks whether the implementation deserves trust.
Glossary
- Input: a measured value or chosen parameter supplied to a model.
- State: the smallest set of values needed to continue or reproduce a model.
- Validation: comparing an output with a known result, limit, invariant, or measurement.
Self-check
- Which values are inputs, and which values must remain state?
- What observable result would tell you the model is behaving as expected?
- Which assumption would you test first before applying the model to a real system?
Model review: turn Standard Model Overview into a test
Present the Standard Model as a scoped, sourced framework with evidence and open boundaries.
- Name the inputs and units that the nuclear and particle physics model needs.
- Separate the state you must keep from values you can calculate when needed.
- Write one rule that maps the current state and inputs to an observable result.
- Choose a limiting case, unit check, invariant, or known result before trusting an output.
- State one assumption you would change before using this simplified model for a real decision.