New essay: Counting Is a Discovery. Seconds Are a Decision.

true
essay
methodology
calibration
framing
A new essay on a discipline that runs underneath the whole A=1 program: keeping the counting engine free of imported constants. A number you can count from the lattice is a discovery; a number you must import is a decision — and in a sentence they look identical, which is how a chosen constant ends up restated as a prediction. The fix is structural: we do not hard-code constants.
Author

Jack D. Menendez

Published

July 4, 2026

There is a new essay on the site — Counting Is a Discovery. Seconds Are a Decision. — on a discipline that runs underneath the whole A=1 program: keeping the counting engine free of imported constants.

The essay draws a line between two kinds of number. Some you can count straight off the lattice — how many steps, how many arrangements; that is distance, that is entropy. Others you cannot get at all without a number that is not in the lattice — seconds, joules, meters — a factor you chose to match the world. Count the first and you have discovered something; import the second and you have decided something. In an English sentence the two look identical, which is exactly how a constant picked to fit the data ends up restated, a paragraph later, as a prediction the model made.

The remedy is structural, not a resolution to be careful — because carefulness demonstrably fails. The piece opens with the author’s own slip (mid-sentence, while describing the wall) and closes with a true story about a login system that had quietly learned one specific person’s name, hundreds of times over. The rule it lands on: we do not hard-code constants. The engine emits only counts; every calibration lives behind a single declared boundary — which turns “how much are we assuming?” from an argument into a number you can read off.

It is a methodological piece, in the program’s usual lane: a claim about how we work, not about what the universe is.

Read it: Counting Is a Discovery. Seconds Are a Decision.