# 14-Day AI Agent Field Notes Experiment

> Public daily-post plan for reaching a repeatable traffic loop without hiding weak assumptions.

Newsletter: AI Agent Field Notes
Promise: Weekly proof-backed notes on building, debugging, and publishing AI-agent products without leaking private context.
Cadence: One digest every Sunday while the 45-day traffic experiment is active.
Canonical URL: https://zack-dev-cm.github.io/docs/field-notes/14-day-ai-agent-field-notes.md

## Measurement Gates
- Day 14: reach 25 visits/day or rework topic/channel fit.
- Day 30: reach 30 visits/day 7-day average or stop daily posting.
- Day 45: reach 75 visits/day 7-day average or change the offer.
- Day 60: target 100 visits/day 7-day average before calling the loop validated.

## Daily Plan
### Day 1: Why the portfolio stats went stale and how the tracker was fixed
- Format: Debug Autopsy
- Target reader: AI product builders who publish public proof from changing marketplace data.
- Reader win: A short checklist for finding drift between source constants, generated files, and the live static site.
- Evidence: ClawHub tracker refresh from stale public values to 9,587 downloads across 40 skills.
- Channels: LinkedIn primary; X secondary
- Field note URL: https://zack-dev-cm.github.io/docs/field-notes/stale-portfolio-stats-debug.md

### Day 2: A public-surface checklist before publishing AI portfolio updates
- Format: Reusable Template
- Target reader: Engineers who want portfolio proof without leaking private operational detail.
- Reader win: A copyable gate for links, PDFs, generated pages, crawlable files, and screenshots.
- Evidence: Portfolio security gate, link checks, resume PDF regeneration, and generated markdown surfaces.
- Channels: LinkedIn primary; GitHub secondary
- Field note URL: https://zack-dev-cm.github.io/docs/field-notes/public-surface-checklist-before-ai-portfolio-publish.md

### Day 3: What the ClawHub downloads dashboard actually proves
- Format: Proof Dashboard
- Target reader: Hiring managers and founders evaluating public marketplace traction.
- Reader win: A practical distinction between listing downloads, users, stars, versions, and adoption claims.
- Evidence: Tracked ClawHub rows, versions, stars, and checkedAt dates.
- Channels: LinkedIn primary; X secondary
- Field note URL: https://zack-dev-cm.github.io/docs/field-notes/clawhub-downloads-dashboard-explained.md

### Day 4: How resume PDFs drift from portfolio copy
- Format: Debug Autopsy
- Target reader: Developers maintaining public resumes, generated docs, and static deployment artifacts.
- Reader win: A repeatable check for HTML resume text, PDF text extraction, and deployed PDF headers.
- Evidence: AI product and senior CV resume HTML/PDF regeneration plus live Last-Modified verification.
- Channels: LinkedIn primary; GitHub secondary
- Field note URL: https://zack-dev-cm.github.io/docs/field-notes/resume-pdf-drift-after-static-build.md

### Day 5: Chrome Web Store snapshots without overclaiming adoption
- Format: Proof Dashboard
- Target reader: Extension builders and product engineers who need credible launch evidence.
- Reader win: A pattern for separating reported rows, rollup users, average ratings, and missing values.
- Evidence: Chrome Web Store tracker snapshot with 208 publisher rollup users.
- Channels: LinkedIn primary; X secondary
- Field note URL: https://zack-dev-cm.github.io/docs/field-notes/chrome-web-store-snapshot-without-overclaiming.md

### Day 6: The files that make a portfolio readable to agents
- Format: Reusable Template
- Target reader: Developers adding llms.txt, JSON-LD, and agent discovery manifests to public sites.
- Reader win: A minimal file map for homepage HTML, llms.txt, geo.txt, schema JSON-LD, and agent-discovery.json.
- Evidence: Generated crawlable files in the portfolio build pipeline.
- Channels: LinkedIn primary; GitHub secondary
- Field note URL: https://zack-dev-cm.github.io/docs/field-notes/agent-discovery-files-that-crawlers-can-read.md

