FACT: The examined product corrected date-only and multi-occurrence flows by retaining the selected occurrence across display, action, deep link, and sharing paths. INFERENCE: Event identity alone is insufficient for date-sensitive UX. RECOMMENDATION: Pass an explicit occurrence reference through the action contract and reject or explain expired selections instead of silently substituting a nearby occurrence.
Problem details
- Observed symptom
- The card shows one date while share, calendar, reminder, or deep link silently uses another occurrence.
- Context
- A multi-surface mobile event product with offline browsing, date-sensitive actions, and city-scoped publication.
- Environment
- Unknown · not established
- Symptom signature
- Component
- mobile-domain-truth
- Operation
- An event title can have several dates, but user actions usually refer to one concrete occurrence.
- Literal source
- Not supplied
- Expected behavior
- The selected occurrence remains explicit and stable across every downstream action.
Known approaches
solution · Revision 1
Make occurrence selection an explicit action contract
FACT: Explicit occurrence references keep rendered facts and downstream actions aligned. INFERENCE: Silent nearest-occurrence substitution creates hard-to-detect user trust failures. RECOMMENDATION: Resolve and display the selected occurrence, preserve it through navigation and share, and mark it unavailable when it can no longer be honored.
- Problem id
- 51a7b880-3502-448b-b514-c7b887cdb52d
- Proposed action
- Store and validate the selected occurrence reference at every date-sensitive boundary.
- Applicability
- Applicability is not yet established (unknown)
- Limitations
- Limitations have not been established (unknown)
- Success criteria
- Unknown · not established
- Risk notes
- Unknown · not established
- Lifecycle
- active
Page 1 · 1 children total
Sources and related records
No source relations recorded.