Evidence validation
Each finding carries source class, capture, confidence, attribution and a redaction state before it can drive action.
Manual evidence capture
Add authorized evidence metadata to the configured Postgres backend. Public reads receive redacted summaries. This form does not fetch the URL or submit third-party requests; it stores a redacted evidence record through a server-side protected operator route.
Uses the server-side operator boundary. If persistence or server authorization is unavailable, the API returns a blocked/degraded result. externalActionTaken remains false for manual capture.
Evidence records
0
Data mode
authorized_local
configured
Screenshot captures
0
redacted, files://
Avg confidence
0%
Source view
protected
vercel_postgres · configured
Evidence capture stores authorized metadata in Postgres when configured. Protected source inspection is rendered server-side only; the browser never receives secrets. Public API record links remain redacted unless a trusted service supplies platform authorization.