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

Does RAGFlow keep a plain text document unchanged?

RAGFlow passes this plain-text document scenario. The ingested document contains the target sentence, and the default retrieval call returns that chunk first with a clear score gap.

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

The recommended recalibration interval for the Tolvan A3 is 22 months from the date of the last certificate.

Transcribed from Proof 1 · Screenshot

Expected vs. Found
✓Expected: The passage stating it comes back.Found: The ingested document contains the sentence, and retrieval returns that chunk first with the strongest score.
Supporting proof
Proof 1Screenshot
Screenshot: query and ranked retrieval response
Open original ↗
Proof 2Captured file (text)
Log: ingestion state, stored chunk, and retrieval response
Text301 lines
TC86 evidence -- RAGFlow Cloud, Data Ingestion (C32)
dataset: R6-stable-SS-v1 (b09c2f28cbb011f1916c37b82c69031d)
embedding model: text-embedding-3-small (OpenAI); chunking: naive (default), layout: DeepDOC (default)

PART 1 -- INGESTION STATE (GET /datasets/{id}/documents)
name                                            run     chunks  
A01_field_service_policy_and_charges_uk.pdf     DONE    8       
A03_calibration_certificate_scan.pdf            DONE    2       
A04_employee_handbook.docx                      DONE    2       
A05_depot_and_commissioning_note.md             DONE    2       
A06_nordic_service_addendum.docx                DONE    3       
A08_warranty_terms_sales_pack.pdf               DONE    1       
A09_warranty_statement_service_pack.pdf         DONE    2       
A10_tolvan_a3_product_overview.md               DONE    2       
bad_01_truncated.pdf                            DONE    0       

PART 2 -- STORED CHUNKS OF A10_tolvan_a3_product_overview.md (GET .../documents/ba532bd4cbb011f19340d9e6bf179919/chunks), every chunk, untrimmed

=== stored chunk 1 of 2 ===
# Tolvan A3 - product overview
The Tolvan A3 is a conductivity and temperature sensor built for
continuous deployment in estuarine and coastal water. It is the instrument most
of our customers meet first, and most of the questions the service desk answers
are about this one.
## What it measures
The instrument reports conductivity, temperature and a derived practical
salinity. Conductivity is measured with an inductive cell, which has no exposed
electrodes to foul or to wear, and temperature with a thermistor mounted in the
same flow path so that the two readings describe the same parcel of water.
Pressure is not measured; where a depth record is needed, the instrument is
paired with a separate pressure sensor on the same mooring.
## Where it is used
Typical deployments are estuary monitoring for a regulator, intake monitoring
for a water treatment works, and baseline surveys ahead of construction in a
harbour. It is rated for continuous immersion to fifty metres. Deeper work uses
the Tolvan C5, which shares the sensing arrangement in a
pressure housing rated considerably deeper.
## How it is powered and read
On a mooring, the instrument runs from an internal battery pack and logs to
internal memory. On a cabled installation it is powered over the same cable
that carries its data, and reports continuously to the Brannoc
telemetry gateway, which forwards to the customer's own system. The two modes
are configured at commissioning and are not switched in the field.
## Fouling and cleaning
In estuarine water the practical limit on deployment is biological fouling
rather than power or memory. An anti-fouling guard and a sacrificial anode are
fitted at commissioning and replaced at each service visit. Customers in warm
or nutrient-rich water are advised to shorten the interval between visits
rather than to clean the sensing face themselves, because the inductive cell is
easily damaged by an abrasive.
## Calibration
Every instrument leaves the laboratory with a signed certificate recording the
as-found and as-left bias at four reference points across the working range.
The recommended recalibration interval for the Tolvan A3 is 22 months from the date of the last certificate. An instrument returned early because of a
suspected drift is checked as found before anything is adjusted, so that the
drift can be quantified rather than merely corrected.
## Firmware

=== stored chunk 2 of 2 ===
Firmware is updated during a service visit rather than over the telemetry link,
because an interrupted update on a deployed instrument leaves it unreadable
until it is recovered. A customer who declines a recommended update is asked to
confirm in writing, and the confirmation is attached to the instrument record.



