TERMINAL://boot.sys
RESUMESCAN PRO v4.2.0
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
> Initializing neural network...
> Loading ATS bypass protocols...
> Connecting to AI providers...
├── OpenAI GPT-4 ............ [OK]
├── Anthropic Claude ....... [OK]
└── Google Gemini .......... [OK]
> Calibrating keyword scanner...
> Mounting secure storage...
> Encryption protocols active
SYSTEM READY
[ PRESS ANY KEY TO CONTINUE ]
RESUMESCAN PRO
HomePricingBadge

LIVE_DEMO

Every number below came from running PVAIO 2.7.0 against a fixture resume + JD, right now, as you loaded this page. No screenshots. If you regenerated this page you'd get exactly the same Merkle root — same inputs, same bytes, forever.

resume: PVAIO strict resumePVAIO strict/verify/d1c5593c9ad0bc21…

Merkle root (this page just minted this, right now)

d1c5593c9ad0bc2104f989f6e575888c44db7d520f830eac22f66963fa382aef

ATS score (deterministic)

94%

weighted across 7 rule-driven categories

Semantic match (BM25)

100%

JD ↔ resume retrieval, local MiniLM layered on

Anchors

19

19 exact · 0 fuzzy · 0 semantic · 0 fabricated

ATS FINDINGS

parsing integrity

Clean structural parse.

100

contact recognition

All contact signals detected.

100

keyword density

Keyword coverage healthy.

100

skill clustering

Skills block is clearly structured.

100

experience relevance

Experience section has structural issues.

90

education match

Education details need tightening.

90

formatting quality

Formatting is inconsistent.

75

PER-SENTENCE ANCHORS

Every generated sentence is classified against the original resume. In this demo the rewrite is a faithful pass-through, so every anchor is exact. A real LLM rewrite would show a mix — fuzzy for paraphrases, semantic for loose matches, and fabricated for lines the model invented without evidence.

exact100%AVERY KIM
exact100%Senior Product Engineer
exact100%avery.kim@example.com | +1 (415) 555-0199 | linkedin.com/in/averykim
exact100%SUMMARY
exact100%Product-focused engineer with 7 years shipping consumer and B2B platforms.
exact100%Led 6 shipping cycles across payments, onboarding, and growth.
exact100%EXPERIENCE
exact100%Zeta Inc - Senior Product Engineer | Mar 2022 - Present
exact100%Shipped a billing migration from Stripe v2023 to v2024 that cut
exact100%checkout abandonment by 31% across 4 markets.
exact100%Owned p95 latency (<= 220ms) for the real-time order pipeline.
exact100%Mentored 4 junior engineers on code review and incident response.
exact100%Acme Labs - Software Engineer | Jul 2019 - Feb 2022
exact100%Built the mobile onboarding flow; lifted D7 retention by 18%.
exact100%Delivered the Stripe Connect integration adopted by 120 merchants.
exact100%SKILLS
exact100%TypeScript, React, Node.js, PostgreSQL, Redis, Kubernetes, GCP, CI/CD
exact100%EDUCATION
exact100%B.Tech Computer Science, BITS Pilani, 2019

PROVENANCE LEDGER

engine_version2.7.0
policy_modestrict
merkle_rootd1c5593c9ad0bc2104f989f6e575888c44db7d520f830eac22f66963fa382aef
signature (HMAC)7b03609da8836188e40946c4fbd7b687c1a1407a513925fe028abaab6b812275
pubkey_sig (Ed25519)fa5639b0fbd941ce1addf1f764aff1a3c4f09cdb33935862a148b0dd961d1d8859482fb3ddb7d8ec46a5a4f103369d9ddcad9d2abe023be151c177b8b222e10d
pubkey_fingerprint6a45bdebf19b0685
issued_at2026-06-20T12:54:48.858Z

What this proves

  • This resume was generated by PVAIO engine 2.7.0 against a specific job description.
  • Every anchor is reproducible: run the same pipeline and you get the same leafHash, the same Merkle root, the same signature.
  • The policy mode is cryptographically bound — nobody can rebrand a permissive ledger as strict. The signature would break.
  • An offline verifier (our pvaio-verify CLI) can confirm all of this without talking to our servers.
Generate your ownSee pricingRecruiter badge