# Launch automation without publishing private data

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

Format: Debug Autopsy
Target reader: Founders and engineers who automate launch workflows but need public-safe artifacts.
Primary channel: LinkedIn
Secondary channel: X
Canonical URL: https://zack-dev-cm.github.io/docs/field-notes/launch-automation-without-private-data.md

## Reader Win
A practical split between private operations, public proof, and shareable artifacts.

## Evidence To Use
Publish guard, browser proof, and artifact redaction project surfaces.

## Thumbnail Direction
Three-column public/private/review diagram over a sanitized release checklist.

## Writer Brief
Make the boundary useful. Avoid mentioning private client names, account details, or hidden docs.

## Call To Action
Open Publish Guard

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