Most pentest writeups are great at the finding part and stop there. I kept landing in reviews where the hard question was the opposite one: can you show where you stopped, and why?
So I wrote down the part that usually isn't written down — the scope gate, the stop-at-proof rule, and a record a second person can read without you in the room. It's free, and every card points to a public reference.

The first habit is boring but does the most work: decide the boundary before you touch anything. If a target isn't written in scope, it's out. No "just this once," no "we were only checking." Turning something down isn't the method failing — it's the method working.

The second is stop at proof. For each kind of finding, decide ahead of time what's enough to show it's real, and stop there. Going further doesn't make the work more defensible. It just creates more exposure and a longer story you have to explain later.

The third one surprised me most when I started doing it: write down what you ruled out. Facts in one column, hypotheses in another, ruled-out in a third — suddenly "we were careful" becomes something a reviewer can check instead of take on faith.

None of this is my invention. It maps to frameworks you can look up yourself: NIST SP 800-115, OWASP WSTG/ASVS and the LLM Top 10, MITRE CWE/ATT&CK, and FIRST CVSS v4.0. That's deliberate — you should be able to check the method, not trust me on it. One boundary I want to be explicit about: this is defensive, educational material only. No real targets, no working payloads, no jurisdiction-specific legal advice.

The whole method is free to read: https://friendly-skiff-f57.notion.site/ — SOP, mapping cards, update policy, change log. No paywall on the reading; the paid part is only the fill-in sheets people actually use mid-engagement.
There's also a short, searchable reading hub: https://xuehai120.github.io/the-stop-rule/

How do you record the "we stopped here" decision today — a proper form, or pieced together from memory afterward?