Daily Team · 2026-10-31
A protocol engineer or learner hand-delivers, drops, duplicates or delays packets between two toy handshake machines while advancing the clock by hand.
Countermand
Shelf Peek
Clay Mend
Gapless Rank
Checked Countdown
Cut on Save
Gauge Shelf
A protocol engineer or learner hand-delivers, drops, duplicates or delays packets between two toy handshake machines while advancing the clock by hand. When the handshake fails, the panel expands the failing step, names the event that caused it in one sentence, and offers Retry from the last good snapshot. A second run is compared against the first, with a marker at the first event where they diverge.
Concept: Handshake Bench
bench.js: handle(state, event) -> {state, outputs}. Events are Tick(ms) and Packet(msg). The initiator resends after a 5 s timeout and gives up after 3 tries. The responder rejects replayed counters. Every step pushes {event, stateBefore, stateAfter} onto a log, which gives per-step snapshots for Retry.index.html as two machine columns with a wire queue between them. Each in-flight packet is a card carrying its own Deliver, Drop, Duplicate and Delay buttons. The first frame loads with message 1 on the wire and Deliver focused. Stack the columns vertically below 560 px. Reserve label widths so nothing shifts. Put status in a polite live region. Under reduced motion, cards move with no transition.```json
{"schemaVersion":1,"name":"Handshake Bench","audience":"Engineers writing or learning network protocol code","problem":"Timeout and replay failures are hard to reproduce and read","interaction":"Deliver, drop, duplicate or delay packets and advance the clock by hand","outcome":"Failed step expands with a one-line cause and a divergence marker between runs","recovery":"Retry from any snapshot as a new run, or Reset to the opening frame","mechanism":"Pure state machine fed hand-made events, with per-step snapshots and run diff","difference":"Packet captures show what happened. This lets you replay it and change one event.","whyNow":"HN sans-IO WireGuard post shows the testable shape. Dot post shows wish for readable errors. Titles only, no demand data.","sourceIds":["8d821849286ada42dbbaeffc","e32e9e5cb5666d607d79fa51"],"evidenceStatus":"sourced","alternatives":[{"name":"Handshake Bench","need":"Reproduce and explain protocol failures","mechanism":"Manual clock and per-packet deliver, drop, duplicate, delay","rejection":"Selected: cross-domain, new to recent dates"},{"name":"Error Signpost","need":"Plain next steps for a CLI error","mechanism":"Paste error, get you-are-here sign with routes","rejection":"Too close to the Dot feed entry and needs real parsing"},{"name":"Fault Tag Sheet","need":"Report broken shared equipment","mechanism":"QR label opens a printable fault card","rejection":"Echoes the Avery label post and recent printables"}]}
```