JevMade Sign in
← Back to guides

JevMade field notes / Model announcement and worked example

Strands Decider brings set-answer decisions to your computer

The Strands team introduces a small decision model that runs on your computer, compares its reported results with other models and shows it checking a weather assistant’s guessed city.

Original by Marc Brooker, Mike Chambers and Fabio Nonato de PaulaGuardrails

Listen to this guide

JevMade’s plain-English explanation

0:00 /

AI narration

Credits

“Introducing Strands Decider 2B: a small, open source, decision model” by Marc Brooker, Mike Chambers and Fabio Nonato de Paula. Read the original source.

This expanded guide is an AI-narrated adaptation prepared by JevMade. It expands the source’s essential ideas, examples and caveats in JevMade’s own words and is not a word-for-word reading. The synthetic voice does not imitate the author or imply their endorsement.

Our summary

Strands Decider is a small AI model that chooses from supplied answers instead of writing replies. Marc Brooker, Mike Chambers and Fabio Nonato de Paula explain how it can run on your own computer. It belongs to the same broad class as Jev, but it is a separate model.

Their weather example catches an assistant guessing a city the user never named. Before the weather tool runs, Decider checks whether the proposed details came from the user and whether clarification is needed. Ordinary Python code turns those answers into a next step: ask for the city or allow the call.

The team reports tests of accuracy, confidence estimates and speed, not independent guarantees. Its weather example illustrates a hand-picked policy, not proven protection. The decision model runs locally, but the surrounding assistant uses Amazon Bedrock. Developers can study the released code without assuming the whole demonstration works offline.

Key takeaways

  1. Use a decision model for a bounded question; use a text-writing model when you need an explanation or reply.
  2. Check the exact proposed action against what the user said, and keep the rule for allowing it in ordinary code.
  3. Separate local decision processing from the rest of the assistant, and test reported confidence and speed on your own task.

The latency chart uses version 18 while the launch introduces version 19. The example weather tool is a demonstration, and its surrounding assistant needs Amazon Bedrock access. The model’s open-source release does not establish narration rights for the article.

Strands Agents Blog · Original published

Read the original guide Opens the author’s site in a new tab.

Keep this for later

Sign in to bookmark experiments, guides and videos, and keep notes only you can see.

Continue to sign in

We’ll bring you back to this listing.