Telemetry, Evidence & Operations
Telemetry Trust and Stale Data
Understand why stale or missing telemetry is a mission risk and how to identify it.
- Time estimate
- 25–30 min
- Complexity
- advanced
- Maturity
- pilot ready
- Simulator readiness
- implemented
- Software available now
- Available now — `telemetry_trust_and_stale_data` surfaces trust/stale teaching behavior in simulator/replay paths.
Student path
- Choose an anomaly scenario and read the description carefully.
- Click each clue card to mark it as relevant — consider both supporting and contradicting clues.
- Select the likely subsystem and your confidence level.
- Submit your diagnosis and read the feedback and "next check".
- Try a second scenario — notice how the same type of symptom can have different root causes.
- Copy your evidence before moving to Session 5.
Learning outcomes
Student can identify stale telemetry, explain its risk, and describe a mitigation strategy.
- Define telemetry staleness and explain how to detect it.
- Describe what a flat-line error signal could indicate.
- Propose one mitigation: watchdog timer, heartbeat check, or redundancy.
Concept primer
Understand why stale or missing telemetry is a mission risk and how to identify it.
Run telemetry_trust_and_stale_data experiment; observe stale data indicator behaviour.
Define stale data and write two questions an operator should ask when telemetry goes flat.
Interactive lab
Teaching-grade software activity slot — not a flight simulator or certified propagator.
Anomaly detective lab
Diagnose the anomaly from clues
Select an anomaly scenario. Review the clue cards, mark which clues are relevant to your diagnosis, pick the likely subsystem, and submit your diagnosis.
The error channel has been exactly 0.000° for 45 seconds. That looks too perfect.
Clues — click each to mark as relevant to your diagnosis
Your diagnosis
Self-check · Local only
3 questions — 0/3 answered correctly
Local-only. No submission, no grade. Answers revealed here only.
The attitude error channel has read exactly 0.000° for 45 consecutive seconds. What is the most likely cause?
Which clue best CONTRADICTS the hypothesis that a comms fault caused elevated packet loss?
Why is acting on stale telemetry sometimes worse than having no data?
Evidence · Local only
Capture your evidence
Local-only — no submission, no upload. Copy the text below or screenshot this panel to share manually.
Evidence prompts
- Which anomaly scenario did you diagnose?
- List one supporting clue and one neutral/contradicting clue.
- What next check would you perform to confirm or rule out your diagnosis?
Captured values
- Scenario
- Record which anomaly scenario you diagnosed
- Clues selected
- List the clue channels you marked as relevant
- Diagnosis
- Your likely subsystem and confidence level
- Next check
- The next channel or action you would perform
Track 6 — Telemetry / Evidence Activity: telemetry_trust_stale Captured: 2026-05-16T07:38:33.603Z --- Scenario: Record which anomaly scenario you diagnosed Clues selected: List the clue channels you marked as relevant Diagnosis: Your likely subsystem and confidence level Next check: The next channel or action you would perform --- Teaching-grade evidence. Local-only — no account, no submission, no official grade.
Evidence capture
Expected outputs learners should be able to show after the lab (Phase 9 evidence engine preview available).
- Stale or flat-line segment identified on chart
- Student proposes mitigation (watchdog, redundancy, operator procedure)
Reflection
Given a telemetry trace with a flat-line period, diagnose the possible cause.
Responses are not persisted in this preview unless a specific activity component adds storage later.
Assessment / quick check
Why is acting on stale attitude data sometimes worse than having no data?
Teacher notes
Discuss cyber-physical trust: stale data is an ops problem, not only a math problem.
Teacher use
Emphasise that supporting, neutral, and contradicting clues are all evidence. A contradicting clue helps rule out hypotheses. Prompt: "What additional channel would you check to increase your confidence from medium to high?" Connect the battery-drain scenario to Track 3 and the packet-loss scenario to Track 4 link margin.
Next activity
Suggested progression from the mission learning path. Links avoid missing activity routes.