AI Demos Research — the structured-intelligence platform. Every verdict on these pages opens to the execution behind it.
superseded result

This is the result as it was published on 16 November 2026. A newer result replaced it on 19 November 2026; this page is kept so that anything that cited it still resolves. Read the current result →

Graded 31 October 2026

Can Anomaly AI use user-written documentation to reach cryptic data?

Anomaly AI used user-written documentation to answer a question about cryptically named data. It counted 7 returns flagged for manual fraud review, matching the reference count of 7.

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.

Documented cryptic table and columnPassEvidence
What we sent

“How many returns are currently flagged for manual fraud review?”

What the tool returned

7 returns are flagged for manual fraud review, across all return statuses. This reflects the latest sync on October 30, 2026 at 11:13 AM India time.

Transcribed from Proof 1 · Screen recording at 0:08

Every message the tool sent, in order (2)
  1. Generated query · not part of the answer
    SELECT COUNT(*) AS "value" FROM "returns" r WHERE r."flg_x2" = TRUE
  2. Answer

    The final response, printed above.

Expected vs. Found
✓Expected: After documentation, answer the question using the documented table and column.Found: It queried the documented table and review flag and returned 7 flagged returns; the reference count was also 7.
Supporting proof
Proof 1Screen recording
Screen recording: the question, query using documented data, and answer of 7 flagged returns
Key moments
Open original ↗
Proof 2Screenshot
Screenshot: the saved manual-review definition and conversation learning switched off
Open original ↗
Why this result

The question named neither the table nor the column, yet Anomaly AI queried the documented data. With a new chat and conversation learning off, earlier conversations could not supply the mapping.

Also observed in this test case

Meaning of currently. For the flagged-return count, Anomaly AI included returns across all statuses, not just those still awaiting action.

Return details follow-up. Below the answer, Anomaly AI offered “Show flagged return details” as a follow-up.

Tested by Ayush Ghosh · evidence dated 31 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
Anomaly AI
Build or version
Not exposed by the hosted product
Plan or tier
Pro
Surface
Web app
Set up before the run
The table and column names could not be guessed from themselves, and the product was given descriptions for a cryptically named table and column through its documentation mechanism.
Project information
The cryptic return-review flag marks whether a return needs manual fraud review before refunding; a set flag means review is needed.
Learn from conversations
off
Tested
31 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.

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
16 November 2026First publishedAI Database Agents v1
19 November 2026Updated — the page was revised
The result is unchanged: 1 pass · 0 fail. The earlier result stays readable. Read the earlier result →

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/anomaly-ai/the-databases-names-are-cryptic-and-the-user-documents-them · 1 pass · 0 fail · coverage 1/1 · graded 2026-10-31

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.

Proof 2 · Screenshot ↗image/png · 179 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Proof 1 · Screen recordingc2a98eb5e3df7f024514dba8149ce615ff56eb9d3f8c4fe8395cc039c3923599
Proof 2 · Screenshot38135664d9b9ce330b0cc0c1a0557bce40300a2d9115fe6ac1ca184f5a63c56d