1 · Retrieved evidence
Every passage the claim was compared against
2 · Laya's typed question
Question and state (the JSON the page builds)
Exact text Laya reads (its token sequence, decoded)
3 · Source document
How it works
Every document is split into short passages and embedded with all-MiniLM-L6-v2; the vectors live in this browser's IndexedDB. The claim is embedded the same way and a brute-force cosine scan returns the top-k passages. The claim and those passages become the state of one typed question for the Laya decision model, which returns a probability for each option instead of generated text. That probability drives the verdict, and its confidence decides whether the verdict is acted on or held for a person. All of it runs in this tab: no server, no API key.
The Evaluate page runs the same pipeline over all 72 sample claims and scores it against the gold labels.