Fundamental particles

Particle physics becomes easier to query when particles are records, not icons. A useful record separates stable identifiers from measured properties and conventions: name, family, electric charge, spin, mass convention, antiparticle relationship, interactions, uncertainty, source edition, and update date.

Think like a programmer

Design a typed data schema before designing a particle chart. A label such as “mass” is ambiguous unless it says rest mass, energy unit, uncertainty, and data source. Keep interactions as explicit relations rather than relying on a color code in an infographic.

Model checklist

Inputs: A versioned particle-data source, selection filters, unit convention, and uncertainty policy.
State: Typed particle records and interaction relationships.
Rule: Filter or compare properties while preserving units, charge sign, and source version.
Output: A table, family map, allowed interaction summary, or consistency diagnostic.
Check: Every record has an identifier, a declared unit for any mass value, and a source version.

A data model before a diagram

type Particle = {
  id: string;
  family: "quark" | "lepton" | "gauge-boson" | "scalar";
  electricChargeInE: number;
  spin: number;
  restMassMevC2?: { value: number; uncertainty?: number };
  antiparticleId?: string;
  sourceEdition: string;
};

Quarks and leptons are matter fields in the Standard Model. Gauge bosons mediate the model's strong, electromagnetic, and weak interactions; the Higgs boson is a scalar. Protons and neutrons are not fundamental in this classification: they are composite hadrons made from quarks bound by the strong interaction.

Avoid a common visual error: “force carrier” does not mean a tiny ball physically thrown between objects in an everyday mechanical sense. It is a compact way to describe interactions in a quantum field theory. A teaching diagram should name the interaction and the affected fields alongside any connecting line.

Make conventions executable

Charge is a useful sanity check. The proton's quark content is commonly represented as uud, so its charge in units of elementary charge is

const protonCharge = (2 / 3) + (2 / 3) - (1 / 3);
expect(protonCharge).toBe(1);

This does not model confinement or calculate a proton mass. It verifies that the record's stated charge convention is internally consistent. The same caution applies to masses: use the source's quoted value and uncertainty rather than implying a particle's mass is an exact, timeless scalar.

Try this experiment

Prediction: A particle table that uses color alone to distinguish antiparticles becomes ambiguous when rendered without color.

Create one row for a particle and one for its antiparticle. Predict which fields must differ or be explicitly linked, then check whether a screen-reader user can tell them apart without the visual palette.

Where this model breaks

This overview omits quantum-field calculations, hadron structure, neutrino mixing details, detector reconstruction, and the distinction between measured and theory-derived quantities. It also does not make the Standard Model a theory of gravity.

Summary

Use versioned, typed records to teach particle properties. Check charge and units mechanically, label interactions in words, and keep composite particles distinct from the Standard Model's elementary fields.

Glossary

Quark: elementary matter field that participates in the strong interaction.
Lepton: elementary matter field such as an electron or neutrino.
Antiparticle: a particle counterpart with related mass and opposite additive quantum numbers.

Self-check

Why is a particle name alone not a sufficient data record?
What does the uud charge calculation test, and what does it not test?
Why must a particle diagram name an interaction in addition to using color?

Sources

OpenStax, University Physics Volume 3, The Standard Model.
Particle Data Group, Review of Particle Physics, current particle-property conventions and data tables.

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 Fundamental Particles, 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 Fundamental Particles 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 Fundamental Particles into a test

Use typed, sourced, versioned particle records rather than unsourced diagram labels.

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.

Share to: