Human Approval as a System Boundary
Design human approval around an exact operation, with reviewable payloads, durable decisions, expiry, and execution checks that survive retries.
Ai-Engineering
Store a source checksum to skip unchanged documents
Compare a document’s source checksum, metadata, and ingestion profile before repeating extraction, chunking, embedding, and index writes.
Keep tool results inside a token budget
Bound every model-visible tool result before it enters the next prompt.
Your First Qdrant Collection
Run Qdrant locally, connect with the official .NET client, and create a collection whose vector size and distance match the embedding model.
Run production evaluations outside the user response path
Hand production samples to a separate evaluation worker instead of making users wait for an evaluator model.
AI Systems Need Runtime Budgets
How to bound time, tokens, retries, tool calls, and estimated cost across a complete AI execution instead of limiting each call in isolation.
Make AG-UI events drive UI state, not assistant prose
Reduce structured AG-UI events into frontend state instead of parsing generated text to control application components.
Version prompts, models, datasets, and evaluation results together
Keep every evaluation result tied to the exact prompt, model identities, dataset, evaluator, and configuration that produced it.
Provider Independence from Day One
A C# implementation for keeping provider coupling at explicit boundaries while making model capabilities and provider-specific behavior visible.
Retries Are Not a Recovery Strategy
Why bounded retries help with transient faults but cannot resolve unknown outcomes, partial workflows, or duplicated side effects in AI systems.