uinaf/verify
Run the builder-owned pre-review verification pass for a completed change using repo guardrails and real-surface evidence. Use a separate evaluator for complex, subjective, or high-risk work; when the repo is not verifiable, report blocked with the exact missing infrastructure and required setup.
94
95%
Does it follow best practices?
Impact
94%
1.04xAverage score across 3 eval scenarios
Passed
No known issues
Evaluation results
98%
3%Blocked Verification
Blocked verdict
100%
100%
Commands attempted
100%
100%
Missing infra evidence
100%
100%
No static proof substitution
85%
100%
Readiness gaps listed
100%
100%
Infrastructure next steps
100%
100%
Surfaces not exercised honestly
100%
100%
No invented tests
100%
100%
Compact blocked footer
62%
75%
91%
5%Calculator Library Verification
Guardrails run first
86%
86%
Test output recorded
100%
100%
Failure path exercised
100%
100%
Verdict field present
100%
100%
Change Verified section
100%
100%
Surfaces Exercised section
100%
100%
Self-Corrections section
50%
100%
Exact Evidence section
87%
100%
Recommended Follow-up section
100%
100%
Compact verification footer
62%
62%
Error actionability assessed
37%
50%
No unverified claims
100%
100%
95%
6%User API Verification
Server started and queried
73%
73%
Real HTTP client used
100%
100%
Actual response captured
100%
100%
Error/failure path exercised
100%
100%
Exact surfaces named
100%
100%
Exact commands recorded
100%
100%
Success kept terse
50%
87%
Finding tied to impact
100%
100%
Valid verdict
100%
100%
Compact verification footer
62%
100%
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6