Component 53 · Operations
Telemetry quality
Explain sampling, aggregation, staleness and gaps for a metric.
Overview
Explain sampling, aggregation, staleness and gaps for a metric. It converts domain state into an understandable, traceable and accessible interface contract.
When to use
Use HE/Telemetry quality when you need to explain sampling, aggregation, staleness and gaps for a metric. Keep its role distinct from transport freshness, animal-health severity and model confidence.
Example
Samples300
Window5 min
Freshness28 sec
Gaps0
<div class="he-telemetry-quality"><div class="he-telemetry-quality__item"><small>Samples</small><b>300</b></div><div class="he-telemetry-quality__item"><small>Window</small><b>5 min</b></div><div class="he-telemetry-quality__item"><small>Freshness</small><b>28 sec</b></div><div class="he-telemetry-quality__item"><small>Gaps</small><b>0</b></div></div>Anatomy
1Identity
2Primary value
3State
4Evidence or action
Anatomy stays identical in Pasture and Atlantic. A responsive layout may wrap or stack parts, but reading order and focus order remain equivalent.
Variants and states
Variants
States
Accessibility
Write the effective sample interval and last-received time in text.
- Maintain a visible keyboard focus indicator and a logical focus sequence.
- Never rely on colour alone for operational, freshness or severity state.
- Keep touch targets at least 44 × 44 px unless the target is an inline text link.
Cross-platform contract
| Surface | Canonical name | Status |
|---|---|---|
| Figma | HE/Telemetry quality | review |
| Web | .he-telemetry-quality | implemented |
| Flutter | HeTelemetryQuality | implemented |
| Token root | component.telemetryquality | generated |