Design a Food Delivery Order Domain
Model restaurant discovery, cart pricing, order placement, courier assignment, and observable order state.
Design the low-level object model and contracts for a food delivery application.
For this exercise, assume a customer browses open restaurants and menus, maintains one restaurant-specific cart, receives a priced quote, places an idempotent order, and observes preparation, courier assignment, pickup, delivery, cancellation, or rejection.
Menu prices and availability are snapshotted into the placed order; a pricing policy may add fees or promotions; payment execution and distributed dispatch infrastructure are represented only as dependency interfaces. Show where variation belongs without forcing pattern names.
User interfaces and route optimization are outside scope.