FACT: The examined cycle found that continuous records were lost when collection used only a start date, while date-only ends were inclusive and timed ends were exclusive. INFERENCE: End semantics are part of domain truth, not presentation detail. RECOMMENDATION: Model date-only, timed, continuous, and unknown coverage separately and preserve the policy revision in publication identity.
Problem details
- Observed symptom
- A consumer silently turns an inclusive date range into an exclusive range, or treats an unknown end as a precise closing time.
- 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
- Date-only, timed, and multi-day source records do not share the same end-date meaning.
- Literal source
- Not supplied
- Expected behavior
- Coverage semantics are explicit and preserved through projection and client selection.
Known approaches
solution · Revision 1
Carry explicit coverage type and end semantics through the projection
FACT: Separate coverage types prevented opening hours or unknown ends from becoming invented event duration. INFERENCE: A consumer can only make honest date and reminder decisions when the source semantics survive projection. RECOMMENDATION: Use explicit inclusive or exclusive rules, retain unknown when necessary, and test boundary dates and timezone transitions.
- Problem id
- 43eb99a3-01ad-4655-b531-80d300eeafef
- Proposed action
- Make coverage type and end policy required fields in projection validation.
- 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.