Transparency
Known weaknesses
For each thing this dashboard is willing to say, here is the strongest rebuttal and the guardrail already in the code.
Single-label channel-state compression
- What the app says
The dashboard reduces the channel's current algorithmic situation to one label (e.g. suggested_run, search_tail, dormant) from a fixed set of states.
- Strongest counter-argument
A channel can be in multiple states simultaneously — for example, in a suggested run on one video while other videos are dormant. A single label hides this co-occurrence and may assign the wrong dominant frame for a given reader's question.
- Mitigation in the code
The state label is backed by two support metrics from event_channel_state_change that reflect the actual weighted evidence for the classification. The Honesty panel names the compression explicitly.
- Why it still ships
A single-state label is more actionable for most readers than a multi-state matrix. The support metrics partially compensate for what the single label omits.
Traffic-source attribution gaps
- What the app says
Traffic source breakdowns claim to show where views came from (Browse, Search, Suggested, External, etc.).
- Strongest counter-argument
YouTube does not expose every source, and the per-source impression rows often don't sum to the per-video total. The unattributed share can be substantial on some channels or source types. Comparing sources by share may over- or understate the true split.
- Mitigation in the code
Unattributed impressions are surfaced on the Honesty panel rather than being redistributed. The limits registry names this as a first-class attribution limit.
- Why it still ships
Attribution data is the best available signal for how videos reach viewers. The unattributed gap is visible, not hidden, so readers can calibrate accordingly.
Edit before/after observational limits
- What the app says
The Changes page shows click rate before and after a title or thumbnail change, implying a before/after comparison.
- Strongest counter-argument
Many factors change simultaneously with or shortly after an edit — seasonality, topic trends, the age of the video at the time of the edit, and YouTube's own ongoing impression testing. The before/after comparison observes correlation in time, not causation.
- Mitigation in the code
The Changes page copy states explicitly: "Whether the edit caused the change is observational, not provable — many things move in parallel." No causal language appears in the rendered prose.
- Why it still ships
Knowing that click rate rose or fell around an edit is a factual observation that has informational value even without a causal claim. The hedge is present at the top of the page and in every era comparison.
Wisdom threshold flips near boundaries
- What the app says
The Wisdom panel renders verdicts (agrees / disagrees / mixed) on conventional YouTube creator beliefs using this channel's data.
- Strongest counter-argument
Verdict boundaries are threshold-based. A channel sitting just below a threshold (e.g. a 0.1 pp difference in CTR) flips from 'agrees' to 'disagrees'. At that boundary the verdict carries less signal than the raw numbers do.
- Mitigation in the code
Verdicts include the underlying numbers that drove them. The Wisdom panel design surfaces the evidence rather than just the verdict label, so readers can assess near-boundary cases.
- Why it still ships
Structured verdicts are substantially more scannable than raw numbers alone. The evidence display lets attentive readers catch boundary effects.
Detector-family consolidation hiding module nuance
- What the app says
The Moment chapter and Story timeline surface one insight per render, selected from the full detector inventory.
- Strongest counter-argument
Collapsing dozens of detectors into one featured insight per render means many relevant signals are not shown. The selection algorithm prioritises by magnitude, recency, and certainty — but a less prominent signal may be more relevant for a specific reader's question.
- Mitigation in the code
The /help/detectors page lists every detector with its activation stage and sample-size threshold. The selection algorithm is transparent about its priority ordering. Story timeline events surface the most significant insight per week.
- Why it still ships
Showing all active detector outputs simultaneously produces an unreadable wall of context-free numbers. One featured insight per render is the minimum to remain coherent. Readers who want the full inventory can read the Story page or /help/detectors.
Keep verifying
The rest of the honesty layer
Known weaknesses is one of three honesty surfaces. Beside it sit the methodology notes and the limits registry. Each names a different part of what the data can and can't say.