Name the write queue in the index of the directory that holds it

src/server/mod.rs

@@ -45,6 +45,16 @@
 //! same reason [`transport`] holds no socket, and where the last of its states
 //! hands over to is [`recovery`].
 //!
+//! [`write_queue`] holds 0047's one queue, which that record opens by deciding
+//! is the path every write to a server takes rather than the offline path: the
+//! counter the order is kept by rather than any clock, which two actions
+//! touching one target with one kind are coalesced into one entry at the moment
+//! of enqueue, the bound and the oldest entry an overflow drops, what the queue
+//! reports afterwards, and the order a drain walks in. Nothing is sent, nothing
+//! is acknowledged and no drain runs, for the same reason [`transport`] holds no
+//! socket, and what a drain would be scheduled by is [`recovery`] rather than a
+//! timer of its own.
+//!
 //! [`federation`] holds what 0072 decides: a second host becomes reachable only
 //! through an act a person performed, against one server, naming what it shares,
 //! and revocable without the network. Which hosts may be contacted at all is