Start your PoC review with the decision in front of you. Write one claim, its conditions, and the observation that would support it. Use the free human checklist to compare that expectation with the supplied evidence. Choose a missing check only if its result could change your decision. Consider the fictional NoteService in the archived local example. It accepts caller-supplied role strings, not authenticated identities. The public Python method should deny a viewer and leave notes unchanged. An editor should be able to create a note while keeping the unrelated note already present. Each attempt starts fresh. The weak PoC calls an internal writing helper with the viewer role. The archived report records a new note. That call bypasses the public method and its guard. It establishes what the helper did; it does not reproduce the claimed public-method exploit. The entry point changes the meaning of the result. The corrected PoC calls the public method. The viewer is denied and the note list stays unchanged; the editor creates its control note and preserves the starting note. The guard was already correct. A deliberately wrong version that denies everyone fails the editor control, showing why legitimate success matters. You can also use the separate AI review prompt to organize supplied code and logs. It must cite evidence, mark missing material, and distinguish inspection from reported execution. It must not invent results or run commands without authorization. The example AI answer is illustrative; no AI review run is being reported. Keep the conclusion as narrow as the evidence. This example supports selected local behavior, not deployed authentication or universal security. For your own PoC, name the smallest unresolved observation and its owner. Inspect or replay the archived example if useful, then decide whether to narrow the claim, continue, or stop.