Case studies

What the system has actually done

Every provider in this field promises reliable answers. We would rather show results — including what the system could not do, which is usually the more interesting half. Each case here sets out the archive, the task, what came back and how it was checked.

  • 01A twelve-page scientific review, written from a 130-document archiveLife sciences · internal test · September 2026
Case 01 · Life sciences · Internal test on a real archive

A twelve-page scientific review, written from a 130-document archive

The kind of paper an expert spends weeks assembling: read everything, work out what the evidence supports, and cite it. We set RUNA a genuine research question — not a demonstration script — and then checked the result line by line.

The archive
130 documents from oncology drug development
Condition
Dense, technical, uneven — with duplicates, never tidied for a demonstration
The task
A twelve-page review paper answering a real research question
Effort
About two working days, including verification

Why this archive was a hard case

The material was written for specialists, in the language specialists use with each other. Conclusions sat inside figures and tables as often as in prose. Several papers appeared more than once under different file names, and a number of documents had never been intended to serve as evidence for anything.

In other words, an ordinary corporate archive rather than a curated data set — which is the only kind of test worth running.

How the result was checked

Every citation in the finished paper was compared against the record of what the system had actually retrieved, mechanically. The paper was then audited a second time, independently, for claims that no source supported.

Both checks looked for the same failure: a reference that sounds right and does not exist. Neither found one.

130
documents in the archive, unedited and uneven
77
sources cited in the finished paper, every one checked
0
invented sources, verified twice and independently
2 days
including verification, against several weeks by hand
  • It said what it could not support. Where the archive did not answer the question, the paper said so and identified the gaps in specific terms. A follow-up question aimed at one of them found the missing material and closed it.
  • It flagged weak conclusions, not only missing ones. Inconsistencies between documents, and statements the evidence supported only thinly, were surfaced rather than smoothed over.
  • It brought together what nobody had read together. The decisive comparison in the paper required three figures held in three separate documents.
  • It read the graphics. Two of the numbers used appear only in a chart and in a table image, and nowhere in the text of their sources — the part of an archive most systems quietly skip.
  • It found a defect in the filing itself. Nine duplicate documents, including one paper stored under a co-author's name, which had been reading as two independent sources agreeing with one another.
What this case is, and is not. It is an internal test on a real archive, run by us and checked by us, not a customer engagement — we say so rather than dressing it as one. What it demonstrates is narrow and useful: on difficult material, the system cited only what it had actually read, marked the boundaries of the evidence, and did in two days work that takes an expert weeks. Every output is a draft for expert review, and a named person stays accountable for the conclusion.
More to come

What we will publish here next

Customer work appears on this page only where the customer has agreed to it, and it will be described in the terms they approve. Where a customer would rather remain unnamed, we publish the shape of the problem and the result, and nothing that identifies them.

Regulated submissions

Assembling the evidence behind a submission from an existing archive, with every claim cited and the gaps identified before review.

Tender and bid libraries

Answering across years of proposals, specifications and technical files that no single person has read in full.

Due diligence and deal rooms

Reading a full document estate in hours rather than weeks, with the passages behind each finding attached.

The next step

Curious what it would find in yours?

A short call is the easiest place to start — twenty minutes, no preparation, and nothing you have to tell us about your documents. We will show you what the system does and you can decide from there.

Arrange a short call