How should HTTP status codes and ProblemDetails be designed for production in Web API?

Map domain outcomes to suitable status codes, use ProblemDetails, include correlation IDs, and avoid leaking internals. The implementation should be justified by measurable requirements, kept as simple as the problem allows, and validated with realistic tests, telemetry, failure handling, and documented tradeoffs.