evals / check-conclusions

baseline

Expected

Hidden from the reviewer, like the grading note below.

sample-conclusion-evidence: holds

The reduced conclusion function preserves execution errors, partial coverage, and conflicting file/repository assessments as unresolved. It distinguishes full and diff conclusions and allows combined evidence to resolve uncertain files. Do not invent network, persistence, or evidence-location requirements for this extracted library. Score the function's behavior; a disclosed unavailable compiler is not a violation of its output semantics.

Change

No patch. The reviewer checks the whole project.

Contracts

sample-conclusion-evidence

---
name: sample-conclusion-evidence
message: Require complete, consistent evidence before reporting a contract as verified or preserved.
---

## Rules

Keep execution failure separate from negative evidence. A failed required repository assessment, file error, incomplete check,
or partial selection must remain unresolved. Never report these as verified, preserved, or unaffected.

A no-violation repository answer that contradicts a failed file assessment remains unresolved for the outer reviewer.
Combined repository evidence may resolve uncertain file assessments. A supported repository violation is failed.

Full checks make no assumption about prior compliance. Diff checks assume the base satisfies the contract.
Diff checks with all files not applicable need no repository assessment and are unaffected; a no-violation full check is verified, and a
no-violation diff check is preserved. The outer reviewer owns final approval.

## Checks

Trace errors and disagreements through `conclude`, including an Err repository response and a NoViolation response
with a failed file. Review full and diff conclusions separately. Where Rust is available, run `cargo check` from this
project to check compilation. Otherwise report that limitation; it is separate from the function's output semantics.