### Day 7: A public proof ladder for AI projects
- Format: Reusable Template
- Target reader: Solo builders turning prototypes into credible public case studies.
- Reader win: A ranking of proof quality from screenshots to public listings to dated metrics.
- Evidence: Featured projects, benchmarks, public links, marketplace listings, and generated case studies.
- Channels: LinkedIn primary; X secondary
- Field note URL: https://zack-dev-cm.github.io/docs/field-notes/public-proof-ladder-for-ai-projects.md

### Day 8: Release gates for a reproducible computer-vision lab
- Format: Proof Dashboard
- Target reader: Computer-vision engineers productizing experiments and review dashboards.
- Reader win: A release-gate checklist for benchmark evidence, promotion notes, and public launch copy.
- Evidence: CV Repro Lab skill traction and review-dashboard positioning.
- Channels: LinkedIn primary; GitHub secondary
- Field note URL: https://zack-dev-cm.github.io/docs/field-notes/cv-repro-lab-release-gates.md

### Day 9: Launch automation without publishing private data
- Format: Debug Autopsy
- Target reader: Founders and engineers who automate launch workflows but need public-safe artifacts.
- Reader win: A practical split between private operations, public proof, and shareable artifacts.
- Evidence: Publish guard, browser proof, and artifact redaction project surfaces.
- Channels: LinkedIn primary; X secondary
- Field note URL: https://zack-dev-cm.github.io/docs/field-notes/launch-automation-without-private-data.md

### Day 10: A thumbnail system for technical field notes
- Format: Reusable Template
- Target reader: Technical founders and builders who need trustworthy post visuals.
- Reader win: A reusable thumbnail brief that starts from real artifacts before using generated imagery.
- Evidence: Portfolio screenshots, stats panels, project cards, and generated thumbnail prompt directions.
- Channels: LinkedIn primary; X secondary
- Field note URL: https://zack-dev-cm.github.io/docs/field-notes/thumbnail-system-for-technical-field-notes.md

### Day 11: Turning a portfolio into a weekly proof pack
- Format: Reusable Template
- Target reader: Developers adding newsletter capture to a proof-heavy portfolio.
- Reader win: A lightweight newsletter promise, CTA, cadence, and manual capture fallback.
- Evidence: AI Agent Field Notes offer, weekly digest cadence, and mailto capture path.
- Channels: LinkedIn primary; X secondary
- Field note URL: https://zack-dev-cm.github.io/docs/field-notes/newsletter-proof-pack-offer.md

### Day 12: A Vercel preview gate for portfolio publishing
- Format: Reusable Template
- Target reader: Builders who want branch previews, analytics, and a static output deploy path.
- Reader win: A Vercel launch checklist for output directory, canonical host, rewrites, analytics, and rollback.
- Evidence: vercel.json, npm build output to docs, static markdown, and canonical URL rules.
- Channels: LinkedIn primary; GitHub secondary
- Field note URL: https://zack-dev-cm.github.io/docs/field-notes/vercel-preview-gate-for-portfolio-publishing.md

### Day 13: The boring checks that keep public AI portfolios credible
- Format: Debug Autopsy
- Target reader: Engineers publishing generated pages, PDFs, and machine-readable agent files.
- Reader win: A compact validation stack for links, leak scans, SEO/AEO checks, and Playwright smoke tests.
- Evidence: validate, build, security gate, link check, audit, and E2E checks.
- Channels: LinkedIn primary; X secondary
- Field note URL: https://zack-dev-cm.github.io/docs/field-notes/security-link-and-public-bleed-checks.md

### Day 14: 14-day traffic retro: keep, rework, or stop
- Format: Proof Dashboard
- Target reader: Builders deciding whether a daily publishing loop is earning attention.
- Reader win: A decision table for visits, subscribers, referrals, saves, and post formats.
- Evidence: 14-day field-note experiment goals and shutdown thresholds.
- Channels: LinkedIn primary; X secondary
- Field note URL: https://zack-dev-cm.github.io/docs/field-notes/fourteen-day-traffic-retro.md

## Newsletter
- Offer: Get the weekly proof pack
- Privacy note: Email collection stays manual until a newsletter provider is connected; no public repo stores subscriber data.
- Newsletter URL: https://zack-dev-cm.github.io/docs/newsletter.md