Always review before you commit. --dry-run shows you the candidate list with evidence. No surprises. No regrets.
Every serious engineering tool with destructive potential has a dry-run mode. terraform plan. rsync --dry-run. git stash before a rebase. The pattern exists because irreversible actions deserve a preview.
Removing someone from your life โ or adjusting how much of it they have access to โ is irreversible in ways that file deletions usually aren't. Dry-run isn't optional caution. It's mandatory respect for the weight of the decision.
Running a scan surfaces every tracked subject, sorted by priority, with the evidence behind their score:
For each flagged subject you'll see:
Dry-run output isn't a verdict. It's a briefing. Before you act, ask yourself:
If everything checks out and the answer to all of those is "yes, this is accurate" โ then you have your answer.
The estimated false positive rate with dry-run review is under 2%. Without it โ without pausing to actually read the results and apply human judgment โ that rate climbs to roughly 8%. One in twelve. That's not a risk worth skipping the review to avoid.
The most common false positive cause is context the system doesn't have: a subject going through something significant that you know about but didn't flag. The review step is where you apply that knowledge.
Dry-run doesn't contact anyone. It doesn't save to any server. It doesn't create any record outside your own browser. It's a read-only operation โ a look at the state of your data and what the algorithm concludes from it. You are the only one who sees it.