Kit 13 · Don't Click · deliverable · designed and built by I Wayan Usada · fictional company
In this fictional brief: more attack mail reported through the Report button, without more genuine mail landing in the security queue. Proposed measures are on the case page; nothing has been measured.
Awareness training taught slogans. People either act on well-written attacks or start reporting everything, and a security queue full of genuine mail hides the real attacks.
| # | Behaviour | What it looks like | Where the build practises it |
|---|---|---|---|
| 1 | Read the address right to left and stop at the registered name | the name just before the ending decides, not the display name | "Which building?" step on every message; 3D prediction before the trace |
| 2 | Report attacks through the Report button | report, not delete or forward | action step; Report scores 2 on the three attacks |
| 3 | Verify unusual payment or credential requests through a known channel | phone or intranet, never the email's own link | Verify scores 1 everywhere: safe, but slower than needed when the address already decides |
| 4 | Treat genuine mail as genuine | colleague and real IT messages answered normally | two genuine messages; reporting one scores 0, two fails the drill |
It will not replace technical controls. The case page recommends an external-sender banner, a one-click Report button and phishing-resistant MFA alongside it.
Building named 1, action 2 / 1 / 0; 15 maximum; pass = 12 or more, nothing lost, at most one over-flag.
Prefer the source? Download the raw markdown.