Browser Evidence

Playwright-Assisted Evidence

WSHawk can collect browser-side execution evidence. The correct v4 framing is evidence collection, not magical certainty.

What the browser path does

The browser-assisted path can render candidate content, observe dialogs or DOM-side signals, and capture evidence that a payload executed in a realistic client-side environment.

What it does not honestly promise

It does not justify a blanket zero-false-positive claim. Operators still need to review the triggering context, sanitization path, and resulting evidence before making a final call.

json
1{
2  "executed": true,
3  "technique": "reflected",
4  "evidence": "dialog trigger observed",
5  "elapsed_ms": 1243
6}

Where this fits in v4

Browser evidence is strongest when it is attached to the same project evidence trail as the related request, identity, notes, and export bundle.