> For the complete documentation index, see [llms.txt](https://docs.antivamp.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.antivamp.io/partners/09_checklists.md).

# Checklists

## Conformance checklist

Run `npx antivamp-conformance` (green) and confirm each behavior in your own code path:

* [ ] Your normalization uses the SDK / matches AntiVamp (leet, `$`→S, ASCII, uppercase).
* [ ] Authorized launcher → `allow`, and you proceed.
* [ ] Unauthorized launcher → `block`, and you reject with the reason.
* [ ] You call `verifyValidationDecision` and reject `{valid:false}`.
* [ ] Expired/stale decisions are rejected (no launch on stale `allow`).
* [ ] Tampered decisions are rejected (`bad_signature`).
* [ ] Retries with the same idempotency key return the same result.
* [ ] Webhook signatures verified against the raw body; tamper rejected.
* [ ] Outages/timeouts → fail closed (`AntiVampFailClosedError` ⇒ do not launch).
* [ ] Deploy cannot proceed on a decision past `expiresAt` (re-validate first).

## Production-readiness checklist

* [ ] API key stored server-side (never in browser/mobile bundles).
* [ ] Decision verification wired with cached public keys + rotation handling.
* [ ] Fail-closed enforced on every non-`allow` / error / timeout path.
* [ ] Webhook endpoint verifies signatures + is idempotent by delivery id.
* [ ] `reportLaunch` + `reportBond`/`reportMilestone` wired to your lifecycle.
* [ ] Rate-limit backoff handled (or rely on SDK defaults).
* [ ] Chain values restricted to AntiVamp live/integration-ready chains.
* [ ] Monitoring/alerting on validation error rate + fail-closed rejects.
* [ ] Protected badge (optional) links to the identity proof page.
* [ ] Production access requested and production key issued.

## Partner launch checklist

* [ ] Conformance suite green against sandbox.
* [ ] End-to-end lifecycle rehearsed: reserve → block copycat → allow authorized → report launch → report bond → protection extended → webhook received → explorer + usage reflect it.
* [ ] Support + escalation contacts saved (support@ / partners@ / security@).
* [ ] Incident runbook: what you do if AntiVamp is degraded (fail closed).
* [ ] Dispute path shared with your support team (`/disputes`).
* [ ] Go-live window agreed; production rate limits confirmed.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.antivamp.io/partners/09_checklists.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.