Architecture

Qualify fallback models against the feature contract, define eligible failures, bound attempts, and make reduced behavior visible to callers.

Compose shared chat-client behavior in .NET without moving feature policy into middleware or hiding streaming, caching, and retry costs.

How to keep an AI-enabled product useful when a dependency fails, without hiding reduced capability or returning unsafe substitutes.

A small ASP.NET Core foundation for model access, validated configuration, tracing, buffered and streaming HTTP contracts, and future AI capabilities.

List a feature’s required model capabilities and check them in one request flow before comparing candidate deployments.

Register .NET AI clients, tools, prompts, and retrieval services with explicit lifetimes, safe request state, and clear disposal ownership.

Design human approval around an exact operation, with reviewable payloads, durable decisions, expiry, and execution checks that survive retries.

How to bound time, tokens, retries, tool calls, and estimated cost across a complete AI execution instead of limiting each call in isolation.

A C# implementation for keeping provider coupling at explicit boundaries while making model capabilities and provider-specific behavior visible.

Why bounded retries help with transient faults but cannot resolve unknown outcomes, partial workflows, or duplicated side effects in AI systems.