Checkout readiness depends on observable milestones.

Checkout surfaces may require client-side state, authentication, or control responses that standard analytics may not preserve or expose at the same event-level provenance. Merchant systems may record the last observed milestone and a surfaced error. They do not reveal an off-property model decision, and Cartograph does not claim to observe one.

• Cart creation or retrieval requires a client-side step not represented in merchant-observed events.
• The next tax or shipping milestone is not observed, or the merchant system records an error.
• A bot, fraud, or risk control records a challenge or block at a named milestone.
• Merchant-surfaced evidence at the named milestone does not include payment-method or wallet option identifiers.
• Authentication or account creation is required before the next milestone.
• No log-origin request evidence is attached to the cart or checkout milestone events.

The Transactable category, applied to your checkout. Two separate evidence channels, never merged.

1. Merchant-observed events — from your own cart and checkout systems:

• The last observed cart or checkout milestone and the next expected milestone that was not observed.
• The named control and response, only when the merchant system exposes them.
• Merchant-surfaced payment-method and wallet option identifiers at the milestone in scope, without collecting credentials, payment data, or form values.

2. Future authorized diagnostics — separately authorized, not running today:

Authorized diagnostics are planned to exercise selected cart and checkout steps in merchant-approved environments. Merchant authority would be separately verified. Staging or another merchant-approved test environment is preferred; production requires separate explicit authorization. Diagnostics stop before authentication, payment submission, order placement, or any irreversible action. Synthetic evidence remains separate from merchant traffic metrics. Nothing here implies current availability or counsel clearance.

The initial public scan is not running today. When it launches, it is specified to evaluate public, non-authenticated commerce surfaces using read-only GET and HEAD requests. It is not specified to log in, create accounts, submit forms, mutate carts, initiate checkout, enter payment data, place orders, test security controls, or bypass access controls.

• Checkout and conversion teams — prepare to review the last observed milestone and the next expected milestone that was not observed.
• Payments teams — prepare to review merchant-surfaced payment-method and wallet option evidence at named milestones, without inferring model legibility or preference.
• Risk, fraud, and bot teams — prepare to review named control responses at exact milestones when those responses are exposed by merchant systems.