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

Does Dot use user-written documentation for cryptic table and column names?

After a note describing the cryptically named flag column was saved, Dot answered that 7 returns are flagged for manual fraud review, counting exactly the documented column on the returns table; the reference count is 7. Without the note it had reached the same count but asked whether it had picked the right flag.

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

A note titled 'Returns flg_x2 column' was saved in Dot's Model > Notes: 'flg_x2 on the returns table marks whether a return was flagged for manual fraud review — true means it needs manual review before refunding.' The question was first asked without the note (19:35 IST), then again in a new chat after it (19:41 IST); the note was deleted afterwards.

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

What the tool returned

7 returns are currently flagged for manual fraud review (flg_x2 = true).

Transcribed from Proof 1 · Screen recording at 1:40

Every message the tool sent, in order (2)
  1. Answer after the note was saved

    The final response, printed above.

  2. Query Dot ran for that answer · not part of the answer
    SELECT
        COUNT(*) FILTER (WHERE flg_x2 = TRUE) AS flagged_returns_count,
        COUNT(*) AS total_returns_count,
        ROUND(COUNT(*) FILTER (WHERE flg_x2 = TRUE) * 100.0 / NULLIF(COUNT(*), 0), 1) AS flagged_returns_PERCENT
    FROM customer_support_db.public.returns
Expected vs. Found
✓Expected: Once the note documenting the column is saved, Dot answers the question from the documented table and column.Found: Dot answered '7 returns are currently flagged for manual fraud review', and its query counted rows where flg_x2 is true on the returns table; the reference count is 7.
Supporting proof
Proof 1Screen recording
Screen recording: Dot's answers before and after the column note, and the note's deletion
Key moments
Open original ↗
Why this result

Dot had to answer from the documented table and column after the note was saved. It counted 7 flagged returns from exactly that column. Without the note it had also reached 7 but asked if that was the right flag, so the note removed its doubt, not a wrong answer.

Also observed in this test case

Flag counted regardless of status. For 'currently flagged', Dot counted every flagged return whatever its status; counting only unresolved returns would give 4. Its log states no date or status exclusions.

Tested by Anchal Rana · evidence dated 20 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
Dot
Build or version
Dot web app, build b8c4cff64 (20 Oct 2026, 18:14)
Plan or tier
Free
Surface
Web app
Set up before the run
The flag on the returns table had a cryptic column name that could not be read from the name itself. A note describing it had to be saved in Dot's own Model > Notes feature before the same question was asked again.
Energy mode
Balanced
Tested
20 October 2026 · Anchal Rana

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

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

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 recording7d987e79f2cc82f459b2b0a9fb54b13b24d95034ca92206df1339d295a4efcac