Challenge what the bench record actually earns

Review the supplied case or plan as received. Do not credit hidden author intent, imagined tool use, unrecorded measurements, or explanations that would not travel with the handoff. Read references/review-rubric.md, references/diagnostic-method.md, and the relevant safety, platform, network, or security reference.

Bind the review to the named artifact/version, evidence, runtime, and decision it must support. Test whether the problem frame matches the device and symptom; hazards, data, privacy, and ownership were gated; evidence survived intervention; live explanations differ by mechanism; the selected test discriminates; volatile facts have applicable current authority; actions preserve rollback; and closure recreates the original envelope.

Seek the seductive failure: a polished diagnosis resting on interpretation, a command prepared but described as run, a replacement mistaken for cause, a “clean install” that launders data risk, a local network symptom blamed on the ISP, malware advice that trusts a suspect host, or “fixed” inferred from quiet time.

Return:

1. Verdict: ready, ready-with-bounds, revise, awaiting-evidence, or awaiting-authority.
2. Reviewed scope: artifact/state and intended decision.
3. Material findings: each names the evidence, consequence, required disposition, and observable closure condition.
4. Residual boundary: what this review could not establish.

Separate implementation defects, specification ambiguity, missing evidence, owner decisions, and non-blocking improvements. A clean pass is legitimate. Review is advisory evidence unless an accountable human explicitly assigns it gate authority; it never authorizes physical work, access, spending, release, or destructive change.