Topic
LLM Decisions & Evaluation
Define a model decision, set thresholds from the cost of errors and evaluate results on representative cases.

Local Models and Polish Routing: Evaluate the Errors, Not the Average
A local model changes where inference runs, not what its scores mean. Evaluate English and Polish pairs, separate agreement from correctness, and see why a margin threshold misleads.

Azure Decision APIs: Root, Deployment, Operation and Token Audience
Microsoft-Decision-1 and Azure OpenAI Decisions use different paths, serializers and token audiences. Bind each to one validated C# profile and keep the token inside the deadline.

Native Decision API Clients in C#: Wire Shapes and Stalled Bodies
Build one C# client for System One and OpenAI Decisions that maps answers by meaning, parses strictly, owns one deadline past the headers and reports every failure as a distinct outcome.

From AI Draft to Accepted Work Order: One Service, Real Review
A complete-looking AI draft can pass every validator and still overstate its evidence. Route forms and IChatClient through one service and bind approval to revision and evidence.

Decision APIs: Derive the Threshold From the Cost of Each Error
A probability is not an action. Derive automation and review thresholds from error costs, model imperfect reviewers, rank a scarce queue and check what calibration must hold.

Designing a Decision Contract That Preserves Meaning in C#
Write the rubric first, give choice, predicate and score their own C# types, and reject what a JSON schema cannot see: missing candidates, inconsistent means and duplicate keys.

What a Decision Probability Actually Computes: Logits to Labels
The same {"department":"technical"} can come from generation, a classifier or label scoring. Work through softmax, candidate sets, multi-token labels and schema masks to see what 0.88 means.

Decision APIs in .NET: One Judgment Inside a Working Support Desk
What a decision API is, how it differs from a chat model, why three vendors shipped one in five weeks, and how one bounded judgment fits inside a working .NET support desk where C# owns the action.