"Checkout is not live yet"

Every shop has a checkout button. This one has a checkout button that says:

Checkout — not live yet (disabled)

and next to it, in the cart: “Payment is not connected, so nothing can be ordered or charged yet — the shipping prices above are real quotes.”

That is not a placeholder waiting to be designed. It is the honest state of the product, and it is verified like any other feature.

The state machine the copy describes

The storefront’s payment path has exactly two states, and the copy is different in each:

Until a secret key is saved, the button stays disabled and says so. That is the whole design: the shop can be built, filled, priced and browsed without ever pretending it can take money.

The copy is data, and it is verified

The storefront separates words from layout: store-level copy, product copy and shipping labels live in the vault and are editable from the desk with no deploy; only layout is code. That split is what makes the honest state cheap to maintain — the go-live is a vault write, not a code change [FACT, copy-map.md].

But “words are data” is not a licence to say anything. The independent verifier checks the rendered DOM, not the source:

• the button’s text is exactly “Checkout — not live yet”;
• disabled is true and aria-disabled="true" is set, so it is unusable and announced as unusable;
• the reason line is present and not hidden;
• the cart toast says “Added to cart — 1 item. Checkout is not live yet.”;
• the meta description matches the shipped description, including the honest clause;
• the text passes contrast (5.72:1 for the disabled checkout line);
• the preview page says, in its own meta description, that it is “Not the live shop. Checkout is not live.” and makes no network requests [FACT, honest-states.md].

A disabled button is not a fallback. It is a claim with a test.

The traps the copy work found

Writing honest copy at this level surfaces traps that are invisible in a design file:

• A field that is stored but rendered nowhere. One description field is saved by the desk and appears on no page. The copy contract marks it explicitly so an operator edit is not silently lost.
• A field missing from the server cap table. A long footer line was silently dropped on save until the table was fixed; the contract records which fields had this bug.
• A claim that must stay verifiable. The [ PROOF ] band makes factual statements about the shop; the rules say the claim must remain true, and the origin audit (the previous piece) is what keeps it true.
• The [ Preview ] page. A static design-review page that is explicitly not the live shop and says so in its meta description and its first paragraph.

None of these are features. They are the difference between a shop that is honest and a shop whose copy happens to be true today.

Go-live is a data change

The Stripe integration is built and sandbox-ready; what remains is keys, a webhook endpoint and a go-live decision. The important property is where those live: the secret key goes into the vault (0600, outside the app tree), the webhook secret goes into the vault, and the copy flips because the server sees the keys — not because someone edited a page [FACT, stripe-live.md].

That is why the honest state is stable: a deploy cannot accidentally make the shop claim it takes money. The claim is derived from configuration the operator sets deliberately.

What I’d tell someone

1. Build the honest state first. A disabled button with a reason is better than a fake checkout, and it lets you demo the real product before the payment path exists.
2. Verify copy in the DOM. Text, disabled, aria-disabled, the reason line, contrast, the meta description — all of it is testable.
3. Make go-live a data change. Keys in a vault, copy derived from their presence; no code edit and no deploy should be able to flip the claim by accident.
4. Write down the traps. The stored-but-unrendered field, the field missing from a cap table: they are copy bugs that look like design bugs.
5. Keep the preview honest too. A design preview that says “not the live shop” is part of the product.

“Checkout is not live yet” is the most important sentence on the site. It is the one that costs a sale and keeps the shop trustworthy.

The copy map and the honest-states inventory are attached below.