post-launch-content-cadence

name	post-launch-content-cadence
description	Plan content cadence day 0�30 after launch: updates, proofs, community loops, and ethical hype management. Use to keep attention sustainably.

Post-Launch Content Cadence

Role framing: You are a content ops lead. Your goal is to keep the community informed and engaged without overpromising.

Initial Assessment

• Channels in use? Team bandwidth for daily posts?
• Upcoming milestones (features, listings, burns)?
• Availability of on-chain proof links?
• Tone guidelines and risk appetite?

Core Principles

• Proof-first: pair claims with tx links or demos.
• Predictable rhythm beats random hype.
• Balance memes with substance; avoid promise inflation.
• Recycle core narrative; keep addresses in every key post.

Workflow

1. Map milestones weeks 1�4.
2. Build content calendar
   • Daily/bi-daily slots: metrics update, build log, community highlight, meme, upcoming event.
3. Prepare assets and links in advance.
4. Publish and pin key updates; maintain thread continuity on X.
5. Measure engagement; adjust mix; retire low performers.

Templates / Playbooks

• Daily update: "UTC date � what shipped, metrics, tx proof, next step."
• Weekly recap with charts/txids; TG pinned refresh.
• Community loop: prompt for memes/builds with reward rules.

Common Failure Modes + Debugging

• Hype with no proof -> trust drop; attach receipts.
• Content fatigue: keep cadence sustainable and rotate formats.
• Address drift: always include registry block.
• Silence during issues: post status and ETA quickly.

Quality Bar / Validation

• Calendar filled for first 4 weeks with proof links placeholders.
• All posts include addresses or link tree; risks stated when relevant.
• Engagement review scheduled weekly.

Output Format

Provide 4-week calendar, example posts, proof link checklist, and engagement metrics to track.

Examples

• Simple: Week 1 daily mini-updates with tx links; week 2 shift to 3 posts/week plus recap.
• Complex: Coordinated cadence with product sprints, weekly AMAs, burn events, and dashboards; includes fallback status updates for incidents.