From f46476bb844aad5b31f4ac1a73707aa067e1675f Mon Sep 17 00:00:00 2001 From: Jean-Pierre Martineau Date: Tue, 11 Aug 2026 02:07:25 -0400 Subject: [PATCH] Payload marks: a request goes up, its answer comes down MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The console's compact glyphs for REQ and RESPONSE read them as inbound and outbound mail — ↓ for the ask, ↑ for the answer. That is the wrong axis: what a reader is tracking is the exchange, not the mailbox, and in an exchange the question goes out and the answer comes back. Co-Authored-By: Claude Opus 5 (1M context) --- meshterm/ui/theme.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/meshterm/ui/theme.py b/meshterm/ui/theme.py index f21801f..78443d8 100644 --- a/meshterm/ui/theme.py +++ b/meshterm/ui/theme.py @@ -521,8 +521,8 @@ _GLYPH_MAP: dict[str, str] = { "✅": "✓", # ack (the ok-family check) "❔": "·", # unknown class — a neutral dot # Raw payload classes (PAYLOAD_ICONS); raw ADVERT/ACK reuse ☼/✓ above - "📥": "↓", # REQ — inbound ask - "📮": "↑", # RESPONSE — outbound answer + "📥": "↑", # REQ — a question going out + "📮": "↓", # RESPONSE — the answer coming back "📩": "→", # TEXT_MSG (overheard direct message) — text in flight "📻": "#", # GRP_TXT — channel text (the # channel mark) "💽": "§", # GRP_DATA — a data section on a channel