Design a Pizza Ordering Domain
Model customizable pizzas, cart pricing, order submission, and guarded kitchen-state transitions.
Design the low-level object model and contracts for a pizza ordering application. For this exercise, assume a customer builds one or more pizzas by choosing a size, crust, and toppings from an active menu; receives a deterministic quote; and submits the cart as one order.
A submitted order snapshots every pizza specification and price. Kitchen staff may move it from submitted to preparing, ready, and completed, while cancellation is allowed only before preparation begins.
Unsupported choices, empty orders, stale quotes, duplicate submissions, and invalid state transitions must have explicit outcomes. Menu storage, payment execution, delivery routing, and user-interface details are outside scope.