A record, not a feed.
Eight numbered, source-led pieces. File numbers stay with their original articles; new entries extend the record rather than replacing it.
- File 01Data & Numbers
Measured, calculated, or normalized?
A useful launch-monitor report starts by telling you how each number was produced.
- File 02Equipment
What a driver specification can tell you
A documented driver configuration is not the same thing as a demonstrated gain.
- File 03Guides
Make two iron-set quotes comparable
Compare the actual build and the whole bill—not two prices attached to different baskets.
- File 04Guides
The questions worth taking to a fitting
A baseline, a clear comparison and a written build make a fitting easier to understand.
- File 05Equipment
Loft, bounce, grind—and the claims between them
Read the geometry, the manufacturer’s intended use and the evidence as separate things.
- File 06Data & Numbers
Why speed alone does not decode carry
Three launch numbers deserve three clear labels—not a distance prediction.
- File 07Data & Numbers
Keep modeled distance separate
Save the conditions with the number, not just the number.
- File 08Data & Numbers
A small record makes a fairer comparison
Keep a reproducible session note—not a decontextualized best shot.
All pieces distinguish Confirmed, Our note and Still unknown. A check date marks when linked information was reviewed; it is not a guarantee that a specification or service remains unchanged.