Reactivation intent-aware recommendation handoff policy

DEC-0076 - Reactivation intent-aware recommendation handoff policy

Context

Reactivation notifications already bring users back, but the first recommendation set after entry can feel generic. This creates friction right at return moment and reduces chance of immediate re-engagement.

Decision

Add one lightweight handoff contract from notification to recommendation:

• Notification payload includes:
  • reactivation_intent_stage (lost_streak | inactive_1w | inactive_1m | inactive_1y | inactive_q3_repeat),
  • optional seed_program_id,
  • optional seed_skill_id,
  • reactivation_entry_session_id.
• First recommendation set after reminder click uses one-time seed boost:
  • include at least 1 quick-win item aligned to seed context when inventory allows,
  • keep existing habit_first, freshness/topic caps, and entitlement-lock behavior unchanged.
• Stage-based seed defaults:
  • lost_streak / inactive_1w: prioritize last-active skill + quick-win.
  • inactive_1m / inactive_1y / inactive_q3_repeat: include 1 quick-win + 1 trending-new item in program.
• Expiry/guardrails:
  • seed boost applies only to first set in current session,
  • boost ends after first attempt-start or session end,
  • if seed inventory is missing, fallback to baseline trending_14d + easy_start_bias.
• Non-expansion rule:
  • no extra follow-up sequence is created if user clicks reminder but stays idle,
  • no bypass of paywall/entitlement rules.

Decision Value

• Increases relevance exactly at comeback moment.
• Preserves simple deterministic engine.
• Avoids additional complexity in notification cadence.

Rationale

A one-time seeded first set gives immediate direction without overfitting or introducing long-lived personalized state.

Implications

• Product/UX impact:
  • smoother return flow from reminder click to first meaningful action.
• Data/logic impact:
  • needs minimal handoff metadata and one-session TTL.
• Operational impact:
  • no additional marketer workflow; only contract-level payload extension.

Alternatives considered

• Option A: Keep reminders and recommendation fully decoupled.
• Option B: Force dedicated comeback mode with separate UX state machine.

Open follow-ups

• No blocker for baseline lock.