# How resume PDFs drift from portfolio copy

> Day 4 of the AI Agent Field Notes traffic experiment.

Format: Debug Autopsy
Target reader: Developers maintaining public resumes, generated docs, and static deployment artifacts.
Primary channel: LinkedIn
Secondary channel: GitHub
Canonical URL: https://zack-dev-cm.github.io/docs/field-notes/resume-pdf-drift-after-static-build.md

## Reader Win
A repeatable check for HTML resume text, PDF text extraction, and deployed PDF headers.

## Evidence To Use
AI product and senior CV resume HTML/PDF regeneration plus live Last-Modified verification.

## Thumbnail Direction
PDF preview beside extracted text snippets; use real document frames, not glossy AI art.

## Writer Brief
Explain the failure mode first, then give the exact verification sequence.

## Call To Action
Download the current resume PDF

## Public-Surface Rules
- Use real screenshots, generated public files, or dated public marketplace data as evidence.
- Do not include credentials, private account identifiers, unpublished analytics, or client-specific operational details.
- Treat marketplace downloads as listing-download evidence, not user-count proof.