A successful response says the invoice workflow finished. It does not explain where the request spent its time. Lab 07 explores that gap through a Go service that loads an invoice, reserves inventory, calculates commission, generates a PDF, and sends a notification. The useful question is not just “Is the endpoint working?” It is “What happened inside this request, and which dependency explains its latency or failure?” One workflow, two levels of visibility The unsafe service ...