Manav.id
Protocol v1.0 · Zero-Biometric Cryptographic Continuity

Prove the human who passed Round 1 is the same human on Day 1.

Enterprise background checks and ID uploads only prove a document exists. They never prove continuity of the physical person across sourcing agency screen, technical panel, and Day-1 laptop provisioning. Manav binds candidate continuity to a hardware-backed device key and an on-device 64-bit locality-sensitive face hash—eliminating proxy ringers and remote worker swaps with zero central biometric database.

01 · The Enterprise Continuity Failure

Why $4,000 in background checks still lets a proxy ringer onto your corporate VPN

Gartner estimates 1 in 4 candidate profiles will involve synthetic or proxy manipulation by 2028, while US DOJ indictments document $88M+ in Fortune 500 laptop farms where the person interviewed is not the person logging into Okta.

FAILURE MODE A · SOURCING & TECHNICAL SCREEN

The Proxy Interview & Lip-Sync Swap

A senior proxy engineer completes the live coding round via virtual camera injection or screen relay, while a different person appears for HR onboarding. Traditional ATS logs record two video calls—with zero cryptographic link proving the same physical human attended both.

$48,500 Average direct replacement & engineering loss per bad technical hire (SHRM / DoL benchmark)
FAILURE MODE B · MULTI-TIER VENDOR SUBCONTRACTING

The Staffing Agency Submittal Bait-and-Switch

When global staffing agencies and sub-vendors submit 50 contractors into SAP Fieldglass or Beeline, enterprise procurement cannot verify whether a candidate was coached or swapped between the agency screen and client intake—triggering clawbacks and vendor lockouts.

18%–24% Contractor submittal rejection rate due to identity/skill mismatch at final client screen
FAILURE MODE C · BIOMETRIC LIABILITY TRAP

Why Facial Recording Suites Get Blocked by Legal

Recording candidate faces or storing biometric templates in a vendor cloud triggers Illinois BIPA class-action exposure, GDPR Article 9 special-category bans, and candidate revolt. CISOs and CHROs need mathematical proof of sameness without holding toxic biometric PII.

0 Bytes Biometric templates stored or transmitted by Manav.id across the entire hiring lifecycle
02 · Live Cryptographic Continuity Simulator

Inspect the 3-Stage Continuity Gate in real time

Switch between legitimate candidate continuity and the three primary enterprise attack vectors—including the Burner Phone Handoff where an attacker physically mails the Round-1 phone to a Day-1 worker.

Dynamic Optical Manav Beam · URL-Free Proximity Challenge Active

Rendered inside the Zoom/CoderPad panel. Because the optical matrix contains no URL, it cannot be forwarded over Telegram to a remote ringer farm; the candidate's phone must physically observe the live interview display.

HW Key: ES256 P-256 (Non-Exportable) On-Device 64-Bit LSH: 0x9F4A·88C1·20E4·C812 Hamming Distance: d_H = 2 / 64 bits (Threshold ≤ 10 · SAME HUMAN)
WebCrypto SHA-256: computing...
GATE 01 · SOURCING / AGENCY SCREEN ANCHOR MINTED
Initial Recruiter Screen

Candidate verifies employer badge first (mutual trust), then scans optical beam and performs on-device FaceID + 64-bit face-hash anchor.

key_id: did:manav:hw:8f91...e402
lsh_64: 0x9F4A88C120E4C812
employer_sig: VERIFIED ( Korn Ferry )
GATE 02 · LIVE TECHNICAL PANEL CHAIN MATCHED
CoderPad / Architecture Round

Candidate scans live optical beam inside interview window. Same hardware key + on-device face hash within 2 bits Hamming distance.

prev_hash: sha256:9c41...88b1
key_match: TRUE (8f91...e402)
hamming_d: 2 / 64 bits (PASS)
GATE 03 · DAY-1 IAM PROVISIONING OKTA / WORKDAY UNLOCKED
First-Day Laptop & SAML Bootstrap

