Epic 003 headline journeys
Headline journeys are long presentation-level demonstrations, not detailed coverage inventories. Failure cases and boundaries live in the linked story scenarios.
| ID | Journey | Primary stories |
|---|---|---|
| MVP-JRN-001 | Configure menu and sell the product | PROD-002, ORD-001, PAY-001, KDS-001 |
| MVP-JRN-002 | Normal commercial service loop | ORD-001/002, PAY-001, KDS-001/002, SALES-001, HIST-001 |
| MVP-JRN-003 | Non-commercial service loop | ORD-001/002/003, KDS-001/002, SALES-001 |
| MVP-JRN-004 | Checkout failure safety | PAY-001, REL-001, TECH-001 |
When implemented, journey evidence should use Playwright against the real application/database with the deterministic fake checkout adapter. Journey tests also include the journey ID in their title. They never need provider secrets or external network availability. Surfboard Demo payment/ECR verification is a separate staging smoke/contract concern under MVP-TASK-034, while production Live enablement remains an explicit release activity.