Data Nexus

Systems that answer

The route the system takes when it has nothing — designed, tested, and the single most valuable thing in a deployment.

Also called Designed refusal · Fallback · Путь отказа

01/What it means

Every one of these systems will meet questions its material does not cover, on the first day and every day after. What happens then is a design decision, and where nobody has made it the default takes over: the model produces something fluent, because that is what it does when given a question and no answer.

A working refusal has three parts and all three are usually missing. The system has to be able to know it has nothing, which means retrieval must be permitted to return empty rather than always returning its best three passages. It has to say so in a way that keeps the conversation alive rather than ending it. And it has to hand over with the history attached, so the person arriving is continuing something rather than starting fresh.

This practice states it as the invariant on the service that sells these: an agent that will not say it does not know is not an asset. It is a liability that has not yet been triggered.

02/What people get wrong

The refusal path is the least-exercised branch in the system and the one whose failure is most expensive, which is a poor combination. It needs its own test set — questions with no answer in the corpus, questions whose answer is nearly present, questions phrased to sound like ones that are covered — run on every material change. A path nobody has fired is not a path.

How to test it

Knowing the definition is not the same as being able to check the figure. These are the procedures that do the second thing.

Accepting an automated agent
“The agent is trained on your data and ready to go live.” · 45 minutes, 6 questions.
Next

The definitions are the easy part. Whether the figure on your dashboard was computed this way is a different question, and usually the more expensive one.