AT-1 Link
Send only the surprise
When both endpoints hold a shared model of the traffic, the channel carries only each message’s deviation from what the model expects. Ship the model once, then every frame is a few bytes of surprise — the win is largest 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.
- 3.2×
- fewer channel bytes than standalone compression, small frames
- byte-exact
- the receiver reconstructs every frame exactly
- divergence
- a one-byte model desync is caught at the handshake
- fallback
- on desync, resend standalone — graceful, never wrong
at1 link model traffic-history.log -o shared.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
Honest scope.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.
Billed per 1k frames — first 10M frames/month free. See pricing.