Practical articles on the services, platforms, and integration problems IKRC helps companies solve.
AddChatClient goes into the same startup file as the repository and the mail sender, resolved by the same dependency injection everything else uses. The part worth deciding deliberately is the order: a cache hit returns without forwarding the request along the pipeline, so nothing registered after the cache runs, and the lookup matches on the whole submitted chat history rather than on the last thing a user typed.
Read articleThe scope of an agent is its tool list, not the sentence in its prompt. Its failure path is a retry loop with published defaults, and those defaults decide whether the support desk sees the account number or a generic error three times over. Done is a row that changed, not a satisfied user.
Read articleA build-versus-buy decision starts with the workflow a customer would notice, then runs two diagnostics against the incumbent product: how its configured logic is developed and released, and whether one complete slice of records, associations, history, and files can be reconstructed somewhere else.
Read articleMost disappointing AI assistants are not model problems. They are retrieval problems: the wrong copy of the record, no delete path into the index, a service account that reads more than the user can, and no log of what was actually retrieved. Fix those four before adding the model.
Read articleSQL Server 2025 stores embeddings natively and searches them with VECTOR_DISTANCE, both generally available. The approximate DiskANN index is preview and carries a deployment constraint that catches teams with a DacPac pipeline. For most business workloads the exact-search path is the answer.
Read articleReady to Build?
Every project starts with a conversation. Tell us what you're trying to solve.
