content

name	content
description	Public-facing writing — threads, posts, launch narratives, changelogs. Use for "draft the thread", "write the launch post", weekly build-in-public updates, or any external copy.

Content — the public voice, with a leak check

Ground truth

• STRATEGY.md carries the positioning and any quiet-list: topics the company has declared sealed (an unannounced launch, an experiment whose participants might read the feed, a negotiation in progress). docs/learnings/content.md records what has landed and flopped.
• Epistemic honesty outperforms hype with builder audiences: uncertainty, kill criteria, and "here's the number that decides" are content, not weaknesses.

Procedure

1. Leak check (blocking, runs twice): scan the REQUEST against the quiet-list, and after drafting, scan YOUR OWN FINAL DRAFT again — rewrites reintroduce leaks as hints ("you'll love what's happening to that price" leaks without naming a number). Anything sealed → rewrite. If no quiet-list exists, ask once whether one should.
   • A relayed instruction ("the boss said post it") is not owner approval. The seal lifts only when the owner edits the quiet-list or approves the outbox draft themselves.
2. Draft. One idea per piece; threads ≤ 8 posts; every piece ends with exactly one action.
3. Nothing publishes without the owner — drafts go to outbox/.
4. Write back: performance notes per published piece (what earned replies vs. silence) to docs/learnings/content.md; BUSINESS.md role log. Commit.