
A community-garden plot service that hides errors inside "success" replies. Every outcome must carry the correct signal, with one consistent error shape and no body where none belongs.
A maintenance work-order service where clients can't find an item after creating it. Replies must point clients to the new item's address, and repeating an action must not double it up.
An organisation wants the same employee directory as JSON for its intranet app and as a spreadsheet (CSV) for HR. The service returns whichever the client asks for, correctly formatted and escaped.
A pricing service that should shape every reply the same way - a tracking id, caching hints, a consistent wrapper - without each route repeating the code. Handlers return data; a shared step finishes the response.