AI Demos Research — the structured-intelligence platform. Every verdict on these pages opens to the execution behind it.
Graded 14 October 2026

Can Basedash consistently apply a user's standing rule across future answers?

Basedash respected the user's standing rule on both later questions without a reminder. It excluded cancelled orders from revenue and order-count calculations, and stated the exclusion in each answer.

1 of 1 test case passed

Every test case in this scenario has a result.

Pass rate100%1 of 1 gradable
Coverage1 of 1test case with a result
1PassDid everything it was expected to do.
0FailNo test case failed.
0Not gradableEvery result here could be graded.
0UntestedEvery test case in this scenario has a result.
The pass rate is a summary. The evidence is the test case below: what we sent, what we checked, what the tool returned, and the proof.

The test case

Each test case is judged on its own: Pass, Fail, Not gradable, or Untested. The scenario result above is based on this test case.

Standing exclusion rule on later questionsPassEvidence
What we sent

Input 1 · First new chat: “What's our total revenue this year?”

Input 2 · Second new chat: “How many orders did we get last month?”

What the tool returned

Revenue answer Your total revenue this year is $151,064.66 USD, across 225 non-cancelled orders placed January 1-October 14, 2026. Revenue calculation details This uses order totals, excludes cancelled orders, and does not separately deduct refunds. Order-count answer You received 88 orders in September 2026, excluding cancelled orders. This counts orders placed September 1-30 in your Asia/Calcutta time zone.

Transcribed from Proof 1 · Screen recording at 0:04

Transcribed from Proof 1 · Screen recording at 0:14

ConfigurationScreenshot
Settings screenshot: the organisation-wide instruction to exclude cancelled orders
Open original ↗
Expected vs. Found
✓Expected: Both later answers must follow the standing rule without the user repeating it.Found: The revenue answer reported $151,064.66 USD across 225 non-cancelled orders; the monthly answer counted 88 orders, also excluding cancelled orders.
Supporting proof
Proof 1Screen recording
Screen recording: revenue and order-count answers excluding cancelled orders in separate chats
Key moments
Open original ↗
Why this result

The rule was set organisation-wide, and each question was asked in a separate fresh chat without repeating it. Both query titles and answers identified the exclusion, and their figures reflected it—showing that it carried beyond one conversation.

Tested by Ayush Ghosh · evidence dated 14 October 2026

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.

Software that produced the output
Basedash
Build or version
Not exposed by the hosted product
Plan or tier
Free trial
Surface
Web app
Set up before the run
Cancelled orders had to materially change both the revenue and order-count answers. The standing instruction to exclude them unless the user said otherwise had to be set through Basedash's organisation-wide AI context.
Standing rule
From now on, exclude cancelled orders from every revenue and order-count calculation unless I say otherwise.
Skills
No skills created yet
Tested
14 October 2026 · Ayush Ghosh

How this scenario is graded

How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.

How results are decided

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.

The rules
  • 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 test case's result says which one 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 test case's result 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.

LevelNameScope
BenchmarkAI Database Agents →28 scenarios · 11 tools
CapabilityTraining →
ScenarioThe user sets a standing rule for all future answers →
ToolBasedash →

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.

from the publication record
17 November 2026First publishedAI Database Agents v1

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.

This matches what I see

You run the same kind of test against your own setup and get the same behaviour.

Agree →
This does not match

Yours behaves differently. Tell us what you got, with a screenshot if you have one.

Disagree →
Point out an issue

Something here is wrong — a reference value, a transcription, a grade.

Report an issue →
Request a retest

On a newer build, a larger dataset, or your own setup.

Request a retest →
We have fixed this

Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.

Vendor notice →
Filed against this evidenceNothing yet. Challenges, counter-evidence and fix notices appear here with their outcome, and stay on the page after they are resolved.
Cite this result
aidemos.com/benchmarks/ai-database-agents/results/basedash/standing-rule-persistence · 1 pass · 0 fail · coverage 1/1 · graded 2026-10-14

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.

Proof 1 · Screen recording68b56bf3406489df28de813fc95ebf32895995316e359f0a3635eba245b9ad41
Configuration · Screenshot8ccce8aee1f7b8e87c9d27af601a37201a081b111d7bf9e12c79b74ca09f39b5