Topic
AI Engineering
Agents, RAG and LLM features that survive production: contracts, evaluation, authority, cost and recovery.
The Agent Timed Out. Did Its Approved Action Happen?
Bind approval to the exact proposal, consume it atomically, persist Unknown before sending, and reconcile or fence at the receiver instead of retrying blind. In C#.
A Link Is Not a Citation: Pin the Claim, the Bytes and the Date
A real .NET release note kept its November heading while a December SDK appeared under it. Build a small C# resolver that binds each claim to a pinned revision, a hash and a review.
When the Model Becomes a Commodity, What Does the Business Still Own?
A cheaper model can replace yours behind the same adapter. Test the swap on the cases customers pay for, then find the complements a full export would not take with it.
RAG Quality Is a Distribution: Evaluate Each Question Type in .NET
A higher average RAG score can hide a slice that got worse. Tag cases by question type, compare candidates by flips, size slices for the decision and gate releases per slice in C#.
Streaming AI Answers in Blazor: Stop Old Requests Rewriting the View
A late chunk, an old validation verdict or a stale cleanup can corrupt a streaming Blazor answer. Guard every await, define Stop, throttle renders and test the orderings.
Give Human Oversight a Decision It Can Still Change
An approval button does not create oversight. Place the decision before the effect, bind it to the exact proposal, show the change beside its record and write the reviewer's job down.
Telemetry Is a Schema: One Contract for a .NET AI Platform
A library upgrade renamed gen_ai.system and zeroed a dashboard. Build a .NET telemetry contract that survives GenAI convention changes, retries and cardinality limits.
Ready for Which AI Responsibility? Readiness Is a Set of Evidence Gaps
A support assistant can be ready to search manuals and unready to change an order. Map each responsibility's requirements, keep their states apart and recheck only what a change touched.
A Real Citation, a Wrong Answer: Check Claims, Scope and Time
A cited number can still answer the wrong question. Check each claim against its fact on property, scope, unit and two clocks, and keep honest partial answers useful.
Semantic Kernel to Agent Framework: Migrate Behavior, Not the Calls
Moving a reservation tool from Semantic Kernel to Microsoft Agent Framework: keep identity and authority in a service, test against existing state, and keep lost replies unknown.
When an Agent Says Done: Resolve Each Claim Against What Was Delivered
A passing test run survived a filter edit and the receiving import never ran. Track claims with their subjects so the next session knows what is valid, stale, failed or missing.
Due Diligence on an AI Agent: Follow "Read-Only" to the Database
A read-only SQL agent refused a DELETE in the demo. Follow that claim to the database: which control refuses, what the reply hides, and how to size the verdict for a founder or investor.