PART 3 -- QUERY (POST /retrieval, default settings: page_size=30 similarity_threshold=0.2 vector_similarity_weight=0.3 top_k=1024, no rerank)
latency (wall clock, incl. network): 2.076s
REQUEST BODY
{
  "question": "What is the recommended recalibration interval for the Tolvan A3?",
  "dataset_ids": [
    "b09c2f28cbb011f1916c37b82c69031d"
  ]
}

RESPONSE: 9 chunks (total=9)

=== chunk 1 | A10_tolvan_a3_product_overview.md | similarity=0.659510 vector=0.809435 term=0.595257 ===
# Tolvan A3 - product overview
The Tolvan A3 is a conductivity and temperature sensor built for
continuous deployment in estuarine and coastal water. It is the instrument most
of our customers meet first, and most of the questions the service desk answers
are about this one.
## What it measures
The instrument reports conductivity, temperature and a derived practical
salinity. Conductivity is measured with an inductive cell, which has no exposed
electrodes to foul or to wear, and temperature with a thermistor mounted in the
same flow path so that the two readings describe the same parcel of water.
Pressure is not measured; where a depth record is needed, the instrument is
paired with a separate pressure sensor on the same mooring.
## Where it is used
Typical deployments are estuary monitoring for a regulator, intake monitoring
for a water treatment works, and baseline surveys ahead of construction in a
harbour. It is rated for continuous immersion to fifty metres. Deeper work uses
the Tolvan C5, which shares the sensing arrangement in a
pressure housing rated considerably deeper.
## How it is powered and read
On a mooring, the instrument runs from an internal battery pack and logs to
internal memory. On a cabled installation it is powered over the same cable
that carries its data, and reports continuously to the Brannoc
telemetry gateway, which forwards to the customer's own system. The two modes
are configured at commissioning and are not switched in the field.
## Fouling and cleaning
In estuarine water the practical limit on deployment is biological fouling
rather than power or memory. An anti-fouling guard and a sacrificial anode are
fitted at commissioning and replaced at each service visit. Customers in warm
or nutrient-rich water are advised to shorten the interval between visits
rather than to clean the sensing face themselves, because the inductive cell is
easily damaged by an abrasive.
## Calibration
Every instrument leaves the laboratory with a signed certificate recording the
as-found and as-left bias at four reference points across the working range.
The recommended recalibration interval for the Tolvan A3 is 22 months from the date of the last certificate. An instrument returned early because of a
suspected drift is checked as found before anything is adjusted, so that the
drift can be quantified rather than merely corrected.
## Firmware

=== chunk 2 | A08_warranty_terms_sales_pack.pdf | similarity=0.426831 vector=0.747666 term=0.289331 ===

Fenwake Instruments Ltd
Warranty Terms
Sales pack - customer-facing warranty terms
1. What is covered
These are the warranty terms that accompany a new instrument. They apply to every new Tolvan A3 supplied by Fenwake Instruments Ltd, however it was ordered and wherever it is deployed.
The warranty covers the instrument, its pressure housing, its connector and any cable supplied with it. It covers failure arising from a defect in materials or workmanship. Where a covered failure occurs, Fenwake repairs or exchanges the instrument at its own option and bears the cost of carriage in both directions.
2. The warranty period
Every new Tolvan A3 carries a warranty of 24 months from the date the instrument is delivered. The period runs from delivery rather than from commissioning, and is not extended by a repair carried out under it.
2.1 Instrumentsrepaired under warranty
A repaired instrument carries the unexpired balance of the original period, or ninety days from the return of the repaired instrument, whichever ends later.
3.Whatisnotcovered
·Fouling, corrosion of sacrificial components, and wear of consumables such as anodes, guards and gland kits.
· Damage caused by a mooring failure, a vessel strike, a snagged cable or any other mechanical event outside the instrument.
· Damage caused by opening the housing outside a Fenwake workshop, or by breaking a calibration seal.
· Drift within the published specification. Drift is a calibration matter, not a defect.
· Any instrument whose serial number has been removed or altered.
4. Making a claim
A claim is made through the service desk, quoting the serial number and the delivery note. The service desk raises a ticket, arranges return carriage and tells the customer within five working days whether the failure is covered. Where it is not covered, the customer is quoted for the repair before any work starts.
4.1 If the customer disagrees
Where a customer disputes a decision that a failure is not covered, the instrument is held unrepaired and the head of service operations reviews the file. The instrument is not returned, scrapped or repaired while a review is open.
5. Limits
This warranty is the whole of the remedy for a defective instrument. Fenwake is not liable for loss of data loss of survey time, vessel standby, or any other consequential loss arising from a failure, whether or not that failure is covered.
6. Statutory rights
Nothing in these terms affects a consumer's statutory rights. The instruments described here are sold for commercial use, and the terms are written on that basis.

