STATE - Onboarding Goals

Current truth

Goal setup is fully optional across all flows. Goal prompting uses contextual non-blocking nudges with daily cap and adaptive soft-snooze to prevent nudge fatigue.

Rules

• After successful registration, user goes to Home first and receives first goal popup.
• During first 7 days after signup, Home may show inline activation guidance card; this does not replace or hard-gate goal onboarding.
• If auth/signup returns user directly to protected in-progress context, suppress immediate goal popup at return moment.
• If user later enters Home in the same session, goal nudge can appear on first Home entry when daily cap allows.
• User can skip goal popup without any block.
• Do not run fixed weekly popup re-ask.
• Use contextual goal nudge only at:
  • Home,
  • Practice Management,
  • Profile.
• Nudge frequency cap: maximum 1 goal nudge per day per account.
• Combined nudge cap across goal/profile prompts: maximum 1 nudge per day per account.
• Nudge fatigue suppression:
  • if user dismisses/ignores goal nudge >=3 times in rolling 14 days and goal is still missing:
    • enter goal_nudge_soft_snooze for 14 days.
  • during soft-snooze:
    • do not show popup-style goal nudge,
    • only show lightweight inline reminder at valid touchpoints.
  • soft-snooze exits early when user opens goal editor or saves goal.
  • after soft-snooze expires (goal still missing), popup eligibility resumes under normal daily-cap rules.
• If both goal and profile prompts are pending, show goal prompt first.
• Goal is not required for any flow, including paid flow.
• If goal is missing:
  • hide target-comparison surfaces,
  • keep non-target progress analytics visible.
• Goal can be set/updated later from Home, Practice Management, or Profile.
• Goal selector guardrails still apply by program (min/max/step).
• Goal setup is program + assessment-form + skill aware:
  • goal input options are loaded from selected program profile,
  • each assessment form and skill can have different target scale/input pattern,
  • program/form/skill options are sourced from canonical assessment form catalog,
  • do not use one global target-score input for all programs/forms.
• Saved goal payload must include:
  • goal_program_id,
  • goal_assessment_form,
  • goal_skill_id,
  • goal_scale_profile_id,
  • goal_target_value.
• Goal priority model:
  • one active primary_goal,
  • one optional secondary_goal,
  • Home/recommendation default emphasis follows primary goal.
• Goal versioning model:
  • each goal edit creates immutable goal_version_id,
  • downstream result/progress comparison reads version-at-submission.
• On successful goal save/update, show quick confirmation popover.
• Profile milestone model remains encouragement-only.
• Payment milestone handling:
  • visible for all users,
  • weighted in completion score,
  • paid flow requires payment information only (not goal/learning profile),
  • optional payment prefill before paid flow is allowed.

Encouragement layer

• profile completion,
• subtle profile attention marker,
• one-time goal-set badge,
• reminder presence in practice-management context.
• badge surface strategy:
  • profile-first,
  • light mention on Home after milestone completion.
• profile completion is recalculated live from current data.
• profile information visibility defaults to private.
• V2 achievement scope is track+display only; social-sharing rollout is deferred but data-ready.
• milestone reward is one-time per milestone (no repeat farming).
• display-name remains optional with friendly default nickname fallback.
• academic profile uses Program + Score goal, both optional with partial completion allowed.

Decision trace

• DEC-0006
• DEC-0040
• DEC-0041
• DEC-0049
• DEC-0059
• DEC-0060
• DEC-0061
• DEC-0071
• DEC-0072
• DEC-0073
• DEC-0074
• DEC-0079