diff --git a/display-board-1408.md b/display-board-1408.md
index a42b3afc..356757d6 100644
--- a/display-board-1408.md
+++ b/display-board-1408.md
@@ -99,9 +99,12 @@ also the RIO's **error annunciator**:
 
 - **`E0` serial-diagnostics readout** (`$D5F2`) — `E0xxyyzz` where
   `xx` = TX-ring overflow count (`$3187`, outbound byte dropped because
-  the ring was full, `$D66A`), `yy` = reply-retransmit count (`$3184`,
-  the game failed to ACK a reply, `$D96A`), `zz` = reply-teardown/give-up
-  count (`$3185`, `$DA2F`). Each increment site immediately re-renders,
+  the ring was full, `$D66A`), `yy` = give-up count (`$3184`, `$D96A` —
+  reply cycles whose 5 timeout retransmits all went unACKed), `zz` =
+  reply-teardown count (`$3185`, `$DA2F` — any reply cycle that needed
+  at least one retransmission; the counter behind a lone `E0000001`).
+  Semantics bench-confirmed 2026-07-19: display read `E0000105` after
+  one give-up + five teardowns. Each increment site immediately re-renders,
   so the display live-updates as serial trouble accumulates. If a
   cockpit's display reads `E0…` instead of `F0000000`, the serial link
   has been dropping or retrying. Note there is **no threshold in stock