# Perseus — Embargo & Exclusive Policy

**Last updated:** 2026-05-25

## Default position

**Perseus is open game.** No embargoes, no exclusives, no NDAs. If you want to cover Perseus, cover it.

## When this changes

The default may change if we run a coordinated launch event — e.g. a Show HN paired with a Product Hunt launch and a Pragmatic Engineer post-launch deep dive. In that case, embargo terms would be communicated up front to the specific outlets coordinating. Until you hear otherwise, assume no embargo.

## What we ask (not require)

- **Heads up before publishing.** If you're about to publish, a one-line email is appreciated so we can be ready for traffic / questions. Not required.
- **Link back.** If you cover Perseus, a link to either [perseus.observer](https://perseus.observer) or [github.com/tcconnally/perseus](https://github.com/tcconnally/perseus) helps readers find the project. Not required.
- **Factual accuracy.** If you cite a benchmark number, please verify against the raw JSON in `benchmark/` — the numbers in social posts have rounded; the raw files are authoritative.

## What we won't do

- We won't gate access to the maintainer based on coverage size or publication. A blog with 200 readers gets the same response time as a major publication.
- We won't offer paid coverage, sponsored content, or kickback arrangements.
- We won't dictate framing. If you want to write a "Perseus considered harmful" piece, you're welcome to. We may push back in comments, but we won't ask for edits.

## Quote approval

We do not require quote approval. You can publish quotes from Thomas Connally without sending drafts in advance. If a fact-check question comes up, we'll respond within 24h.

## On-the-record default

Everything we say is on the record unless we explicitly say otherwise during a conversation. We don't do "background" or "deep background" by default; if you need that, ask.
