# Commerce Cutover Kit — first-wave brief

Use this with your own team. Blank project answers are unknown, not verified facts.

## Capability

Which order, customer, configuration or other capability must move?

Project answer: ___
Evidence / owner / next decision: ___

## First consumer

Which application makes the first request, and what must it be able to do?

Project answer: ___
Evidence / owner / next decision: ___

## Systems and coexistence

Which interfaces and consumers remain on the existing path during this wave?

Project answer: ___
Evidence / owner / next decision: ___

## Records and identity

What store/tenant keys, relationships, exact values and capture boundaries must be preserved?

Project answer: ___
Evidence / owner / next decision: ___

## Acceptance and recovery

Who accepts records, behavior, access, cutover and recovery, and what evidence will they inspect?

Project answer: ___
Evidence / owner / next decision: ___

## Timing and next decision

What real release or retirement commitment drives the work, and which decision comes next?

Project answer: ___
Evidence / owner / next decision: ___

## Proposed paid boundary

One commerce capability, its mapped records, required adapter and API path, first consuming application, reconciliation, cutover and operating handover.

## Remaining decisions

Access, exclusions, acceptance owners, operating handover, delivery dates and commercial scope remain to agree.

Local tool use does not send this brief. Choose what to share through https://www.jextra.com/campaigns/commerce-capability-migration#lead-form.