Skip to content

feat(patterns): author Speculative Decoding entry in family 17-ai-agentic - #403

Closed
mjmirza wants to merge 2 commits into
mainfrom
feat/speculative-decoding-pattern-14284939946109495184
Closed

feat(patterns): author Speculative Decoding entry in family 17-ai-agentic#403
mjmirza wants to merge 2 commits into
mainfrom
feat/speculative-decoding-pattern-14284939946109495184

Conversation

@mjmirza

@mjmirza mjmirza commented Aug 23, 2026

Copy link
Copy Markdown
Owner

1. What Changes

Authors the master-level pattern entry Speculative Decoding (patterns/17-ai-agentic/speculative-decoding.md) with all 18 mandatory dimensions, Level A/B citations (ICML 2023 primary literature, vLLM/TensorRT-LLM docs), and runnable code examples in Python, TypeScript, and Go. Updates all discovery pathways and catalogue status artefacts.

2. Why This Matters

Speculative Decoding is a fundamental LLM inference acceleration technique that solves memory-bandwidth bottlenecks in autoregressive Transformer decoding by using a draft model for token proposals and a target model for parallel verification via modified rejection sampling.

3. Why Now

As of 2026, Speculative Decoding is standard across production LLM serving frameworks (vLLM, TensorRT-LLM, Apple MLX, SGLang) for low-latency agentic and interactive workloads.

4. Exact Current-Date Evidence

  • Leviathan, Kalman, Matias (ICML 2023): "Fast Inference from Transformers via Speculative Decoding" (arXiv:2211.17192). Verified 2026-08-23.
  • Chen et al. (2023): "Accelerating Large Language Model Decoding with Speculative Sampling" (arXiv:2303.01318). Verified 2026-08-23.
  • vLLM Documentation: "Speculative Decoding Architecture" (docs.vllm.ai). Verified 2026-08-23.
  • NVIDIA TensorRT-LLM Developer Guide: "Speculative Decoding". Verified 2026-08-23.

5. Multi-Pass Confidence Score

  • Novelty / Non-duplication: 25/25
  • Evidence quality: 20/20
  • Real user value: 15/15
  • Current relevance/timing: 15/15
  • Catalogue fit: 10/10
  • Feasibility: 10/10
  • Risk/reversibility: 5/5
  • TOTAL: 100/100

6. Validation

Passed all quality gates: check-structure, check-prose, check-code --strict, check-duplicates --strict, check-claims, and make test.


PR created automatically by Jules for task 14284939946109495184 started by @mjmirza

…ntic

Co-authored-by: mjmirza <34001140+mjmirza@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

…ntic

Co-authored-by: mjmirza <34001140+mjmirza@users.noreply.github.com>
@mjmirza

mjmirza commented Aug 24, 2026

Copy link
Copy Markdown
Owner Author

Review finding. this branch predates the recent family-17 work and
its own copies of the generated dashboards, indexes, and family README
now conflict with current main. Closing in favor of #441, which pulls
the entry content forward unchanged and regenerates every dependent
file fresh against the current repository state. The entry itself was
reviewed against its cited primary sources and carried forward as is.

@mjmirza mjmirza closed this Aug 24, 2026
@google-labs-jules

Copy link
Copy Markdown
Contributor

Review finding. this branch predates the recent family-17 work and
its own copies of the generated dashboards, indexes, and family README
now conflict with current main. Closing in favor of #441, which pulls
the entry content forward unchanged and regenerates every dependent
file fresh against the current repository state. The entry itself was
reviewed against its cited primary sources and carried forward as is.

Understood. Acknowledging that this pull request is closed in favor of #441 and stopping work on this task.

mjmirza added a commit that referenced this pull request Aug 24, 2026
…agentic (#441)

* feat(patterns) author the Speculative Sampling entry in family 17-ai-agentic

Rebases PR #403's entry onto current main. the branch predated a large
share of the family 17 work that has since landed, so its own copies
of the generated dashboards, indexes, and family README conflicted on
every file except the entry itself. Pulled the content file forward
unchanged and regenerated every dependent file fresh.

Speculative Sampling, also known as Assisted Generation. Leviathan,
Kalman, and Matias 2023 (Google Research) and Chen and colleagues 2023
(DeepMind) introduced the pattern independently. a small draft model
proposes a run of tokens, the target model verifies the whole run in
one forward pass, and a modified rejection sampling scheme guarantees
the accepted output distribution is mathematically identical to
sampling from the target model alone.

Regenerates the family 17 index, BY-PROBLEM and BY-LANGUAGE, the root
README and catalogue-status dashboards.

Verified. check-structure.py 890/890, check-prose.py 931/931,
markdownlint-cli2 0 issues, check-code.py --strict 2846 compiled with
0 failed, check-duplicates.py finds no new collision, validate-refs.py
--strict resolves all 4995 citations including the entry's own arXiv,
vLLM, and TensorRT-LLM sources.

* fix(patterns) regenerate catalogue-status after the refs cache settled

The prior commit ran gen-catalogue-status.py before validate-refs.py
--strict had finished its probe pass, so references_checked locked in
5063 instead of the 5067 the cache actually held once probing
completed. CI's own fresh run of the generator caught the mismatch.
Re-running validate-refs.py first, then the generator last, brings
README, dist/catalogue-status.json, and docs/PROGRESS.md back in sync
with the real cache state.
@mjmirza
mjmirza deleted the feat/speculative-decoding-pattern-14284939946109495184 branch August 24, 2026 10:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant