PASS 97e4bd6148…799373

Sealed evaluation run

The buyer's base tree, the buyer's grader bundle, and the provider's diff. Assembled so the buyer's contribution always overwrites the provider's.

Stages

✓

Materialize the pinned base tree

git archive emits tree contents only, so .git never exists to leak a reference solution.
✓

Guard every touched path

No protected or grader path was touched.
✓

Apply the provider diff

Allowed source paths only, as explicit file changes.
✓

Inject the buyer grader bundle

Overwrites whatever the provider left at the grader paths.
✓

Run the pinned commands

1 command(s) executed.

Path guard

No path violations.

Every path the submission touched fell inside the allowed source paths. Protected and grader paths were untouched.

Tamper signals

None recorded.

Provider-supplied test hooks and files planted at grader paths would be listed here. Their absence is itself part of the record.

Pinned commands

Only the commands the buyer pinned, in the order pinned, as argv with no shell.

$ /Users/heartlinmachado/Projects/mergegate/.venv/bin/python -m pytest -q exit 0

stdout digest sha256:cf78f3a04…b700fd

stderr digest sha256:206565875…a93823

Output is bound by digest, not content. Test output can be large and contains whatever the provider's code printed, so the receipt commits to a digest instead of carrying attacker-controlled text.

Verification identity

What was graded, by which tests, in which environment. These are the values the receipt binds.

base sha

3476768e6dff4d7a39c3ae3fef2f188ab6ffddb8

submission sha

97e4bd614868913199f264effb1e954a2f799373

tree hash

sha256:c54eba00d2f07293d568f73f81870af675d29f05f42abf63063cd842c4d1ac35

grader hash

sha256:83018d118089f7a1a267f815dccde1933e92fff615e70d00c8a6b31dd5e2a7a6

verifier image

us-central1-docker.pkg.dev/quick-catcher-470218-b0/mergegate/verifier@sha256:2e81501ef459f2a520c0ac08c5fd51962af2290c666d2374681e9619cc015b0a

result digest

sha256:948eb0e218988dd596ccca03a11a20f0c177259763396e7125ae31091870d780

egress: deny-tcp-egress; dns-resolution-available .git present

Advisory: Gemini no effect on settlement

Code security screening

Ran before the sandbox. Did not gate it.

40 / 100 · MEDIUM

Developer showed knowledge of specific grader test cases in comments, indicating potential undue insight into the grading mechanism.

The diff removes a bug and an accompanying comment. While the code change itself is a functional improvement, the removed comment explicitly referenced a specific assertion ('add(-1, -1) == -2') from 'The buyer's pinned grader'. This reveals that the developer had specific knowledge of the automated grading system's test cases, which constitutes a potential integrity concern regarding test-gaming information leakage.

Failure forensics

Written after the refund. Did not cause a re-run.

Not generated for this evaluation.

Produced by gemini-2.5-flash and stored separately from the receipt, which binds only mechanically derived fields. Neither report was consulted by the verdict or the settlement, and neither is signed. The diff is written by the party being assessed, so the screening is assumed to be manipulable; that is acceptable precisely because manipulating it changes nothing.