 
   ;; The child-monitor loop should handle this
   ;; detail
-  (comment (child-> io-handle ::specs/normal))
+  #_(comment (child-> io-handle ::specs/normal))
   (.close from-child))

                       #(log2/warn %
                                   ::action-trigger
                                   "Updater returned"
                                   (dissoc state' ::log/state)))
        _ (assert (::specs/outgoing state') (str "After updating for " tag))
        my-logs (::log2/state state')
        forked-logs (log2/fork my-logs)

    :as io-handle}
   array-o-bytes]
  (let [prelog (utils/pre-log message-loop-name)]
    ;; Q: What on Earth can I do about logging this?
    ;; I could just create a new set of log entries each
    ;; time.
    ;; Starting over from 0 seems idiotic.
    ;; I could wrap the function definition in an atom/agent that
    ;; tracks the log state over the course of each call.
    ;; That seems really dumb, since it creates a single-threaded
    ;; pipeline bottleneck from each child thread.
    ;; That probably isn't a big deal for clients, but it seems like
    ;; a mistake for servers.
    ;; Servers will wind up with their own bottlenecks, but this
    ;; should not be one of them.
    ;; It's a conundrum.
    ;; TODO: Unravel it.
    (log/debug prelog
               "Top of child->!")
    (when-not from-child
