Ne No Permission

Skip the probe because you lack the consent, authority, or policy clearance to collect it.

You suspect a rival team is quietly duplicating your project, and then you notice a colleague's shared-drive folder is misconfigured and wide open. One click and you'd know everything. The data is available. It is not yours to take, and availability is not permission.

The rule: when consent, authority, privacy, or policy clearance is absent, do not collect, full stop. The cue is that little rationalizing voice explaining why this case is different. Steps: name the missing permission explicitly (this folder wasn't shared with you, and reading it violates both policy and the colleague's trust), then route the underlying question through a legitimate channel: raise the duplication concern with your manager, ask the other team directly, or request the information from someone with authority to share it. What changes is the usefulness of what you learn. Intelligence you can never admit having is radioactive; you can't cite it, act on it openly, or defend decisions built on it. An answer obtained properly can actually be used. The boundary runs the other way too: don't invoke "no permission" as cover for avoiding evidence you could legitimately request but would rather not hear.