Program-adaptive week-1 activation starter policy

DEC-0080 - Program-adaptive week-1 activation starter policy

Context

Week-1 activation ladder is already defined (DEC-0079), but starter suggestions can still feel generic when user intent is clearly program-specific. This can reduce first-week momentum and perceived relevance.

Decision

Make week-1 activation starter program-adaptive with deterministic fallback:

• Program resolution order:
  1. goal_program_id,
  2. last_explicit_program_intent_14d,
  3. trending_easy_available_program.
• Starter composition per activation step:
  • 1 primary quick-start item (target duration 5-10 minutes by default),
  • up to 2 swap options in same program when inventory allows.
• Step continuity:
  • step-2 suggestion (within 48h) prefers same program and nearest assessment-form continuity from step-1 submission.
• Inventory fallback:
  • relax by nearest-ladder inside selected program first,
  • cross-program fallback only when selected program has no eligible available-now starter; show short notice.
• Boundaries:
  • activation remains non-blocking and optional,
  • no fail-state wording, no forced mode switch.
• Measurement additions:
  • activation_program_resolution_source_distribution,
  • activation_week1_completion_by_program_source,
  • activation_step2_same_program_continuity_rate.

Decision Value

• Improves perceived relevance for new users.
• Keeps first-week activation compact and actionable.
• Preserves deterministic, scalable rule-based behavior.

Rationale

Program context is one of the strongest early signals in this product. Using it in first-week activation increases match quality without introducing heavy personalization complexity.

Implications

• Product/UX impact:
  • activation card suggestions feel more aligned with user intent.
• Data/logic impact:
  • requires activation program-source resolution and continuity tracking.
• Operational impact:
  • no additional manual operation needed.

Alternatives considered

• Option A: keep one global starter profile for all programs.
• Option B: ask user to manually choose program every activation step.

Open follow-ups

• No blocker for baseline lock.