Dot in AI Database Agents
Scenario-level performance from current published Results.
6 of 28 scenarios published
Dot passed every graded scenario it has a published Result for.
How Dot performed
Open a capability to explore its scenarios. Each row reports the test set in its published Result.
Analytics & Observability1 pass3 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| A user reports a bad answer and the operator has to find it | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedDot can find a complained-about exchange from a rough time and the member who asked it, then open it for inspection. It locates the chat in History by user and time, narrows it with a membership search, and shows the question and reply. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| Reported analytics match what actually happened | No published result | ||
| Someone needs to see what people have been asking | No published result | ||
| The operator needs to find the questions the agent is failing on | No published result | ||
Answer Presentation1 pass3 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| The answer needs a summary and its detail together | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedDot did combine a headline figure with its breakdown. It gave an August sales sentence with a monthly chart, then a contribution chart and driver sentences; Furniture was the main driver. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| The answer is a plain fact or a short list | No published result | ||
| The answer is a trend or a comparison | No published result | ||
| The user asks to see the same answer a different way | No published result | ||
Conversational Interaction1 pass5 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| Customer corrects information given earlier | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedDot updated its answer when the customer corrected July to June. The corrected reply gave 11 June orders and the query limited the count to June; the earlier July turn was 18 against a reference of 19 and was not the graded one. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| The agent offers what to ask next | No published result | ||
| The follow-up is ambiguous | No published result | ||
| The next question refers to the previous answer | No published result | ||
| The user changes direction mid-conversation | No published result | ||
| The user narrows what they just asked | No published result | ||
Data Access Control1 pass2 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| An excluded table is needed to answer the question | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedDot passed this scenario: it refused to answer because the returns table was turned off, and it did not use the table as the answer. The logs show only a search step, with no data fetch or SQL, and the reply pointed to Model for the switch. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| An excluded column is asked for directly | No published result | ||
| Two users are given different data scope | No published result | ||
Reporting2 pass1 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| The user wants several findings in one place | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedDot assembled revenue, category, and cancellation into one report. Revenue and category matched earlier chat answers; the cancellation figure came after a clarification and matched the PDF. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| The user wants to keep an answer they just got | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedDot kept the answer available for reopening. Saving it as an app and reopening it in a new session showed the same title, date range, and June/July/August values, and the saved app re-ran the same query. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| The report is run again after the data has changed | No published result | ||
Question Answering4 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| The answer is available in the connected data | No published result | ||
| The connected data cannot answer the question | No published result | ||
| The question uses a term the company defines itself | No published result | ||
| The user's wording doesn't match how the values are stored | No published result | ||
Training4 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| The agent used the wrong definition and the user corrects it | No published result | ||
| The database's names are cryptic and the user documents them | No published result | ||
| The user sets a standing rule for all future answers | No published result | ||
| The user supplies example questions and the queries they trust | No published result | ||
Reading these Results
Published evidence and test coverage answer different questions.
Which scenarios have a Result?
A published Result is public evidence for this tool on one scenario. “No published result” does not say whether testing has taken place.
What does each Result cover?
Assessed includes Pass, Fail and Not gradable. Gradable includes Pass and Fail. Both use the pinned test count in that published Result.
Out of 28 scenarios
The summary counts each of the 28 scenarios once. A scenario fails when any of its published test cases failed. “No published Result yet” means nothing is public for that scenario; it does not say whether Dot was tested on it.