ProofDiff · evidence report

What evidence exists for this change?

A local, evidence-based view of changed code, related tests, deterministic checks, and the places that still need human judgment.

policy-engineworking tree vs HEAD2026-08-12T00:00:00.000Z87f1bc06c60f
?

Unknown

1 changed files · 0 changed symbols · highest risk high

No applicable verification command ran for this file.

Change review queue

Highest-risk files appear first. Expand a file to audit each claim.

policy/access.rego

modified · +4 −0 · unknown

Unknownhigh risk · 75
No changed symbol identified

No applicable verification command ran for this file.

Inspect evidence and reasoning

Evidence

  • Evidence boundary · static-relationship · unsupported-semantics

    ProofDiff could not establish first-class structural semantics for this changed file, so stronger relationship claims were not made. ProofDiff intentionally failed closed at this boundary. Next action: Inspect the file-level and static-analysis limitations; add or connect explicit verification rather than inferring that no tests exist.

    high confidence · limitation

Why review this

  • No verification command was run for this change.
  • No statically related test-like path was found.
  • No first-class language adapter applies.
  • Security-sensitive path name warrants focused human review.

Targeted test outcomes

None observed. Related-file presence alone cannot produce “Related test file passed.”

Statically related test-like paths

None found through resolved static imports or runner qualification.

Calls in changed lines

No parser-observed call site intersects the changed lines.

Estimated impact

No dependent files resolved.

Limits

  • Only file-level analysis is available for this file type.
  • No test-like path or runner-qualified target was related to the change; dynamic imports and runtime dispatch may not be visible statically.

Verification checks

Commands, outcomes, and bounded output from this run.

No supported checks were discovered.

Analysis notes

How to read this: The JSON status verified is displayed as “Related test file passed.” It requires a static relationship, runner qualification, explicit target supply, and at least one non-skipped passing test observed for that exact path—not changed-symbol or changed-line execution, mathematical proof, or a guarantee of safety.