The application side of HotCell. Register the cells a deployment runs, subclass HotCell::Client to name one, and call it with descriptors and a payload. The client owns everything a caller needs to respond correctly to a cell that is saturated, restarting, or absent: the classification of every error into permanent and transient, the exception classes an application injects for each, and instrumentation through ActiveSupport::Notifications.