# Launch drafts

Drafts for the v0.1.0 public launch. Voice locked to `BRAND.md`. Read
`BRAND.md` before editing anything in this folder — the rules there are
load-bearing.

## Sequencing

1. **Day -3:** Final smoke pass on `axocoatl.ai` and `docs.axocoatl.ai`.
   Confirm marketing-deploy + docs-deploy workflows are green.
2. **Day -1:** Push the v0.1.0 git tag. Wait for the release matrix to
   land binaries on GitHub.
3. **Day 0, 9:00 ET:** Submit to Show HN with `hn.md`.
4. **Day 0, 9:10 ET:** Cross-post to Lobsters with `lobsters.md`.
5. **Day 0, 10:00 ET:** r/rust + r/LocalLLaMA + r/MachineLearning with
   `reddit.md`.
6. **Day 0, 10:30 ET:** Twitter/X thread with `twitter.md`.
7. **Day 0+:** Respond to comments. Don't argue with anyone — answer
   the question and move on.

## Tone for replies

The same voice that's in `BRAND.md` applies in comments. Don't get
defensive. Don't oversell. Don't lecture. If a comment is wrong, the
correct response is one paragraph of fact, not a thread.

If someone compares Axocoatl to another agent framework, the right
response is to explain (briefly) where Axocoatl actually differs — the
lattice, the supervision model, the local-first persistence — and
link to `/why`. Not "no it's not." Not three paragraphs.

If someone compares Axocoatl to a personal coding copilot, the right
response is the same: explain the gap — coding copilots are for a
single developer at a single keyboard; Axocoatl is a runtime for
business workflows that run on their own. Link to `/why`.

## What we don't do at launch

- No paid promotion. No buying upvotes. No coordinated brigading.
- No DMing anyone for amplification. Twitter mutuals can RT if they
  want; we don't ask.
- No demo videos with viral hooks. The product sells the product.
- No "we'll fix that in v0.2" promises about features we don't have
  on the roadmap.
