FACT: In a two-city event app, a source snapshot carried date ranges plus optional continuity metadata. An early projector/client path treated a multi-day envelope as daily coverage and separately filtered ongoing timed intervals by exact start, producing incorrect Today/Weekend membership and stale urgency. The corrected contract distinguishes date-only, timed, continuous, and unknown coverage; unknown legacy envelopes expose date inquiry instead of claiming every intervening day. INFERENCE: a series envelope is an availability claim, not a list of sessions. RECOMMENDATION: model explicit occurrences and coverage semantics before implementing date filters, reminders, calendars, or urgency. Tags: mobile temporal data, occurrence modeling, date ranges, event discovery.
Problem details
- Observed symptom
- Date-window membership and urgency were wrong when multi-day event envelopes were interpreted as daily sessions.
- Context
- A mobile event catalog with date filters, reminders, calendar handoff, ranking, and offline publication.
- Environment
- Unknown · not established
- Symptom signature
- Component
- temporal data model
- Operation
- daily date-window membership
- Tool product
- mobile event catalog
- Literal source
- Not supplied
- Expected behavior
- Not supplied
Known approaches
solution · Revision 2
Select dates from one authoritative membership model and explicit occurrences
FACT: The corrected implementation selected explicit occurrences, applied stated civil-day rules, inclusive date-only ends, exclusive timed ends, and continuous overlap only when continuity was explicit; unsupported multi-day coverage remained unknown. A multi-surface projection also stayed consistent when one authoritative membership index owned daily totals and membership, other surfaces enriched only by exact identity or path, weekend membership was an exact deduplicated union, and the selected occurrence remained distinct from a generic next occurrence. INFERENCE: A series envelope is not daily truth, and independently reinterpreted surface buckets create contradictory reader facts. RECOMMENDATION: Build temporal filters, reminders, calendars, ranking, and urgency from explicit occurrence objects plus the authoritative membership index. LIMITATION: This cannot recover missing source occurrences; freshness and completeness of the index remain separate gates.
- Problem id
- 157a1abb-3d46-4a1c-a14b-f514838076a8
- Proposed action
- Make the authoritative membership index the sole owner of daily membership and totals; join display data by exact identity or path, preserve selected occurrence identity, and test date-only, timed, continuous, unknown, DST, midnight, and cross-surface cases.
- Applicability
- State
- known
- Text
- Use for event products with multiple temporal surfaces over one content graph.
- Limitations
- State
- known
- Text
- The membership index must be fresh and complete for the product window; source omissions remain unknown.
- Success criteria
- Today, tomorrow, weekend, and agenda surfaces agree on membership and totals; selected occurrence labels survive into actions; unsupported coverage is never expanded into invented sessions.
- Risk notes
- Text
- A single index is safe only when its freshness and completeness are independently proven.
- Lifecycle
- active
Page 1 · 1 children total
Sources and related records
No source relations recorded.