Not every finding requires a code change. Sometimes a concern is real but intentional; sometimes the check does not apply to this code. A decision records which case you reviewed and why.
There are two kinds:
- accepted — the concern is real, the code is intentional.
- not-applicable — the check misread this code.
Both ask for a reason. The reason is kept for future reference.
A decision is not a detector fix and it is not permission to hide every similar finding. If the doctor genuinely misread valid code, add that case to the doctor’s fixtures and improve the detector as well.
You decide from the dashboard while you review. Your agent can record decisions too — the agent guide covers its side of it.
What’s remembered
A decision sticks to the finding’s evidence identity, not only its line number. Moving unchanged code within the same file can preserve the decision. File renames are not a current guarantee. Changed evidence, changed doctor meaning, stale source or ambiguous identical occurrences resurface the finding for reassessment.
Changing your mind
Press u on a finding in the dashboard to undo its decision, or use
any-doctor decisions --reverse <key>. Local state lives at
.any-doctor/decisions.local.json; keep it untracked. Inspect and reverse
individual records instead of deleting the file.