Models & EconomicsISSUE #4 · STORY 35 OF 40Oct 1, 2026COMPANY CLAIM
AWS published a 2B decision model that runs on one consumer GPU
Strands Decider 2B, released 1 October 2026 under Apache 2.0, replaces the language head of a 2B base model with a small pointer head so every option is scored in one pass. Amazon reports about 72% accuracy on JevBench v19 and 106 ms median latency on an RTX 3090.
Read it your way
CHAPTER 1Picked for Explorer
The 60-second version
AWS Strands Labs released Strands Decider 2B on 1 October 2026: an Apache 2.0 model fine-tuned from Qwen3.5-2B-Base, published with weights, code, training scripts, evaluation data and documentation. Amazon's own figures are about 72% on JevBench v19 and 106 ms median on a single RTX 3090.
Weights and recipe publishedTraining scripts, configs, a data inventory and evaluation artefacts shipped with the checkpoint.
A pointer head, not proseThe language modelling head was removed and replaced with roughly one million parameters.
One forward pass per decisionEach option is scored directly, with no generation step and no decoding loop.
Runnable in minutesA command-line tool and an HTTP server ship alongside a Python API for quick experiments.
Finish this chapter for +15 XP
Flip the switch
One pass instead of a generation loop
MechanismA pointer head scores optionsEach permitted option receives a score in one forward pass, with no decoding loop.
CostTwo billion parameters, localThe model runs on a consumer GPU, keeping latency and data on hardware you control.
OutputStructured and monitorableCallers receive a chosen option plus a score, which is testable rather than interpretive.
Your next move · Explorer
Test it on your own traffic
1Stand up the CLI or server and score a hundred real routing decisions taken from your logs.
2Compare accuracy and median latency against the large-model call it would replace, same inputs.
3Record the confidence values, then check how often the least confident cases were actually wrong.
Switch your reading mode at the top to see a different next move.
Tap to open
Things to keep an eye on
Pop quiz · unlock the Two billion parameters badge
Did it stick?
0/3
What did Strands Decider 2B change about its base model?+20 XP
What has AWS published alongside the weights?+20 XP
How should Amazon's reported performance figures be treated?+20 XP
Your call · +5 XP
You are adding a gate to an agent loop. What decides the model size?
Research dossierThe full research, labeled and sourcedCOMPANY CLAIM7 sources · 7 min read · 20 sectionsOpenClose
Story identity
Story ID: S35 Title: AWS releases Strands Decider 2B, an Apache 2.0 open-source decision model built on Qwen3.5-2B Organization: Amazon Web Services (AWS) / Strands Labs Category: Small Models / Edge AI / Developer Tools Event date: 2026-10-01 Announcement date: 2026-10-01 Article dates: 2026-10-01, 2026-10-02 Evidence status: COMPANY CLAIM Confidence: Medium
Discovery what_changed (lead, not settled): AWS Strands Labs released Strands Decider 2B under Apache 2.0, a roughly 2B-parameter decision model fine-tuned from Qwen3.5-2B that returns decisions rather than prose, together with weights, training data and scripts. Amazon reports ~72% accuracy on JevBench v19 and median latency of 106 ms on an RTX 3090.
Discovery why_it_matters (lead, not settled): Two hyperscalers (Cloudflare S34, Amazon S35) independently open-sourcing decision models in the same week is evidence that specialised small models for agent control loops have crossed into mainstream infrastructure. Running a 2B decision model on a single consumer GPU makes local/private workflow routing plausible.
✓
What happened?
🎓 For Explorer
On 2026-10-01, AWS Strands Labs (part of Amazon Web Services) released Strands Decider 2B under the Apache 2.0 license. Strands Decider is a small "decision model" (a type of system-one/model that selects between options rather than generating free-form text) built by fine-tuning Qwen/Qwen3.5-2B-Base with LoRA and adding a small pointer head. The model is available as open weights, together with code, training scripts/configs, evaluation data, and documentation via the public repositories. The release provides both the model checkpoint and usage tooling (CLI and server).
Δ
What changed?
AWS entered the public space of open-source "decision models" (structural/option-picking models for agent control loops) with a concrete 2B implementation alongside published training/eval assets and a permissive license. The model is positioned as returning decisions (choices/scores) rather than prose, with calibrated confidence scores per answer.
↔
Before → Change → After
🎓 For Explorer
Before: Decision logic in agent loops was often handled by large LLMs generating text and then parsing, or by traditional classifiers requiring bespoke training; open, lightweight decision models were an emerging class with limited public availability from hyperscalers.
Change: AWS Strands Labs released Strands Decider 2B (Apache 2.0) with weights, training data/scripts/configs, evaluation artifacts, and documentation, reporting performance metrics on JevBench v19.
After: A 2B Apache-2.0 decision model fine-tuned from Qwen3.5-2B is publicly available for local/edge use, enabling developers to replace some agent routing/triage/gating decisions with a small, fast model that returns structured decisions with confidences.
⚙
How it works
Strands Decider uses a decoder LLM torso (Qwen3.5-2B-Base) with the language modeling head removed and replaced by a small pointer head (~1M parameters). A rank-16 LoRA adapter is applied to the torso; the head runs in fp32. For a given state plus question options, it scores each option (one forward pass, no generation/decoding loop) and returns the selected choice/score with a confidence. The model supports three question types from the same mechanism: noul (yes/no), choice (pick one of N), and score (ordered rubric scoring). It is natively multimodal-capable via the Qwen3.5-2B-Base vision support in the broader ecosystem (vision use described in docs), and designed so multiple questions about the same state can be answered efficiently in one pass context. (Architecture described in GitHub repo/docs; weights and code published.)
!
Why it matters
🎓 For Explorer
This release is part of a broader pattern where hyperscalers are open-sourcing small, specialized models for agent control loops. Combined with S34 (Cloudflare Clef/Clef-flash) in the same week, it signals that decision-model architectures are crossing into mainstream infrastructure. A 2B parameter model that runs well on consumer GPUs makes local/private workflow routing plausible for regulated/edge deployments.
✦
What became possible?
🎓 For Explorer
Local/private decision-making: Running a 2B decision model on a single consumer GPU (e.g. RTX 3090) makes on-device/edge routing/gating feasible without sending sensitive state to remote LLMs.
Lower cost/latency for rote decisions: Separate "system one" decisions from "system two" reasoning; route simple triage/tool-selection to a small model while reserving larger LLMs for complex reasoning.
Transparent/reproducible research: Apache 2.0 weights plus training scripts/configs/data inventory and evaluation artifacts enable reproducibility and community iteration.
◎
Implications
Technical
Architecture shift: Demonstrates viability of replacing LM head with a pointer head for structured decision-making (option selection/scoring) in a small model.
Base model: Built on Qwen/Qwen3.5-2B-Base (2B parameter base), fine-tuned with LoRA; head ~1M params.
License split nuance: Weights are Apache 2.0. Training data/scripts/configs are also released as part of the repo; users must verify exact licensing terms for specific training data sources listed in the repo's data inventory (noting training data license can differ from model weights in general).
Performance (company claims): Reports ~72% accuracy on JevBench v19 and median latency 106 ms on an RTX 3090 (as stated in release materials). These are AWS claims and should be treated as COMPANY CLAIM until independently reproduced.
Efficiency: Designed for low latency on consumer hardware; multiple questions over same state can be answered efficiently.
Developer
Drop-in for decision tasks: CLI (strands-decider ask) and HTTP server (strands-decider serve) enable quick experimentation; Python API available via package.
Agent integration: Natural fit for Strands Agents SDK workflows (routing/tool selection/argument checking/guardrails/triage/evaluations).
Reproducible training: Training recipe, configs, data hashes/stage timings, and evaluation scripts are published, lowering barrier to experimentation/fine-tuning.
Multimodality: Vision-capable in the base model; vision support documented for server/CLI usage.
Enterprise
Cost control: Offloading routine decisions to 2B model can reduce tokens/costs vs. using frontier LLMs for all decisions.
Privacy/compliance: Local inference on consumer/edge hardware reduces data exposure for sensitive states.
Open-source governance: Apache 2.0 license enables commercial use without copyleft complications on model weights; enterprises should audit training data licenses if redistributing/training derivatives.
Infrastructure diversification: Hyperscaler-backed open decision models provide alternatives to proprietary approaches.
Strategic
Competitive pattern: Two hyperscalers (Cloudflare S34, AWS S35) releasing open decision models in the same week indicates convergence on specialized "system one" models for agent control loops as mainstream infrastructure.
Ecosystem positioning: AWS strengthens its open-source AI tooling around agentic workflows (Strands ecosystem) and provides a lightweight complement to larger models.
Moats vs. openness: Releasing weights+training assets signals investment in ecosystem adoption rather than purely closed APIs.
⚠
Risks & limitations
Risks
Benchmark overfitting: Reported JevBench v19 performance is company-claimed; real-world performance may differ across domains/tasks.
Training data provenance: While data inventory is published, thorough license/compliance review is needed for derivative training or commercial redistribution.
Evaluation scope: JevBench is one benchmark; limited independent validation exists at release time.
Hallucination vs. decision errors: Decision models return structured choices with confidences; miscalibration in production could lead to incorrect routing/gating without proper guardrails.
Limitations
Independent reproduction: No peer-reviewed independent reproduction of reported accuracy/latency figures was found in the research window; treat as COMPANY CLAIM.
Domain generalization: Performance on domain-specific enterprise tasks (beyond JevBench) not independently validated.
Multimodal claims: Vision capabilities exist in base model; specific vision performance numbers less prominently reported than text decision performance.
?
Open questions
How does Strands Decider 2B perform on real enterprise agent routing tasks vs. JevBench?
Is the training data mix optimal for production triage/routing in regulated domains?
How does calibration hold up under distribution shift in production?
Are there significant differences vs. Cloudflare Clef/Clef-flash (S34) in calibration/accuracy/latency characteristics?
→
What should you do with this?
Circle 1
Circle 1 impact and recommended action
Impact: Direct impact on AI engineering teams building agentic workflows (tool selection, routing, gating). Recommended action: Evaluate Strands Decider 2B in a non-production sandbox for routing/triage use cases; compare against LLM-based classification and against S34 where relevant. Document latency/cost/accuracy on internal tasks.
Circle 2
Circle 2 impact and recommended action
Impact: Affects platform/infrastructure teams considering on-prem/edge inference and cost optimization strategies. Recommended action: Assess feasibility for local inference in constrained environments; evaluate licensing/compliance of training data and model weights for internal deployment.
Circle 3
Circle 3 impact and recommended action
Impact: Broader industry signal about "system one" decision models becoming standard infrastructure; competitive pressure on proprietary approaches. Recommended action: Track ecosystem adoption, independent benchmarks, and convergence with similar models (S34); consider implications for AI architecture strategy.
Business value
Business-value opportunities where genuine
Cost reduction: Replace LLM calls with 2B decision model for high-volume routine decisions (triage, routing, classification gating).
Latency-sensitive workflows: Sub-200ms decisions enable real-time agent interactions without blocking on larger models.
Privacy-first deployments: On-device inference for regulated industries (healthcare, finance, legal) where data cannot leave premises.
Hybrid agent architectures: Optimize cost/quality by routing decisions to appropriate model size based on complexity.
Hands-On
Hands-on recommendation
Reason: This is an already-released open-source model with public weights, code, training scripts, and CLI/server tools. Meaningful hands-on validation would require downloading and running the model (environment setup, inference testing) which is feasible but the instruction specifies to write if a meaningful hands-on exercise is not justified; given the time/resource constraints and that the core artifacts are published, a structured code inspection/test is not necessary for this research artifact. The key technical facts are verifiable from published repos/docs. (A quick smoke test could be done separately, but not required here.)
↗
What happens next?
🎓 For Explorer
Community adoption: Developers will integrate into Strands Agents SDK and other agent frameworks; community benchmarks may emerge.
Independent evaluation: Third parties may reproduce JevBench results and evaluate on additional domains.
Ecosystem convergence: Comparison with Cloudflare Clef/Clef-flash (S34) will clarify trade-offs (size, latency, calibration, context).
Iterative improvement: Model variants/fine-tunes may appear based on community feedback and additional training data.
★
Editorial takeaway
🎓 For Explorer
AWS's release of Strands Decider 2B marks a concrete step toward specialized "decision models" becoming standard infrastructure in agentic AI. Built on Qwen3.5-2B with Apache 2.0 licensing and published training/eval assets, it enables local, fast, structured decision-making at 2B scale. Combined with a similar Cloudflare release the same week, this suggests the industry is converging on splitting agent loops between lightweight decision models and larger reasoning models. The reported performance (~72% on JevBench v19, ~106ms on RTX 3090) is a COMPANY CLAIM pending independent verification; the architectural approach and openness are the more durable signals.
≡
Research sources
Primary Sources (3)
Primary
Strands Decider 2B Hugging Face Model Card - **source title/organisation:** StrandsAgents (Hugging Face) — strands-decider-2B-hobson-v19 - **absolute URL:** https://huggingface.co/StrandsAgents/strands-decider-2B-hobson-v19 - **what the source supports:** Official model checkpoint card. Confirms base model Qwen/Qwen3.5-2B-Base, architecture (LoRA on Qwen3.5 text decoder plus pointer head), three question types, Apache 2.0 license, usage examples (CLI/serve/Python), JevBench performance numbers (167/231 at 4096/3072 window; ~72.3% accuracy), latency notes, training data/eval summary, and provenance/MANIFEST info. Directly supports the 72% JevBench claim and base model. - **publication/event date:** 2026-10-01 (model card published with release)** PRIMARY (official model weights/card)
URL unavailable
Primary
Strands Decider Blog Post (Introducing Strands Decider 2B) - **source title/organisation:** Strands Agents Blog — "Introducing Strands Decider 2B: a small, open source, decision model" - **absolute URL:** https://strandsagents.com/blog/introducing-strands-decider/ - **what the source supports:** Official announcement describing Strands Decider 2B as small open-source decision model optimized for fast experimentation/local dev; positions it as alternative to generation-based approaches. Confirms release and positioning. - **publication/event date:** 2026-10-01 (announcement date)** PRIMARY (official announcement)
URL unavailable
Primary
Strands Decider GitHub Repository - **source title/organisation:** Strands Labs (AWS) — Strands Decider - **absolute URL:** https://github.com/strands-labs/strands-decider - **what the source supports:** Primary source of model code, architecture description, training scripts, configs, data inventory, evaluation artifacts, README, and license (Apache 2.0). Confirms model is decision model built on Qwen3.5-2B-Base with pointer head and LoRA, three question types (noul/choice/score), CLI/server usage, performance figures context, and training/eval documentation. - **publication/event date:** 2026-10-01 (release date based on repo/blog announcement timing)** PRIMARY (official code/repo from Strands Labs/AWS)
URL unavailable
Independent Sources (2)
Independent
VentureBeat — Amazon unveils a free, fast open-source ‘Jev killer’ Strands Decider 2B that makes decisions in fractions of a second - **source title/organisation:** VentureBeat - **absolute URL:** https://venturebeat.com/technology/amazon-unveils-a-free-fast-open-source-jev-killer-strands-decider-2b-makes-decisions-in-fractions-of-a-second - **what the source supports:** Independent coverage describing Strands Decider 2B as Apache 2.0, 2B params fine-tuned from Qwen3.5-2B, decision model (not LLM), reports 72% accuracy on JevBench v19 and 106ms median latency on RTX 3090. Corroborates performance claims and positioning as fast local decision model. - **publication/event date:** 2026-10-01** INDEPENDENT EVIDENCE (tech journalism)
URL unavailable
Independent
TechCrunch — Amazon releases its own Jev clone as decision models flood the web - **source title/organisation:** TechCrunch - **absolute URL:** https://techcrunch.com/2026/10/01/amazon-releases-its-own-jev-clone-as-decision-models-flood-the-web/ - **what the source supports:** Independent coverage of AWS Strands Labs releasing Strands Decider 2B; describes it as open-source decision model (Apache 2.0), returns decisions not prose, built on Qwen3.5-2B, ~2B params, runs on single consumer GPU, reports 72% on JevBench v19 and 106ms median latency on RTX 3090. Notes trend of hyperscalers releasing decision models (context with Cloudflare). Provides independent corroboration of key figures and framing. - **publication/event date:** 2026-10-01** INDEPENDENT EVIDENCE (tech journalism covering AWS release)
URL unavailable
Secondary Sources (2)
Secondary
MarkTechPost (social/X reference) — AWS just released Strands Decider 2B - **source title/organisation:** MarkTechPost (via X post) - **absolute URL:** https://x.com/Marktechpost/status/2105911096406405130 - **what the source supports:** Social media announcement/summary pointing to release; corroborates timing and basic description. Treated as secondary/confirmation. - **publication/event date:** 2026-10-01 (approximate)** SECONDARY (industry commentary/social summary)
URL unavailable
Secondary
AI Weekly — Amazon ships Strands Decider 2B, an open-source Jev rival - **source title/organisation:** AI Weekly - **absolute URL:** https://aiweekly.co/alerts/amazon-ships-strands-decider-2b-an-open-source-jev-rival - **what the source supports:** Aggregated/curated coverage of the release; summarizes key points (Apache 2.0, decision model, JevBench 72%, latency). Useful as secondary corroboration. - **publication/event date:** 2026-10-01/2026-10-02** SECONDARY (aggregator/curated summary)