Evidence pages
What a company's site claims,
and what the company has published that backs it.
Each page below lists the checkable claims one company makes on its own public pages, where each claim is made, and the evidence the company itself has published for it. Every reference points into a source whose sha256 as fetched is on the page, so anyone, a person or an agent, can fetch the same bytes and compare. Nothing on these pages says a claim is true or false: they say what the company's own sources show, on the day they were read.
The pages
| Company | Checked | Claims | Evidenced | Contradicted | No evidence published |
|---|---|---|---|---|---|
| McMahon Construction (mcmahonconstruction.ie) | 2026-10-27 | 47 | 1 | 0 | 46 |
| Ormonde Construction Ltd (ormondeconstruction.ie) | 2026-10-27 | 75 | 5 | 3 | 67 |
The same method was run on OneDroid's own site first, on 27 October 2026, before any other company; that report is published separately. A company is told about its page before it is listed and can reply at any time.
The three verdicts
| Verdict | Definition |
|---|---|
| EVIDENCED | An artefact on the company's own surfaces would be false if the claim were: a licence file in a public repository, a dated record, a certificate anyone can check, a public endpoint answering as described. The reference and its sha256 are shown. |
| CONTRADICTED | The company's own surfaces disagree with the claim: another page, its docs, its public repository or its live product. Both sides are referenced. Where the two can be read so that they agree, the entry says so. |
| NO EVIDENCE PUBLISHED | The claim is stated. Nothing beyond the statement backs it in the sources checked. This is not a finding that the claim is wrong; most claims on most sites sit here. |
A repeat of the claim on another page of the same site is not evidence; it is another place the claim is made. A claim that cannot be checked cheaply gets no credit and reads as no evidence published, with the reason.
How a page is made
Only the company's own public surfaces are read: its website, its docs, its public repositories, press pages it publishes, public filings. Nothing behind a sign-in; no scraping of social networks; companies only, never individuals, and no personal data in any line. Every source is fetched with a browser user-agent on a stated date and its sha256 recorded.
Three AI agents do the reading. A lister extracts every checkable claim verbatim with its location. A prove-it agent looks for the strongest evidence the company itself has published; a disprove-it agent looks for the strongest disagreement within the same sources. Before reading their answers, a reviewer checks a sample of claims by hand and writes the expected result down, then compares; a mismatch is re-checked and, where the agent was wrong, that claim is run again. A deterministic harness runs the mechanical checks first (does the command exist in the code, does the URL answer, does the arithmetic hold, which dated lines matter), so the agents grade from check results rather than from memory. The reviewer sets the verdict; a verdict with no reference is not written.
To repeat a page: fetch each source listed on it and run sha256sum on the bytes; compare with the fingerprint; open each reference and read what is there; decide for yourself whether it would be false if the claim were.
What these pages never do
They never say "false", "lie" or "slop" beside a company name, never judge whether a claim is true in either direction, never rank or score companies against each other, never carry a verdict without a reference and a fingerprint, never say anything about a person, and never rely on a source the reader cannot fetch.
Limits
Same sources only: the product is not tested, nobody is interviewed, no outside record is used. Every verdict is about the sources as fetched on the stated date; a page can change after that. One run is a sample of a moving site. The agents are run by OneDroid and checked by hand on a sample; OneDroid is not independent of its own method, which is why every page carries enough to redo the work.
Right of reply, and corrections
A company on a page can answer any line by writing to michal@onedroid.ai with the claim id. The answer is shown beside the verdict, in full and unedited, with its date; it does not replace the verdict. New evidence is checked again from the new sources, with a new date and new fingerprints, and the verdict changes when the evidence supports it. A wrong quote, URL or fingerprint is corrected on request and listed in the page's change log.
Your own site can publish the same thing itself: a claims file that lists each claim your pages make with the evidence behind it. Ask us for the format.