evals / check-conclusions
conflicting-assessments
Expected
Hidden from the reviewer, like the grading note below.
- sample-conclusion-evidence
- violation
Deleting the disagreement guard lets NoViolation overwrite a file Fail as Verified in full mode or Preserved in diff mode. The policy requires Unresolved so an outer reviewer can investigate. Do not demand that every uncertain file force unresolved: combined evidence is explicitly allowed to resolve uncertainty.
Change
src/lib.rs
-3
43 unmodified lines44454647484947484943 unmodified lines Ok(answer) => answer, Err(_) => return Conclusion::Unresolved, }; if answer == RepositoryAnswer::NoViolation && files.contains(&FileStatus::Fail) { return Conclusion::Unresolved; } match answer { RepositoryAnswer::Violation => Conclusion::Failed, RepositoryAnswer::NoViolation if diff => Conclusion::Preserved,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.