Skip to content
Peter's Stack
  • Home
  • About
  • Topics
  • Privacy
  • Contact
  • 한국어

Microsoft Decision-1

Why Did the Same Decision API Produce Different Answers? Question Engineering with Microsoft Decision-1 and JEV

October 12, 2026 by Peter
A workbench diagram shows one Business Policy and Taxonomy splitting into JEV and Microsoft Decision-1 question contracts and adapters, then converging at a JavaScript Resolver and final label. A 17-email tuning-set card marks initial 10/17 and final 15/17 matches.

Porting a JEV email classifier to Microsoft Decision-1 exposed an adapter bug, conflicting business boundaries, and regressions across seven tests.

Categories Enterprise AI Tags JEV, Microsoft Decision-1, Question Engineering

Recent Posts

  • The AI Code Review Bottleneck: Why Does Faster Code Generation Create More Work?
  • Why Did the Same Decision API Produce Different Answers? Question Engineering with Microsoft Decision-1 and JEV
  • How Should Enterprises Calculate AI ROI? Measure Cost per Accepted Business Outcome, Not Token Spend
  • Why Can Agent Skills Reduce Performance? Lessons from Microsoft Research and Enterprise AI
  • Agent Skills vs MCP: How SKILL.md Changes the Way AI Agents Work
© 2026 Peter's Stack · About · Contact · Privacy Policy