Moving files to Trash is recoverable—but space is not reclaimed yet

Why DiskKind stops at macOS Trash and asks you to verify before permanently emptying it yourself.

Moving an item to Trash changes where it lives, but usually leaves its disk blocks allocated. Capacity returns only after Trash is emptied later.

That delay is useful. It gives you a recovery window: reopen the producing app, verify your projects, and restore anything that was needed. DiskKind records a receipt and can rescan the original scope so the result is visible.

Why DiskKind never empties Trash

Emptying Trash is permanent and may include unrelated items that DiskKind never reviewed. The app therefore performs only Finder-equivalent Trash moves. You remain responsible for a separate, deliberate decision to empty Trash after verification.