Verify the Evidence
A green exit is not the same as a verified claim. Start by binding the observation to the archived submission manifest and, for repository tasks, the exact frozen-base manifest. Then read the command, network posture, exit status, clipped-output flag, and actual output.
Integrity proves which bytes were exercised. Relevance asks whether that command can observe the behavior being claimed. A passing unit suite does not prove a browser layout; a screenshot at one pinned viewport does not prove accessibility or every screen size.
Unavailable evidence is an honest gap, not a mandatory gate failure. The evidence pack records that the sandbox or screenshot facility could not run, or a command started but timed out. Judges weigh that absence alongside the artifact and other evidence; they do not replace it with a contestant's unsupported success story.
Negative and partial outcomes deserve exact language: “command exited 1 after these checks,” “output was clipped,” or “screenshot unavailable.” State the strongest supported claim, the exclusions, and the remaining uncertainty.