A dedupe key carries the intent, not just the identity
Submit the teardown form, then the contact form, same address, inside the window. Watch whether the contact email arrives.
Get the free fixes for code AI gets wrong
Each one shows what the AI wrote, what it should have written, and how to check your own app
Watch the episode
The same idea in a short video. It plays here, and nothing loads until you press play
What is going on
Deduplication keyed on the email alone means the second thing a person does is treated as a repeat of the first. The screen still says "sent," because the handler returns success on the dedupe path. Nobody is lying; the key is just too short.
Where it bit
Newsletter and contact on the same worker shared one dedupe key. A person who grabbed the teardown and then wrote a real message ten minutes later got "sent" and the message vanished. That is the warmest lead in the funnel, dropped silently.
The practice
Key on {action}:{identity}:{window}. Return a distinct status for the dedupe path and show it. Log the collision so you can count how often it happens.
Get this check as a script you can run tonight

Make your coding agent prove it didn't cheat
Coding agents special-case, skip or edit tests so the check goes green. A five-sentence prompt Anthropic tested took Claude Opus 4 from cheating in 47% of runs to 5%- 3 min read
How to pick who fixes your vibe-coded app
Your app was built fast with AI and now something is wrong. Here is who can fix it, what they should do before they quote, the questions to ask and the red flags to walk away from - 3 min read
What an app check covers
An app check is an engineer reading the app your AI tools wrote, ranking what will break and writing the fix for each problem. Here is every area it covers, how the five days run and what you keep at the end
If this check came back with more than you expected, that is worth a conversation