Improve Model Serving & Monitoring

Operation

Implement the requested coherent change at the owning source and update directly affected consumers. An earlier audit is optional when the user and repository already establish the target. Validate the changed behavior, then stop when the requested scope is complete.

Goal

Implement one selected, evidence-backed Model Serving & Monitoring improvement at the authoritative owner. Complete the directly affected contract without broad cleanup or redesign.

Domain rules

• Make artifact and preprocessing identity immutable for a deployment and surface it in logs/metrics/traces.
• Bound queueing, batch wait, concurrency, memory, retries, and fallback; shed load explicitly rather than amplifying it.
• Use canary/shadow/flag rollout only with comparison metrics, isolation, and rollback criteria.
• Keep monitoring tied to the decision contract and avoid raw sensitive inputs/outputs in telemetry.

Validation

• Run load/concurrency/cancel/fallback/artifact-compatibility tests with representative inputs.
• Verify readiness, rollout, rollback/disable, and one degraded-dependency trace.
• Report production traffic, hardware, provider quota, and long-window drift gates separately.