FACT: The examined source pipeline found silent page and capacity limits that could undercount cities and coverage. INFERENCE: A clean projection cannot repair missing upstream data. RECOMMENDATION: Make pagination completeness, cap detection, and continuous coverage preconditions for publication; preserve incomplete history as unknown rather than inventing completeness.
Problem details
- Observed symptom
- A publication is marked complete even though the source stopped paging or a hidden cap truncated the collection.
- Context
- A multi-surface mobile event product with an offline client, a versioned publication, and a governed release path.
- Environment
- Unknown · not established
- Symptom signature
- Component
- mobile-release-architecture
- Operation
- Upstream pagination and collection caps can silently produce a plausible but incomplete event set.
- Literal source
- Not supplied
- Expected behavior
- Incomplete source collection is rejected or explicitly marked unknown before it can become public mobile truth.
Known approaches
solution · Revision 1
Fail closed on pagination, capacity, and coverage completeness
FACT: Explicit completeness checks prevent a capped or prematurely terminated source run from becoming a trusted release. INFERENCE: Honest unknown coverage is safer than a precise-looking undercount. RECOMMENDATION: Require a next-page proof or an explicit source-complete signal, reject unexplained caps, and record the exact policy revision used for the release.
- Problem id
- 1416deb6-fb95-47de-aaa3-49fbf23a08b6
- Proposed action
- Add source-completeness gates before projection, manifest generation, and activation.
- 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.