Dishaya / Verification Methodology

What "Verified" Means, Exactly

A trust product should tell you precisely what its badge does and does not promise. Here is ours, in plain language, including the limits.

Updated 8 July 2026 · methodology published before the numbers, on purpose

The promise

Every claim in a Dishaya report is checked against its exact source passage before it is written. A claim that is not actually supported is dropped before it ever reaches the page, and every claim that stays carries a label you can act on. What fails the check is disclosed, never hidden. Every report closes with a Confidence Ledger: how many claims were checked, how many held, and what the run cost. Tapping any claim opens the exact source passage behind it, so you never have to take the label on faith.

The four labels

Claims that fail the check are disclosed in the report, not quietly removed.

What this does not promise

Verification is a rigor tool, not an oracle. It tells you whether a claim is supported by the source it cites, not whether that source is itself correct. A confidently wrong source can still produce a "Verified" label, which is why Dishaya also tracks how reliable different sources tend to be over time. Treat any output as a well-checked draft to build on, not as professional advice. For legal, medical, or financial decisions, have a qualified human review it.

How we hold ourselves to it

We measure how often our labels are right against human judgment, and as the first accounts produce enough real runs to report honestly, we will publish a recurring Verification Accuracy Report with the numbers, whatever they are, as versioned releases. We are publishing this definition first, before the numbers, so the standard cannot be moved later to fit the result.

See It On A Real Report

Ask a real question and watch each claim get checked against its source.

Start Free