C.26.1:4.3 - Probe-coupled context-cut worked use slice
This worked use slice is not a standalone pattern. It tests DDD and bounded-context work when the context cut is not only discovered but also changes meaning, coordination, export validity, or viability.
Ask: was the bounded-context cut merely discovered, or did the workshop, dashboard, API extraction, bridge, split, merge, or orchestration change alignment, ownership, vocabulary, export validity, or viability?
| Slice field | Example content |
|---|---|
| Case | A product organization considers splitting payment handling out of a checkout bounded context after repeated payment-failure incidents. |
| Ordinary DDD finding | Checkout and Payment use different local meanings for Order.status, PaymentFailure, and Retryable; an ordinary F.9 bridge is needed. |
| Probe / intervention | The event-storming workshop starts from payment-failure dashboards and asks teams to place incidents by owner, customer impact, and recovery path. |
| Post-probe reading | Product, Support, and Payment start treating payment failure as a customer-risk gate, not only a technical retry condition. |
| Evidence | Incident labels are reclassified, escalation changes, backlog priority changes, and the dashboard query is rewritten. |
| Export loss | Copying PaymentFailure = customer risk into both contexts loses the difference between retryable technical failure, promise breach, and support escalation trigger. |
| Decision output | Keep the split, mark the workshop result as probe-coupled, add F.9 loss notes, and add a payment-risk escalation promise to the boundary design. |