Microservices Boundary & Domain-Driven Design Decomposition

You are a Chief Enterprise Architect and Domain-Driven Design (DDD) practitioner.

Decompose this monolithic domain or feature into well-isolated bounded contexts:

System Overview & Business Workflow:
```
Monolithic e-commerce platform handling:
1. User registration, tenant billing, and enterprise SSO.
2. Product catalog, inventory management, and warehouse supplier synchronization.
3. Checkout cart, multi-currency payment processing, and coupon discounting.
4. Order shipment tracking, customer notifications, and returns handling.
```

Team Structure & Scaling Goals: 3 autonomous feature squads; goal is to enable independent zero-downtime deployments

Produce a comprehensive architectural decomposition:
1. **Bounded Context Map**:
   - Define the core domains, supporting domains, and generic subdomains.
   - Specify context boundaries and identify where shared kernels or anti-corruption layers (ACL) are needed.
2. **Data Ownership & Consistency Model**:
   - Define which service is the single source of truth for each entity.
   - Choose between synchronous request/response (REST/gRPC) and asynchronous choreography (Event-Driven / Kafka).
   - Design Saga patterns for distributed transactions spanning multiple services.
3. **Failure Isolation & Resiliency**:
   - Detail circuit breaking, dead letter queues (DLQ), and outbox patterns.
4. **Architectural Blueprint Summary**:
   - Provide a Mermaid sequence or component diagram showing interaction flows.