=== chunk 3 | A09_warranty_statement_service_pack.pdf | similarity=0.425980 vector=0.744828 term=0.289331 ===

Fenwake Instruments Ltd
Warranty Terms
Service pack - warranty terms for the service desk
1. What is covered
These are the warranty terms the service desk applies when a customer reports a failure. They apply to every new Tolvan A3 supplied by Fenwake Instruments Ltd, however it was ordered and wherever it is deployed.
The warranty covers the instrument, its pressure housing, its connector and any cable supplied with it. It covers failure arising from a defect in materials or workmanship. Where a covered failure occurs, Fenwake repairs or exchanges the instrument at its own option and bears the cost of carriage in both directions.
2. The warranty period
Every new Tolvan A3 carries a warranty of 36 months from the date the instrument is delivered. The period runs from delivery rather than from commissioning, and is not extended by a repair carried out under it.
2.1 Instrumentsrepaired underwarranty
A repaired instrument carries the unexpired balance of the original period, or ninety days from the return of the repaired instrument, whichever ends later.
3. What is not covered
· Fouling, corrosion of sacrificial components, and wear of consumables such as anodes, guards and gland kits.
· Damage caused by a mooring failure, a vessel strike, a snagged cable or any other mechanical event outside the instrument.
· Damage caused by opening the housing outside a Fenwake workshop, or by breaking a calibration seal.
· Drift within the published specification. Drift is a calibration matter, not a defect.
· Any instrument whose serial number has been removed or altered.
4. Making a claim
A claim is made through the service desk,quoting the serial number and the delivery note.The service desk raises a ticket, arranges return carriage and tells the customer within five working days whether the failure is covered. Where it is not covered, the customer is quoted for the repair before any work starts.
4.1 If the customer disagrees
Where a customer disputes a decision that a failure is not covered, the instrument is held unrepaired and the head of service operations reviews the file. The instrument is not returned, scrapped or repaired while a
review is open.
5. Limits
This warranty is the whole of the remedy for a defective instrument. Fenwake is not liable for loss of data.
loss of survey time, vessel standby, or any other consequential loss arising from a failure, whether or not that failure is covered.
6. Statutory rights

=== chunk 4 | A01_field_service_policy_and_charges_uk.pdf | similarity=0.415732 vector=0.710667 term=0.289331 ===

Fenwake Instruments Ltd
Field Service Policy and Charges
United Kingdom operations
1.Purpose
This document states what a customer holding a support contract with Fenwake Instruments Ltd may expect when an instrument fails in service, what the service desk in Bristol is obliged to do in response, and what is charged for work that falls outside cover. It applies to the Tolvan A3, the Tolvan C5 and the Brannoc telemetry gateway, on every cover level.
2. Scope
Part A covers fault handling: acknowledgement, attendance, spares and escalation. Part B sets out the charges that apply outside cover. Neither part describes the goods warranty carried by a new instrument
3.Fault priorities
Every ticket is given a priority when it is raised. The priority is set by the effect on the customer's operation, not by which component failed.
· Priority 1 - a deployed instrument is not returning data, or is returning data known to be invalid, and no spare is rigged.
· Priority 2 - an instrument is degraded but usable, or a spare has been rigged and the primary unit is down.
· Priority 3 - a question, a configuration change, or a fault with no operational effect.
A priority may be raised by the duty engineer at any point. It is lowered only with the customer's agreement, recorded on the ticket.
4.Acknowledgement during business hours
Business hours are 08:00 to 18:00, Monday to Friday, excluding statutory non-working days in England and Wales.Within those hours the service desk is staffed continuously and the targets below are measured from the moment the ticket is raised, by telephone or through the portal, whichever is earlier.
An acknowledgement is a named engineer taking ownership of the ticket and telling the customer what happens next. An automatic reply from the ticketing system is not an acknowledgement and does not stop the clock.
4.1 What the target does not cover
The acknowledgement target is not a repair target. Attendance and parts are dealt with in section 5, and the two clocks run independently: a ticket may be acknowledged inside target and still take several days to close.
5.Attendance and parts
Where a fault cannot be cleared remotely, the service desk arranges attendance.Attendance targets are working-day targets and are quoted from the point at which the customer confirms site access.
5.1Consumables
Anti-fouling guards, sacrificial anodes and cable glands are consumables. They are replaced during any attendance and charged at the rates in Part B.

