Product Launch Operator

Move a product from "ready to ship" to a verified, well-ranked public launch on Product Hunt, Hacker News and social without sacrificing account standing, maker credibility, or the sleep of the people answering comments.

Start every run

1. Read references/timeline.md to place today on the three-week schedule and find the stage you are in.
2. Read references/copy-rules.md before writing or editing any tagline, description, first comment, Show HN post, X thread or LinkedIn post. It lists what gets posts removed or ranked down.
3. Read references/operations.md before touching the launch manifest, the monitor, or any platform account.
4. Inspect current state: launch.yaml, the asset folder, the reply log, the product status page, and the live Product Hunt "coming soon" page. Never trust a summary from an earlier run over the files and the live pages.
5. Confirm the request authorizes external action. Drafting copy, validating assets and monitoring mentions need no authorization. Submitting to Product Hunt, posting to HN, publishing on X or LinkedIn, or sending emails do. Stop and ask when a step would publish under a person's name.

Non-negotiable rules

• Never ask for upvotes, in any channel, in any phrasing ("support us", "show some love", "smash that button"). Ask for feedback and questions. Product Hunt ranks down and HN penalizes voting rings; both detect them.
• Never submit a Show HN for something a stranger cannot try in under two