Stored Identity vs. Generated Presence
Why your “identity” is just a copyable database record — and what comes next.
CAMERA ──→ SST_18PT ──→ PES_4D ──→ 128D_VECTOR ──→ ZK_PROOF
30fps Skeleton Entropy Motion Presence
Local Topology Scoring Signature Verified
◄──────────────── 0 DATA UPLOADED ────────────────►
All processing on-device. Nothing stored.The Identity Crisis Nobody Is Talking About
In 2026, AI can generate your face. Clone your voice. Forge your writing style. Deepfake detection is an arms race — and the defenders are losing.
But the real crisis is deeper than deepfakes. It is architectural.
Every identity system on the internet today — from OAuth to SSO to identity verification — relies on the same primitive: a stored credential. A password. A token. A visual scan. A static hash. These are snapshots. Frozen data. And anything frozen can be copied.
The question no one is asking: what happens when generative AI can reproduce any stored identity credential at scale?
The answer: stored identity becomes worthless. Not because the cryptography fails — but because the physical link between the credential and the human is severed. A perfect copy of a face is not a face. A perfect copy of a voice is not a voice. And a perfect copy of a password is not a human — but it authenticates as one.
The Architecture of Stored Identity
Let's be precise about what "stored identity" means.
A stored identity system works like this: 1. A human presents a credential (password, face, fingerprint). 2. The system captures that credential and stores a representation. 3. Future authentication compares new presentations against the stored representation.
This architecture has a fatal property: the credential is static. Once stored, it becomes a fixed target. Any adversary who can reproduce the credential — whether through theft, synthesis, or replay — can authenticate as the original human.
This is not a bug in implementation. It is a property of the architecture. Stored identity is fundamentally vulnerable because identity is reduced to data — and data is copyable.
AI does not "break" stored identity. AI reveals what was always true: stored identity was never identity. It was always just a password with extra steps.
Generated Presence: A New Primitive
What if identity cannot be stored?
What if it must be continuously generated — by a living entity, in real time, from irreducible biological entropy?
This is the core thesis of MyShape Protocol.
A presence-based identity system works differently: 1. A camera captures skeletal motion at 30 fps — not a single frame, but a continuous stream. 2. A 128-dimensional Motion Signature is extracted across four independent feature groups: kinematics, acceleration, jerk, and jerk spectrum. 3. A Presence Entropy Score (PES) quantifies the depth of biological entropy in the motion. 4. A ZK-presence proof is generated — proving the motion is human without revealing the motion itself. 5. Zero raw data is stored. Zero raw data is uploaded.
The key insight: presence is not data. Presence is a physical property of a living nervous system. It cannot be copied because it is not a file. It cannot be replayed because it requires continuous non-deterministic entropy. It cannot be synthesized because AI models — trained to minimize loss over distributions — systematically suppress the very signal that makes human motion human.
The Entropy Gap: Why AI Cannot Forge Presence
The PES engine measures four dimensions of biological entropy:
Φ_K — Kinematics. Skeletal ratios, joint angle variances, velocity and acceleration statistics. Human motion is stochastic at the millisecond scale.
Φ_A — Acceleration Profile. Hurst exponent. Human acceleration exhibits H ≈ 0.6–0.8 (long-range dependence). AI acceleration exhibits H ≈ 0.5 (uncorrelated noise after smoothing).
Φ_J — Jerk Profile. The third temporal derivative of position. The most unforgeable single kinematic dimension. Human jerk follows approximate 1/f^α scaling (α ≈ 1.0–1.5). AI jerk exhibits α > 2.0 (over-smoothed) or α ≈ 0 (white noise).
Φ_Jspec — Jerk Spectrum. Frequency-domain analysis across 4 bands. Spectral entropy. The AI Paradox: the better AI gets at generating realistic motion, the more aggressively it smooths — and the more detectable it becomes.
The result: a Human—AI PES gap of 0.3960. This gap is not a temporary AI limitation. It is a consequence of how neural networks optimize for visual fidelity. Every improvement in visual realism comes at the cost of spectral fidelity. AI cannot do both.
This is the Entropy Gap Theorem: Pr[AI generates PES ≥ 0.65] → 0.
What This Means For Identity Infrastructure
If you are building any system that needs to know whether a user is human — authentication, KYC, access control, agent delegation — you have two choices:
1. Store a credential. Accept that it can be copied, stolen, or synthesized. 2. Verify presence. Accept only a continuous, entropy-rich signal that cannot be stored.
The second option is harder. It requires real-time computation. It requires camera access. It requires local processing to preserve privacy. But it is the only option that survives the AI era.
MyShape Protocol is the reference implementation of this second option. It is not a product. It is a standard — a set of primitives that any application can adopt.
The protocol is open for inspection. The benchmark results are reproducible. The threat model is published. The code is on GitHub.
We are not asking you to trust us. We are asking you to verify.
To the skeptic: every claim in this essay is verifiable. The benchmark code is on GitHub. The threat model is published. Attack it. We invite adversarial review.
Repository: github.com/myshapeprotocol · Threat Model: myshape.com/papers/threat-model · Live Demo: myshape.com/motion-demo
Discuss this essay on HN or GitHub.