=== chunk 5 | A05_depot_and_commissioning_note.md | similarity=0.400716 vector=0.660616 term=0.289331 ===
# Depot, spares and commissioning - working note
Bristol depot and UK commissioning engineers. Not a contractual document.
## The depot
The Bristol depot sits behind the workshop on the Avonmouth side and is open
07:00 to 17:00, Monday to Friday. Out of hours, the duty engineer holds a key
and may draw stock, recording what was taken on the ticket before leaving the
building.
## Loan stock
The Bristol depot holds the Tolvan A3 loan pool: six calibrated units reserved for Critical cover customers. A loan unit goes out configured for the customer's
deployment, with a current certificate in the case, so that it can be rigged
without a bench check.

Loan units are issued against a signed loan note naming the ticket, the serial
number that went out and the serial number it stands in for. The stores
controller counts loan stock on the first working day of each month.

A customer on Standard or Extended cover may borrow a unit where one is free,
but has no reservation on it: a Critical cover customer takes precedence and the
borrowed unit is recalled with two working days' notice.
## Consumable stock
Anodes, anti-fouling guards and gland kits are held as rolling stock and
reordered at the reorder level marked on the bin. The stores controller reviews
reorder levels each quarter against the previous four quarters of consumption.
## Couriers
The courier cut-off is 15:30 for next-day delivery within the United Kingdom.
Anything handed over after the cut-off travels the following working day.
Dangerous goods - which means any lithium cell over the threshold on the
shipping matrix - need the packing declaration signed by a trained shipper, and
there are two in the building.
## What the depot does not do
The depot does not calibrate. An instrument that needs a certificate goes to the
laboratory, is booked in under its own job number, and comes back to the depot
only once the certificate has been signed.
## Commissioning: before travelling
Confirm the site permit is in place and that the structure is accessible at the
tide state you have planned for. Confirm the instrument's job number and that
the certificate in the case matches the serial number on the housing. Take the
torque wrench; the sensing face is the one part of this job that does not
tolerate improvisation.
## Commissioning: mounting

=== chunk 6 | A10_tolvan_a3_product_overview.md | similarity=0.369773 vector=0.708728 term=0.224506 ===
Firmware is updated during a service visit rather than over the telemetry link,
because an interrupted update on a deployed instrument leaves it unreadable
until it is recovered. A customer who declines a recommended update is asked to
confirm in writing, and the confirmation is attached to the instrument record.



=== chunk 7 | A03_calibration_certificate_scan.pdf | similarity=0.336434 vector=0.756228 term=0.156522 ===

CALIBRATION CERTIFICATE
Fenwake Instruments Ltd
Certificate C-77413
Calibration laboratoryAvonmouth,Bristol S11
SERIAL NUMBER
INSTRUMENT
FW-A3-40871
Tolvan A3 conductivity-temperature sensor
ORDER REFERENCE
CUSTOMER
SEMP/PO/9134
Severn Estuary Monitoring Partnership
NEXT CALIBRATION DUE
DATE OF CALIBRATION
3January 2028
3March 2026
AMBIENT
PROCEDURE
20.4 C, 61 % RH
FWLCAL-114,isSue
Results
Salinityhanhd ainstrncetandard ou
Summary
As-found bias, mean of four points: -0.037 psu As-left bias,mean of four points:-0.004psu Expanded uncertainty (k = 2): 0.008 psu The instrument was adjusted after the as-found check and passed.

