Delete Safety Kit

Build Packet 05. Nothing in this product is deleted before it has been scanned for what it is holding up. One dialogue, three outcomes, decided by the scan — ADR-0019.

← Component gallery Form kit

1 · The three outcomes

The dialogue never asks “are you sure”. It states the consequence, lists what it found, and offers only the action that is honestly available. Reason capture is required in every case — these are exactly the actions an auditor asks about later.

Blocked — the record is in the Activity Log

4,021 log entries and 42 managed clients. Permanent deletion is not offered at all — not offered and disabled, absent. This is what happens for essentially every real operator account, and it is the correct outcome.

Fixable — live links only, no history

42 managed clients and 1 group membership, but nothing in the Activity Log. The count of one reads in the singular (Packet 101). Permanent deletion is offered but disabled, with the repair named.

Clear — nothing refers to it

The account somebody created by mistake ten minutes ago. Permanent deletion is offered, armed by typing the account’s email address. Try pressing Enter before you have typed it.

2 · When things go wrong

A scan that could not be completed must never fall through to “nothing references this”. Not knowing is not the same as knowing it is safe.

The scan itself fails

The dialogue says so, deletes nothing, and offers Try again.

The deletion fails

The message stays inside the dialogue and the dialogue stays open — a message that disappears cannot be an error message.

A slow scan

Two seconds, so the skeleton state is visible in its own frame rather than as a spinner over the page.

3 · What the module receives

The dialogue resolves with the mode, the reason code and the note — or null when nothing happened. Everything below would go to the server, where the whole check is run again (BC-010).

Nothing yet.