Validation certificate export

Delivering AI-assisted work increasingly means being asked, months later, who reviewed it and what they checked. A chat message saying "we looked it over" answers neither question. A certificate carries the pieces a reviewer needs to trust the claim: the draft it covers, the person who signed it, the timestamp, the rules that were enforced, and the claims with the sources they were checked against.

That last part matters most. The certificate does not just assert that checking happened, it lists what was checked, so a reader can spot the claim they disagree with and see which source was recorded for it. It is a record of process, which is what procurement, legal and compliance teams are actually asking for.

A certificate that can be issued at any moment certifies nothing. This one reads the audit record held in this browser and refuses to generate until every extracted claim carries a verified status with a source URL, and every guardrail — edit share, citations, prohibited claims, reviewer, attestation — has passed. If something is missing, the page names it and links to the tool that fixes it.

The gates are computed from the stored record each time the page loads, so editing a claim back to unverified, or breaking a rule, locks the export again.

The certificate records that the listed checks were completed on the draft as submitted, by the reviewer named. It does not certify that the facts are true, that a cited source says what the draft claims, or that the piece meets a legal, medical or financial standard. Keep the automated report and the reviewer's notes alongside it when the stakes are high enough to need both.