Invariants / DC-OUTBOUND-FIFO-01
DC-OUTBOUND-FIFO-01
DC derived enforcedThe per-peer outbound channel preserves FIFO order: OutboundCommands enqueued for PeerId(p) in order O₁..Oₙ arrive at the peer's TCP socket in the same order (mpsc::Sender::send guarantees FIFO; MuxPump's session-aware encoder processes them sequentially).
- Source
docs/planning/phase4-n-s-invariants.md §3 (D4)
- Cluster
- PHASE4-N-S-B
- Introduced in
- PHASE4-N-S-B
Enforcement trace
Tests 0
no tests named — gap
CI 0
no CI script — gap
Cross-references
Evidence notes
FIFO is structurally guaranteed by the underlying tokio::sync::mpsc::Sender contract (per the tokio docs: 'sent messages are received in the order they were sent'). MuxPump's run() loop processes one OutboundCommand per tokio::select! iteration, so per-peer FIFO is preserved end-to-end without additional ordering primitives.