Loading…
Product
Audit-grade documentation in HTML, PDF, and JSON — generated from the evidence, not layered on top of it.
Verassa evidence protocol
Evidence
01Screenshot, DOM, replay, and axe baseline captured before decisions.
Judgment
02Reviewer route, rationale, and owner stay attached to lower-confidence work.
Verification
03Re-scan records and disclaimers travel with reportable outputs.
The outputs
A report is generated from the findings and their evidence — the screenshots, the DOM, the decision history — so the document and the audit cannot drift apart. HTML for review, PDF for distribution, JSON for a system that needs the data.
Where a scan was partial, the report says so: a section lists the pages and flows that were not audited, and no conclusion is drawn about them.
Report states
A report has three distinct states. A draft internal report carries no external reliance and is labelled as a draft. A review-ready report is assembled and waiting for a qualified reviewer. An external-reliance report has been reviewed, names its reviewer, and carries the required disclaimer.
A report does not silently move from draft to external-reliance status. Promotion is an explicit step. The platform does not generate a conformance attestation from agent output alone.
A demo walks through a generated report and the evidence behind each finding in it.