D9 "Where is my show?" pipeline trace
- Area
- D — Content & household
- Audience
- both
- Kind
- feature
- Status
- accepted
- Maturity
- shipped
- Shipped in
- 0.4.0
- Labels
- verification, ux
The feature in the specification · Read at
Requirements
A single item MUST be traceable across every service that handled it, in one view.
Each stage MUST name the service, the time, and the outcome.
A failing stage MUST carry the reason and a remedy.
Items MUST be searchable by human-meaningful terms, not internal identifiers.
The trace MUST distinguish not-monitored, never-found, never-grabbed, never-downloaded and never-imported.
Correlation across services MUST be automatic.
Uncertain correlation MUST be marked as uncertain rather than presented as fact.
Disagreement between services MUST be surfaced as a finding.
Repeated attempts for the same item MUST be shown as history.
Unavailable historical detail MUST be reported as unavailable, never inferred.
Items reported by queue health MUST link directly to their trace.
Household members MUST be able to see progress of their own requests in simplified form.
Series and season level queries MUST aggregate per-item states with a summary.
Retained history MUST be bounded, and the horizon MUST be stated.