Scenario in benchmark · Version 1
Existing content is changed
A previously indexed item is changed, and the system should answer with the updated value rather than the stale one.
How the tools performed
Every in-scope tool is visible. Outcomes come from current published Results for this scenario and benchmark version.
No published results for this scenario yet.
No published result does not tell you whether a tool has been tested. Test coverage is shown only for comparable published Results.
| Tool | Published outcomes | Test coverage | Result |
|---|---|---|---|
| No published result · alphabetical | |||
| Denser AI | — | — | No published result |
| Dify | — | — | No published result |
| FutureSmart Document Intelligence | — | — | No published result |
| Llama Cloud | — | — | No published result |
| Onyx | — | — | No published result |
| Vectara | — | — | No published result |
| Vectorize.io | — | — | No published result |
Assessed = Pass + Fail + Not gradable. Gradable = Pass + Fail. Both use the published Result’s pinned-test denominator. — means not publicly available.
Test design
- Pinned test cases
- 1
- Disclosure
- 0 public · 1 withheld
- Capabilities exercised here
- Knowledge Sync
What this scenario evaluates
- Whether the updated value becomes the answer after the source has been refreshed.
- Whether the stale value is no longer treated as current.
- Whether the system shows that it has caught up with the changed source rather than continuing to answer from old indexed content.
Exact wording, inputs, fixture state, expected output and detailed grading remain at the test-case level and may be withheld while the benchmark version is active. The scenario and its evaluation intent are public.
How the results are graded
- Pass: the test-case expectations hold.
- Fail: an expectation demonstrably does not hold.
- Not gradable: the evidence cannot establish the outcome.
Version 1 uses test-case expectations; no scenario rubric is pinned.
Benchmark methodology →