Loading…
Product
An approved finding becomes a fix proposal an engineer reviews as a diff — in your workflow, never applied without approval.
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.
From finding to fix
Once a reviewer has approved a finding, Remediation Studio drafts a fix and presents it as a unified diff: the exact change, in context, for an engineer to read, adjust, or reject.
Nothing is applied silently. A fix reaches a codebase the way any change does — through review. The platform does the drafting; the engineer keeps the decision.
Verification
A finding is marked verified only when the diagnostic scan re-runs against the patched build and confirms the barrier is gone. A self-reported fix is not a verified fix.
This is also why the platform never describes a finding as resolved on the strength of a merged change alone — resolution is something verification establishes, not something a commit asserts.
A demo walks a finding through remediation and the verifying re-scan.