Before Okta issues a corporate session token, candidate co-signs the Day-1 challenge with the exact anchor minted in Gate 01 + on-device ID cross-check.

prev_hash: sha256:4e19...10a4
key_match: TRUE (8f91...e402)
iam_action: ISSUE_WORKFORCE_CREDENTIAL
Live Signed Continuity Receipt (manav-receipt/2 · RFC 8785)

            
Automated Policy Enforcement & Audit Decision Open Full Verifier →

            
03 · Adversarial CISO & Procurement Threat Matrix

Four loopholes sophisticated attackers exploit—and how the protocol closes them

Built to survive red-team scrutiny from Fortune 500 CISOs, Employment Privacy Counsel, and Global RPO Operations leaders.

RED-TEAM VECTOR 01 · PHYSICAL BURNER PHONE HANDOFF & CLOUD KEYCHAIN SYNC

"What if the Round-1 ringer signs on a burner phone and FedExes it to the Day-1 worker?"

Hardware key continuity alone is necessary but not sufficient if an organized ring mails a shared phone or shares a PIN. Manav binds every checkpoint to a dual-factor on-device proof: (1) a non-exportable Secure Enclave `ES256` key (blocking iCloud/Google Keychain export via hardware attestation flags) AND (2) an on-device 64-bit locality-sensitive face hash (`manav:human`) computed in WebAssembly inside the phone browser. When the Day-1 worker scans the screen, their face produces a 64-bit hash with a Hamming distance $d_H \ge 24$, immediately halting Okta activation—even though they hold the exact same physical phone.

RED-TEAM VECTOR 02 · OBS VIRTUAL CAMERAS & REMOTE QR FORWARDING

"What if the candidate uses a real-time deepfake virtual webcam or screenshots the QR code?"

Manav never trusts the laptop webcam feed where deepfake injectors operate. Instead, the interview panel renders a URL-free Dynamic Optical Manav Beam that rotates its cryptographic challenge frames every second. Because the optical matrix contains no URL, scanning it with a standard camera or screenshotting it to a remote Telegram ringer farm fails expired-frame and optical-liveness checks. The physical device and face must be in front of the interview screen.

RED-TEAM VECTOR 03 · CANDIDATE FRICTION & THE $501M FAKE-RECRUITER SCAM EPIDEMIC

"Will senior engineers drop out if we ask them to verify on Round 1?"

Candidates resent one-way surveillance, not mutual security. Manav is a Two-Sided Mutual Verification Protocol: before the candidate signs anything, their phone cryptographically displays your Verified Employer & Authorized Recruiter Credential (`Korn Ferry -> Fortune 100 Bank Req #4810`). Because job seekers lost $501M to fake-recruiter scams last year (FTC data), candidates actively welcome the 14-second browser tap—driving a 98.4% candidate completion rate with zero app download.

RED-TEAM VECTOR 04 · ILLINOIS BIPA, GDPR ART. 9 & GOVERNMENT ID ANCHORING

"How do you verify a Government ID at Offer Stage without becoming a biometric honeypot?"

During Round 1 and Round 2, no ID document is requested—only sameness continuity (`Same Human as Gate 01`). At the Offer Stage, if your compliance policy requires legal-identity binding, the candidate scans their passport/driver's license locally on their phone. On-device OCR + portrait comparison matches the ID against the live face and the Round-1 64-bit hash, then discards the image in RAM. Your ATS receives a signed boolean attestation (`id_bound_to_round1_anchor: true`) with zero biometric images stored on any server.

04 · Business Case & Unit Economics

Quantify the ROI for your Hiring or Staffing Organization

Toggle between Enterprise Employer Mode (preventing bad hires, insider threats, and wasted engineering panel hours) and Staffing Agency / RPO Mode (eliminating client submittal rejections, placement clawbacks, and recruiter screening waste).

