# A public-surface checklist before publishing AI portfolio updates

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

Format: Reusable Template
Target reader: Engineers who want portfolio proof without leaking private operational detail.
Primary channel: LinkedIn
Secondary channel: GitHub
Canonical URL: https://zack-dev-cm.github.io/docs/field-notes/public-surface-checklist-before-ai-portfolio-publish.md

## Reader Win
A copyable gate for links, PDFs, generated pages, crawlable files, and screenshots.

## Evidence To Use
Portfolio security gate, link checks, resume PDF regeneration, and generated markdown surfaces.

## Thumbnail Direction
Checklist over a clean terminal screenshot; no synthetic secrets, tokens, or private paths in the image.

## Writer Brief
Make the checklist the artifact. Keep examples public and avoid any internal workflow claims.

## Call To Action
Download the resume or inspect agent-discovery.json

## 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.