Notification governor and AI-score-ready delivery policy

DEC-0052 - Notification governor and AI-score-ready delivery policy

Context

Reactivation baseline existed, but cross-trigger arbitration and AI-score-ready delivery needed an explicit governor model.

Decision

Notification governor:

• Daily cap applies to engagement nudges only.
• Cap unit remains per channel for engagement nudges.
• If multiple engagement triggers occur on same day, send highest return-risk first.
• Overflow nudges queue to next eligible day if trigger remains valid.
• Engagement delivery sends across all enabled channels in parallel.
• Retry policy keeps retrying failed channels until stop conditions.

AI-score-ready delivery:

• Always create notification-center entry.
• Optional in-app toast and push can be sent as one-shot when user enables channel.
• Do not run repeated reminder loop for same score-ready event.
• Reminder/deeplink entry opens target task directly; AI interaction remains on-demand via contextual action (no forced auto-open).

Decision Value

• Prevents spam while preserving high-priority comeback triggers.
• Keeps async-scoring ready-state visible without repetitive noise.
• Clarifies multi-channel behavior for ops and analytics teams.

Rationale

A cap/governor is needed to coordinate overlapping nudges, while score-ready messages must remain actionable but non-annoying.