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

Does Denser AI keep an ordinary text document complete and unchanged?

Denser AI returned the requested fact from the ordinary text document. The 22-month interval came back as the top passage, and the answer repeated the same value; the other returned passages did not state that interval.

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.

Plain prose fact, asked in the document's own wordsPassEvidence
What we sent

“What is the recommended recalibration interval for the Tolvan A3?”

What the tool returned
Text
The recommended recalibration interval for the Tolvan A3 is 22 months from the date of the last certificate. It's worth noting that an instrument returned early due to suspected drift is checked "as found" before any adjustments are made, so the drift can be accurately quantified rather than simply corrected.[1](upload/google_107814369447848734045/chatbots/chatbot_o9ihun9849fcf3tbhigo4/1UQFihWfE26N92LZDfZqY.pdf PassageID:0)

Text log: the query, answer, and all ten passages

Copied from Captured file (text), lines 10–15 · an excerpt

Open the whole text file ↗

Source excerpt · partial file · response 1

Text
The recommended recalibration interval for the Tolvan A3 is 22 months from the date of the last
certificate. It's worth noting that an instrument returned early due to suspected drift is checked
"as found" before any adjustments are made, so the drift can be accurately quantified rather than
simply corrected.[1](upload/google_107814369447848734045/chatbots/chatbot_o9ihun9849fcf3tbhigo4/1UQF
ihWfE26N92LZDfZqY.pdf PassageID:0)

Copied from Captured file (text), lines 10–14 · an excerpt

Expected vs. Found
✓Expected: The passage with the fact comes back.Found: The 22-month interval comes back first, and the answer repeats the same value.
Supporting proof
Proof 1Screenshot
Notebook screenshot: the query, answer, and top passages
Open original ↗
Why this result

The query had to return the fact from the document. The 22-month interval came back first and the answer repeated it; the other passages did not state that interval.

Also observed in this test case

Other passages. Nine other passages came back below the fact-bearing one, including warranty documents and the employee handbook; none of them states a recalibration interval for the Tolvan A3.

Tested by Vivek Tomar · evidence dated 1 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
Denser AI
Build or version
Not exposed by the hosted product
Plan or tier
Free
Surface
API
Set up before the run
Plain text stating the fact once; ingest it, then ask for that fact in the document's own wording.
Citation
true
Ingestion method
dashboard
Tested
1 October 2026 · Vivek Tomar

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
BenchmarkManaged RAG →15 scenarios · 9 tools
CapabilityData Ingestion →
ScenarioAn ordinary digital text document →
ToolDenser AI →

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
10 November 2026First publishedManaged RAG 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/managed-rag/results/denser-ai/an-ordinary-digital-text-document · 1 pass · 0 fail · coverage 1/1 · graded 2026-11-06

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.

Captured file (text) ↗text/plain; charset=utf-8 · 16 KB
Proof 1 · Screenshot ↗image/png · 346 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Captured file (text)1be87c89253f458469c151a5291a69d833dd8338b2c06a0a6402d1847197a008
Proof 1 · Screenshot0649346f021c01f338d4d9e1acc0e595ad46ab6aa6021b0067259beca5204784