Parked sketch — qualify the heartbeat with live throughput (2026-06-03)

DARE.CO.UK · PARKED SKETCH · 2026-06-06

Mirrored from ~/.claude/.../memory/parked_sketch_heartbeat_throughput_qualifier_2026-06-03.md. This is a design sketch parked for future build — read for context, not as a current deliverable.

Future enhancement to status.gf.cx/transfers heartbeat — surface a slowly-changing throughput delta (“3.16 MB/s” / “+0.1 GB”) that ticks every few seconds, so the pulse reads as alive AND honest about pace. Dan’s framing: “equivalency.” Parked until smart.sellars transfer ships and Dan watches the existing heartbeat in real conditions.

Park reason: Heartbeat alone may be enough — decision deferred until the next bulk transfer (smart.sellars takeout, ~1.5TB) so Dan can judge with one more live datapoint.

Dan’s framing (verbatim 2026-06-03):

“Maybe it’s just track 0.1gb updates, or adding 3.16mbps, that changes every few ticks, something that qualifies the heartbeat… It was equivalancy that I was looking for, that very unique aspect of creativity, hard-to-say exactly what it is.”

The concept — “equivalency”: The qualitative property where on-screen motion equivalent to what’s actually happening underneath. Heartbeat alone says “alive.” A heartbeat + live throughput delta says “alive AND honest about pace.” Together they read as TRUSTWORTHY motion rather than decorative motion. This is a generalizable UX principle, not just for transfers.

Specific sketch: - Keep heartbeat as the binary alive/dead signal - Add a small monospace throughput readout that updates every 5-15s: +0.1 GB · 3.16 MB/s (or whatever the rclone stats line emits) - Source: rclone --stats 5s --stats-one-line log parsing (12 ticks/min vs default 1 tick/min) - When throughput dips → number changes → user sees it without alarm. When throughput stops → number freezes → user knows something’s wrong before the heartbeat even stalls.

Resume conditions: - After smart.sellars takeout (link expires 2026-06-08) — Dan watches the current heartbeat-only for ~24h - If he feels the gap, build the throughput qualifier - If heartbeat alone holds up, the principle lives on for future surfaces (agent loops, batch jobs, replication) where motion-vs-truth ratio matters

Build estimate when unparked: ~2-3hr — rclone –stats 5s parser + tiny status.gf.cx writer + CSS readout below the heartbeat.

Sibling principles to weave in: - feedback_heartbeat_animation_progress_pattern_2026-06-03.md — the heartbeat itself - “Equivalency” as a new design vocabulary entry: motion that matches reality vs motion that performs reality