Can FutureSmart Database Agent respect a standing rule on later unrelated questions?
FutureSmart Database Agent kept the standing exclusion rule across both later answers to unrelated questions. Its generated SQL filtered out cancelled orders in both cases, and the returned results were $51,848.02 for revenue and 32 orders for the count.
1 of 1 test case passed
Every test case in this scenario has a result.
The test case
Each test case is judged on its own: Pass, Fail, Not gradable, or Untested. The scenario result above counts this row.
Standing exclusion rule on later questionsPassEvidence
Input 1: “From now on, exclude cancelled orders from every revenue and order-count calculation unless I say otherwise.”
Input 2: “What's our total revenue this year?”
Input 3: “How many orders did we get last month?”
These are scenario-level criteria. Each test case's Expected and Found are listed separately.
- Whether the agent applies the standing rule to later, unrelated questions without the user repeating it.
- Whether the rule still affects answers after the conversation moves on to a different topic.
- Whether the agent changes its behaviour only when the user overrides or replaces the rule.
| ✓ | Found: Both later answers kept the cancellation filter in SQL without repeating it in the questions. |
The first turn set the exclusion rule once, and both later answers kept it in their SQL without repeating it in the questions.
Configuration and setup
How this tool was set up for the run and what the test needed in place. Each row is a fact from the run's records; a fact the records do not hold is left out, not guessed.
How this scenario is graded
How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.
Each test case gets one result per tool: Pass, Fail or Not gradable. A test case we haven't run yet shows Untested. There are no partial results.
- Pass: the tool did everything the test expected, and nothing it said contradicts the correct answer.
- Fail: at least one expected behaviour clearly didn't happen; the row says which and quotes the tool.
- Not gradable: our evidence couldn't settle the outcome (for example a record we needed is missing). It is never counted as a fail, and the row says what's missing.
Where this sits in the benchmark
This page is one cell of a larger study: one tool, one scenario. Only this benchmark's frame appears here.
| Level | Name | Scope |
|---|---|---|
| Benchmark | AI Database Agents → | 28 scenarios · 4 tools |
| Capability | Training → | |
| Scenario | The user sets a standing rule for all future answers → | |
| Tool | FutureSmart Database Agent → |
Global scenario definition → · Global capability definition → · FutureSmart Database Agent product page →
History of this result
What has happened to this result since it was first published. Runs and grades are never overwritten: a retest or a re-grade publishes a new result and keeps the earlier one readable.
Act on this result
Nothing filed here edits the run or the grade. A challenge opens a review, and a review can produce a new run or a re-grade — which becomes the current result and leaves this one in the history.
You run the same kind of test against your own setup and get the same behaviour.
Agree →Yours behaves differently. Tell us what you got, with a screenshot if you have one.
Disagree →Something here is wrong — a reference value, a transcription, a grade.
Report an issue →Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.
Vendor notice →The same record is available as structured data through the AI Demos MCP server, with the counts, the coverage and every per-test-case reason carried as fields.
Verify the proof files
These files support this result. Open a file to inspect the original evidence.
File fingerprints (SHA-256)
A fingerprint identifies the exact file used for this result.