# Publish, deliver, accept

First Offer Kit 1.0.0 · Checklist, not a certification

## Before an offer goes public

- [ ] A specific buyer can understand the result in one sentence.
- [ ] The sample exists and accurately represents the work.
- [ ] The contents, formats, quantities, exclusions, and required inputs are explicit.
- [ ] Price is labeled unresolved, estimated, or firm. A guess is never presented as a live price.
- [ ] Capacity and turnaround reflect what the seller can fulfill; no invented urgency.
- [ ] Revision, cancellation, refund, support, and use-rights terms are chosen and visible.
- [ ] Seller identity and contact are accurate; inquiry or checkout actually works.
- [ ] Human page, JSON, and agent Markdown agree on SKU, version, status, price, delivery, and approval.
- [ ] All placeholder text and fictional-example labels are resolved appropriately. Do not remove a draft label merely to make the page look finished.
- [ ] You own or have permission to distribute all included material.
- [ ] Files contain no private customer information, secrets, hidden tracking, or unwanted metadata.
- [ ] Headings make sense, text has adequate contrast, links have useful names, and keyboard focus is visible.
- [ ] The page works on a phone and the sample opens on a second device or viewer.
- [ ] A paid offer has a tested payment and fulfillment process before being labeled purchasable. This kit does not provide one.

## Before starting a custom service

- [ ] Both parties agree on the exact scope, price, version, timeline, rights, and support terms.
- [ ] Required inputs are complete and the buyer has authority to supply them.
- [ ] The named human has approved any purchase or material scope change.
- [ ] Any payment status comes from the real payment provider, not an agent's claim.

## At delivery

- [ ] File names and version match the agreement.
- [ ] Every promised file opens and passes the stated size, format, print, or accessibility checks.
- [ ] The handoff includes a short file list and use instructions.
- [ ] The buyer has the agreed access and a way to report missing or damaged files.
- [ ] A delivery record distinguishes “sent,” “downloaded,” and “accepted.” Do not infer one from another.
- [ ] A receipt is issued only for a verified payment and includes the actual status, amount, and reference.

## Learn without pretending

Record these separately: offer views, crawler requests, sample downloads, human inquiries, paid orders, refunds, and accepted deliveries. None is a substitute for another. Keep the least personal data needed and explain any tracking before collecting it.