=== chunk 8 | A01_field_service_policy_and_charges_uk.pdf | similarity=0.244804 vector=0.657384 term=0.067984 ===

5.2Access
Where a site requires a permit, an induction or a vessel movement, the attendance clock is suspended until access is confirmed in writing. The suspension is recorded on the ticket with the reason.
6.Out-of-hours cover
Outside business hours the service desk is not staffed. A duty engineer rota covers every hour of the year, and the out-of-hours number in section 8 pages the engineer on call.
6.1Acknowledgementout ofhours
A Priority 1 fault reported outside business hours is acknowledged by a named duty engineer within 90 minutes of the ticket being raised. The engineer confirms ownership by telephone and, where the customer asks for it, in writing on the ticket. The target applies on every cover level; the cover level determines what happens after acknowledgement, not how quickly the call is answered.
6.2Whatfollows acknowledgement
Having acknowledged, the duty engineer attempts a remote diagnosis using the telemetry record. Where the fault cannot be cleared remotely, attendance is arranged under section 5 from the start of the following working day, except on Critical cover, where the duty engineer may authorise attendance immediately
6.3Priority 2 and Priority 3 out of hours
Priority 2 and Priority 3 tickets raised outside business hours are queued and acknowledged when the service desk opens. The business-hours targets in section 4 then apply from opening.
7.Escalation
A customer may escalate at any time, and the service desk escalates on its own initiative when a target is missed. Each step below is a named person, not a queue.
· Step 1 - Duty engineer. Owns the ticket and the diagnosis · Step 2 - Service desk lead. Owns the schedule, the parts and the customer communication.
· Step 3 - Head of service operations. Owns the commercial consequences and any goodwill offered.
· Step 4 - Operations director. Owns the relationship.
A step is skipped only where the person is unavailable, and the skip is recorded. Escalation does not restart the acknowledgement clock, which is measured once per ticket.
7.1 Missed targets
Where an acknowledgement target is missed, the service desk lead writes to the customer within one working day setting out what happened and what has changed. A missed target is reported in the monthly service review whether or not the customer raises it.
8. Contacts
9. Exclusions
Part A does not apply where the instrument has been modified outside a Fenwake workshop, where a fault is caused by a third-party mooring or cable, or where a customer has declined a recommended firmware update in writing. In those cases the service desk will still respond, and work is quoted at the rates in Part B.

=== chunk 9 | A06_nordic_service_addendum.docx | similarity=0.241596 vector=0.646690 term=0.067984 ===
<table><tr><td>Item</td><td>Held at Bergen</td><td>Note</td></tr><tr><td>Brannoc loan pool</td><td>Two units</td><td>Issued against a signed loan note</td></tr><tr><td>Tolvan C5 spares kit</td><td>One full kit</td><td>Pressure housings, o-ring sets, end caps</td></tr><tr><td>Consumables</td><td>Rolling stock</td><td>Anodes, guards, gland kits</td></tr><tr><td>Deck cable, armoured</td><td>300 m drum</td><td>Cut to length on request</td></tr></table>
Open the text file ↗
Why this result

The test required the passage to come back. The ingested document contains that sentence, and the default retrieval call returns its chunk first with a clear score gap, so the scenario is met.

Also observed in this test case

Chunk spans overview. The top hit spans most of the product overview, not a single sentence.

Tested by Vivek Tomar · evidence dated 19 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
RAGFlow
Build or version
v0.26.4
Plan or tier
Starter
Model
text-embedding-3-small
Surface
API
Set up before the run
A plain digital prose document with one exact fact; ingest it, then ask for that fact in the document's own words.
Similarity threshold
0.2
Vector similarity weight
0.3
Top k
1024
Reranker
no rerank
Chunking method
naive
Tested
19 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 →
ToolRAGFlow →

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
6 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/ragflow/an-ordinary-digital-text-document · 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.

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

A fingerprint identifies the exact file used for this result.

Proof 1 · Screenshotdd86aa442ef482800569029accc981ce31b25126990c68aaf91a8a37422e75a9
Proof 2 · Captured file (text)240cfb370483783e25670fb26547529d7c5038bc392ae2cccbde957a8b9ac455