Now let's talk about time in production. Silence cannot be neutral. Let's review. Uh the next uh failure mode is life cycle failure mode. The run waits for an event that cannot arrive. Silence is not a terminal state. In this dangling tool call issue, the session contains a tool call but no matching tool result. A process may have died. The connection may have dropped. A timeout might have happened before the results were recorded. The exact cause uh matters for debugging. The production failure is much simpler. The run is waiting for a event that will never arrive. New messages cue behind that silence. To the user, the agent simply looks stuck. Runs needs deadlines and cancellation. A deadline bounds the weight. Watchdog makes the stuck work visible. Tools needs time modes and error results. Channels needs recovery commands that do not wait behind the stuck work they are trying to fix. Every external boundary needs an ending. Success, failure, timeout, cancel, or max attempts. Most importantly, the receipt records the terminal outcome. So the next step does not have to guess. Bound the work before the work bounds you.