Transformer Systems Lab
Speculative decoding station
Carry the Serving checkpoint into draft-target verification: a faster path only counts if it preserves the target distribution and actually reduces target-model work.
q drafts x1...xk; p verifies; residual repair keeps pserved request plus draft-target step
speedup is not correctness
choose the useful intervention
match, k, cost, verify, repair
accepted prefix and target checks
lossless needs repair; speed needs agreement
falsify the faster-behavior claim
Carry-in contract
A speedup claim has two gates: correctness and target-step savings.
The route already named serving pressure. Speculative decoding adds a sharper test: draft tokens may make generation faster, but only target verification plus residual repair keeps the sampled distribution honest.
Operable Station 08
Speculative decoding
- 01Text to one update
- 02Tokens and position
- 03Attention routing
- 04RoPE phase
- 05KV memory
- 06Long-context pressure
- 07Serving and decoding
- 08Speculative decoding
- 09Evaluation and falsification
- 10Capstone systems claim
Carry-in from Serving
Latency relief is useful only if target verification keeps the model honest.
Serving named the workload pressure. This station asks whether a fast draft model can reduce target-model steps without turning the output into draft-model sampling.
Selected object
One draft-target verification step on the served request
route:ai-lab/transformers/speculative-decoding#speculative-decoding-stationThe object is a verification protocol: draft proposals, target probabilities, accepted prefix, residual repair, and target-step cost.
Prediction checkpoint
Which intervention makes this served request faster while preserving the target distribution?
Manipulation instrument
Change agreement, draft length, draft cost, verification, and repair.
The witness is deterministic and local. It shows which condition the route needs before calling speculation a serving win.
Serving workload carried in
Keep the request visible while testing the acceleration claim.
Route spine
After speculation, the route asks what the faster behavior proves.
Speculation can reduce target-model passes in the local witness. The next question is not "is it faster?" but "which bounded claim about behavior survives source-grounded evaluation?"
Route memory
Save the correctness boundary, then continue from memory.
The station writes a browser-local checkpoint with the draft-target object, first prediction, accepted-prefix evidence, target-distribution invariant, speedup boundary, and next repair.
Open Study Memory