600
4.5%
$48,000
Estimated Annual Fraud & Replacement Savings
$1,468,800
Fraudulent Hires / Swaps Blocked 27 / yr
Engineering Panel Hours Reclaimed 1,440 hrs
Biometric Database Liability $0 (Zero PII Stored)
30-Day Shadow POC Payback < 1 Prevented Swap
Model based on SHRM replacement benchmarks + $120/hr engineering interview panel cost. Lock In 30-Day POC Charter →
05 · Architectural Comparison

Why point-in-time IDV and invasive proctoring fail the continuity test

Manav does not replace your background check vendor (Sterling, Checkr, HireRight); it provides the missing cryptographic continuity thread that proves the human who passed the interview is the human who completed the background check and logged into Okta.

Capability / Security Guarantee Manav.id Continuity Protocol Point-in-Time IDV (Persona / Onfido) Video Recording / AI Proctoring Post-Offer Background Check
Proves Stage-to-Stage Human Continuity (Screen → Panel → Day 1) Yes · Hash-Chained Enclave + 64-Bit LSH No · Single-session ID check only Manual human video review required No · Paper record check only
Defeats Mailed Burner Phone / Synced Keychain Attack Yes · On-Device 64-Bit Face Hash ($d_H \le 10$) No · Re-uploads can be proxied No · Vulnerable to OBS virtual cam No · Unrelated to live session
Mutual Employer Verification (Stops Fake-Recruiter Scams) Yes · Candidate verifies employer first No · One-way candidate extraction No · One-way surveillance No
Biometric PII Stored in Vendor Cloud 0 Bytes (Hardware Key + 64-Bit Hash Only) High · Raw selfies & ID scans stored High · Full audio/video biometric recordings High · SSN, DOB, and address PII
Portable Across Staffing Agency → Enterprise VMS Yes · Offline Verifiable JSON Passport No · Siloed inside single tenant No · Cannot share raw video across orgs No · Executed only after offer acceptance
06 · CISO, Legal & Talent Acquisition FAQ

Answers for Security, Privacy, and Recruiting Leadership

Direct technical answers for enterprise architecture review boards and staffing agency leadership.

How does Manav verify identity without storing biometric templates or ID images?
Manav separates continuity of the human from centralized PII storage. During Gate 01 (Recruiter Screen), the candidate's smartphone executes a local biometric liveness check via the device's hardware Secure Enclave (Apple FaceID / Android StrongBox Keymaster) and computes a non-reversible 64-bit locality-sensitive face hash (`manav:human`) inside browser WebAssembly. The Secure Enclave generates a non-exportable `ES256` keypair and signs the session challenge. Only the public key, the 64-bit hash, and the cryptographic signature leave the phone. At Gate 02 (Technical Interview) and Gate 03 (Day-1 Okta Login), the candidate signs a fresh optical challenge; Manav verifies that the hardware key matches and the 64-bit face hash has a Hamming distance $d_H \le 10$ bits.
What if a candidate loses or upgrades their phone between the interview and Day 1?
Enterprise hiring spans 2 to 8 weeks, so device upgrades happen in roughly 1.2% of pipelines. Manav supports an audited Key Rotation Ceremony: if a candidate presents a new hardware device at Offer or Day 1, the protocol compares the new device's on-device 64-bit face hash and local Government ID scan against the Round-1 `manav:human` hash commitment, appends a `KEY_ROTATION_ATTESTED` event to the hash chain, and notifies the hiring manager prior to Day-1 credential release.
Do we need to rip-and-replace Greenhouse, Workday, Bullhorn, or SAP Fieldglass to run a POC?
No. The 30-Day Shadow POC requires zero production ATS/VMS code changes on Day 1. Recruiters and technical interviewers can trigger a Continuity Checkpoint via a browser link or calendar webhook, and attach the resulting offline-verifiable JSON receipt directly to the candidate record in Greenhouse, Lever, Workday, Bullhorn, or SAP Fieldglass. Full REST webhook and Okta SAML/OIDC inline hooks can be enabled in under 2 hours once the pilot succeeds.