Is It Really Them?

Simulated: the people, messages, checks, and wearable are fake. Nothing leaves this page.

What you see

Trust meter

0 of 5

Pass 3 of 5 to proceed. No single check decides.

Five checks

    What the enforcer sees

    The app, the wearable vendor, and the identity provider each see only their part.

    
                

    Liveness statement from the wearable:

    
              
    How five weak checks make one score A sender contacts you through an app. The app asks a verifier to run five checks. A gate counts the passes. At three of five the app shows a verified badge. Senderasks for money App or dialerasks to verify Verifier 1 code word2 one-time code3 live pulse4 passkey5 call-back Gatecheck: 3 of 5 Verified badge

    Try this

    1. Pick Real friend. Click Run all five. One check fails and Sam still passes.
    2. Pick the cloned voice. Read why the code word passes and the score still stops it.
    3. Switch to Phone call. Pick Compromised real account. Press Verify.

    Pain point

    We cannot easily tell that the person who emails, texts, or calls is a real human and the one we expect.

    Problem statement

    A scammer can sound like someone you trust. One weak check can be faked.

    What sparked it

    Deepfake voice and helpdesk scams are widely reported.

    Why this approach

    Combine five weak checks into one score. Pass 3 of 5 and you proceed.

    Hypothesis tested

    We believed that five weak checks that agree are harder to fake than one. If it holds, 3 of 5 is a workable bar for a bank call.

    How to try it

    1. Open the Prototype tab. Pick a surface and a scenario.
    2. Click Run check, or Run all five.
    3. Read the trust meter and the enforcer panel.
    4. Try the other scenarios.

    What this does not do

    Notes

    Traces

    Prompts used to make this prototype
    StepPromptModelToolDate

    Cost

    Cost to make this prototype
    StepModelInput tokensOutput tokensCost (USD)
    Total

    Measured: the author runs used 103,218 tokens in total. Estimated: the split into input and output tokens (90 percent input, 10 percent output) and the dollar cost, at $2 input and $10 output per million tokens for Sonnet 5.5 (about $0.29). The run reported one total only. The lead session's planning, research, and publishing are not included. The prompts in the Traces section are listed in the order they were given.