Decision-1, then Haiku 5.5, then a person: a three-tier gate
Add an abstention option to a Decision-1 choice, escalate unsure briefs to Claude Haiku 5.5, and keep people for the rest, before any paid Sume call.

A three-tier gate works like this: Microsoft-Decision-1 answers first and is allowed to say it cannot tell; unsure cases go to Claude Haiku 5.5, which can explain itself in words; anything still unclear goes to a person. Only a clean pass from a tier leads to a paid Sume call. Microsoft's own best-practice list suggests including an abstention option such as cannot tell when the model should not be forced to choose.
Tiers and what each costs you
Haiku 5.5 is priced from $0.10 per million input tokens and $0.50 per million output tokens, per Anthropic's models overview; check its pricing page for long-prompt rates. Its default effort is medium. A decision model returns no text, so the second tier is where a written reason appears.
| Tier | Returns | Use for | Source of the numbers |
|---|---|---|---|
| 1. Microsoft-Decision-1 | Option plus a probability for each option, no rationale | Fast bulk triage of briefs | Microsoft Learn: typed answers, probabilities |
| 2. Claude Haiku 5.5 | Text, with adaptive thinking steered by effort | Briefs the first tier would not settle; write the reason down | Anthropic: from $0.10 / $0.50 per MTok, default effort medium |
| 3. A person | A decision | Anything still unclear, or consequential choices about people | Microsoft: use human review for consequential decisions |
How to wire the abstention
Give the choice question an explicit fourth option and describe it, for example cannot_tell: the brief is missing a subject, length or ratio. Microsoft notes that scores can move with wording and option order, so test both before you set a threshold. Send tier 2 only the brief and the question, not the Sume key, and ask it for one word plus one sentence. Keep tier 2 optional: if you would rather have a person look at every unsure case, drop it and the cost is a short queue.
Where Sume's gates still apply
After the last tier says go, the call to Sume is the same as without any model. On hosted MCP that means an idempotency_key, optionally a dry_run first, and max_spend_credits if you want a ceiling. The gates are described on the tools and gates page. The tiers reduce bad submits; they do not replace those controls.
Sources
Related posts
More in Developers
- Decision-1 picks a video model; check it against Sume's catalog
Let a choice question pick among three model ids, then validate the pick against GET /v1/videos/models and fall back to sume/auto when it is missing.
- Microsoft-Decision-1 returns 422 or 404: deployment name and endpoint
Decision-1 wants your deployment name in `model`, not the model name. A 422 means a bad name or question; a 404 means a wrong endpoint or path.
- Microsoft-Decision-1: gate a text brief before a paid Sume video job
Send the brief to Decision-1 as a choice question, render only on 'render', and fail closed on any error. Python sample using the Foundry systemone path.
- Decision-1 score question: order a Sume render queue by urgency
A Decision-1 score is a probability-weighted index, good for ordering but not an absolute grade. Sort briefs with it, then respect Sume's queue limits.
Written by Sume