Glossary · Dry runAlso called dry-run mode, no-op modeChecked 27 September 2026
What is a dry run, and why should a system do one before it acts?
A dry run does everything except the part that changes something. It reads, computes and prints what it would have done, then stops. When it is the default, running the dangerous version of a script takes a deliberate act, and an accident produces a printout instead of a thousand modified rows.
In one lineEverything except the part that changes something. Default, not a flag.
Why it matters to you
This is the cheapest safety rule in operations and it is nearly always retrofitted after the incident that justified it.
On WhoFits the standing rule is that every script writing to the database defaults to dry run, and that tests read production but write their results to a local file, never back. It costs one line and it removes an entire category of Monday morning.
The same instinct applies to deletes. Both foreign keys on the WhoFits interaction-edge table used to cascade, so removing a creator quietly removed the edges that had taken days to collect. Changing them to restrict on 2026-03-22 turned a silent data loss into a blocked delete that names what it is blocking. For data that is expensive to collect, deletion should be loud.
If a proposal used this word and did not explain it, ask us.
The first conversation is with the people who would build it. If there is a fit, the Consult comes next.