Mimir

← Back to documents

ACME-5017: Story for Notification Service reliability improvement 17

jira
notification
f34aa6b0e8d2

jira/acme-5017-notification-story.md

ACME-5017: Story for Notification Service reliability improvement 17

Date: 2025-10-16 Type: Story Priority: P1 Service: Notification Service Owner: Engagement Platform GitHub References: GH-5017, GH-5018 API References: API-NOTIFICATION-01, API-NOTIFICATION-02, API-NOTIFICATION-03, API-NOTIFICATION-04

Business Context

Acme Commerce depends on the Notification Service to protect customer trust during high-volume shopping periods. This ticket captures engineering work needed after operational reviews found risk from misconfigured feature flag targeting a broad customer segment.

Scope

  • Review service contract behavior against API-NOTIFICATION-02.
  • Update dashboards and alerts owned by Engagement Platform.
  • Coordinate rollout with the teams that operate Authentication Service, Checkout Service, Billing Service, Inventory Service, and Notification Service.
  • Link implementation work to GitHub items GH-5017, GH-5018.

Definition of Done

  • Tests cover nominal, timeout, replay, and malformed payload scenarios.
  • Runbook steps are updated and validated in staging.
  • Incident review owners can cite this ticket as remediation evidence.