Send only the surprise — at1 link

When both endpoints hold a shared model of the traffic, the channel doesn’t need to carry the whole message — only its deviation from what the model expects. at1 link ships the model once, then every frame is a few bytes of surprise: 3.2× fewer channel bytes than standalone compression on the tiny frames that satellite, IoT and deep-space links actually send. On mobile it’s an energy claim before a speed one — fewer radio bytes.

Use it

# 1) ship the shared traffic model once, from history
at1 link model traffic-history.log -o shared.model

# 2) then every frame is just its deviation from the model
at1 link simulate live-frames.log --model shared.model
#   42 frames — channel 1,016 B vs standalone 3,277 B (3.23x fewer)
#   byte-exact=True; divergence detected=True

What it guarantees

  • Byte-exact — the receiver reconstructs every frame exactly.
  • Divergence detected — a one-byte model desync is caught at the handshake, deterministically.
  • Graceful fallback — on desync, resend standalone; never wrong, just larger.

The win comes from small frames against a shared model; large batches self-compress and dilute it. Model sync and divergence recovery are the real engineering — the coding is the easy part. Gate a deployment on your actual frame sizes and bandwidth economics.

← CLI reference