Practice
When the log should say “unknown”
Operators often treat blank cells like personal failure. In checkpoint work, a truthful blank is a gift to the next reader.
Unknown beats invented fluency
Writing “likely seed confirm” when you only saw a generic checkmark pollutes later analysis. Write what you saw on screen, then separately write your hypothesis if you must — labeled as hypothesis.
Unknown is actionable
A clean unknown can trigger a firmware note lookup, a vendor ticket, or a pause. A fake certainty triggers nothing until something breaks.
Teach your desk the phrase
Normalize the sentence: “Logged as unknown pending glossary update.” Teams that punish that sentence train people to lie politely.
We treat this as a first-class skill in Hardware Wallet Checkpoint Logs and the flagship course FAQ’s limitation note.