Jev finding evidence review labels the evidence status of one claimed security effect. Supply a claim and the observations from a test, then compare the returned distribution across observed effect, failed attempt and missing evidence. The result creates a pending local review packet; it does not confirm a vulnerability or execute a probe.
The distinction depends on what happened in the supplied test. An invoice response matters only when the account ownership and returned content support the cross-account claim. A successful help-page response says nothing about invoice access. A scanner warning provides a hypothesis to investigate, while a completed denial supplies evidence about the attempted effect.
The workflow was inspired by an API-collected post about a Jev decision layer in a penetration-testing harness. Its primary paper describes finding adjudication from supplied evidence. This page implements an independent text-evidence demonstration with synthetic accounts and observations. It borrows neither the paper's benchmark nor its production harness.
Paste a concise report into the hero window or choose one of the six original inputs. Keep the claim, test identity and observed result together. For a real integration, code must preserve captured receipts, enforce scope and verify deterministic facts before a semantic judgment reaches a reviewer. A high leading probability cannot replace those controls.