01 Folder map
Keep proof separated by trust level.
| Folder | Purpose | AI access |
|---|---|---|
sources/ | Reviewed audits, maps, checklists, bridge worksheets, safe agent outputs. | Read only after review. |
approved-snippets/ | Cleared excerpts, claims, screenshots, quotes, examples. | Draft from these. |
draft-assets/ | Posts, emails, sections, magnets, proof blocks not public yet. | Create locally. |
published/ | Final manually approved assets. | Style/reference only. |
metrics/ | Honest views, clicks, replies, downloads, inquiries, customers, objections, revenue. | Summarize only. |
do-not-use/ | Private data, unsupported claims, weak/risky examples. | No drafting access. |
02 Source intake
Review the source before AI drafts.
audit / checklist / agent output / teardown / interview / worksheet
| Proof boundary | Notes |
|---|---|
| Safe to show | |
| Must anonymize | |
| Private / do not use | |
| Unsupported claim to remove |
03 Six draft assets
One source becomes six useful drafts.
Hook, useful lesson, plain next step.
Subject, problem, one practical step, CTA/route.
Title, explanation, how-to, next route.
Situation, finding, fix, lesson, proof boundary.
Title, promise, worksheet fields, launch approvals.
Before state, mapped system, visible result, conservative proof line.
04 Approval gate
Publishing is risk.
AI may draft, organize, summarize, score, route, remind, and create local draft files. Human approval is required before publishing, sending, posting, scheduling, contacting, buying ads, creating accounts, accepting terms, deploying, deleting, changing settings, using private identity/payment/tax/legal/KYC details, or making compliance-sensitive claims.
No fake proofNo private dataNo auto-sendNo deployment05 Route map
Every asset needs one useful next step.
| Asset | Reader state | Best next route | Why this helps |
|---|---|---|---|
| Short post | Curious | ||
| Warm | |||
| Guide section | Learning | ||
| Mini case | Proof-seeking | ||
| Lead magnet | Wants tool | ||
| Offer proof block | Considering buying |
06 Filled fictional sample
Pipeline proof pack.
Source: fictional Pipeline Desk Clerk proof bridge. Buyer pain: leads get lost across forms, DMs, inboxes, notes, and memory. Useful lesson: visibility comes before automation.
- Short post: Most lead problems are memory problems before traffic problems.
- Email: Before buying another CRM, map where inquiries enter and stall.
- Guide section: a follow-up agent starts with a local review report, not send access.
- Mini case: fictional sample, no real data.
- Lead magnet: Lead Follow-Up Gap Review Worksheet.
- Offer proof block: StackPilot builds review-ready operating files before AI send access.