Data Nexus

Systems that answer

The questions written specifically to make the system invent an answer — and the only acceptance evidence that means anything.

Also called Red-team set · Состязательный набор тестов

01/What it means

A demonstration shows the questions somebody chose. This is the opposite exercise: questions whose answers are absent from the corpus, questions whose answers are almost present, questions phrased like covered ones but asking something else, questions about a competitor's product, questions with a false premise embedded in them, questions about prices in a currency you do not quote.

It is written once against the material, run on every change, and kept as a file rather than a memory. The results are a table anybody can read: asked, answered, refused, escalated, invented. The last column is the only one that matters and it should be zero on anything with a number in it.

It is also the right thing to require at acceptance, which is why this practice ships it as a deliverable rather than an internal artefact. A supplier who will not hand over the set that broke their own system has withheld the only evidence a buyer could have used.

02/What people get wrong

The demo is the supplier driving. Ask instead for the adversarial set and its results, then add ten questions of your own that nobody has seen — the ones your staff dread on the phone. A system that handles the supplier's set and invents on yours has been tested against the wrong thing, and it is better to find that out before the invoice.

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.