DOL English scope boundary and yearly cycle refinement
DomainsDOL EnglishProduct205 words1 min read
DEC-0059 - DOL English scope boundary and yearly cycle refinement
Phần tiêu đề “DEC-0059 - DOL English scope boundary and yearly cycle refinement”Context
Phần tiêu đề “Context”Some UX docs still mixed Product KID logic into DOL English active scope, and cycle wording stayed inconsistent with the latest direction.
Decision
Phần tiêu đề “Decision”Scope boundary:
- Parent/child household flow is Product KID scope, not DOL English Web V2 active scope.
- DOL English active docs must treat KID references as out-of-scope/deferred.
Cycle model refinement:
- DOL English active cycles are:
- Monthly auto-renew,
- One-time 3/6/12 months non-renew (yearly = 12 months).
Auth and contact consistency:
- Existing-contact at signup routes to login step with notice and prefilled contact.
- No default auto-send OTP at duplicate-contact handoff.
- Post-signup contact completion is non-blocking.
- Checkout requires at least one verified recoverable contact (
emailorphone).
Goal reminder consistency:
- Goal remains optional.
- Goal reminder uses contextual nudge only, cap 1/day/account, no fixed weekly popup.
Decision Value
Phần tiêu đề “Decision Value”- Removes scope confusion between DOL English and Product KID.
- Keeps checkout lifecycle simple while preserving a yearly non-renew option.
- Aligns auth, contact, and goal nudges across discovery and UX docs.
Rationale
Phần tiêu đề “Rationale”A clear product boundary avoids accidental feature creep in V2 docs and reduces implementation misalignment across auth, payment, and onboarding surfaces.