Is the telemetry summary current?
You are a ground systems engineer preparing the Kestrel Survey handoff.
The question
At 14:12, the current-state line needs a verified sample at most 6 minutes old. The source log records original event times and sequence IDs.
| Value | |
|---|---|
| Receipt time | 14:10 |
| Listed sample time | 14:08 |
| Reported reading | In range |
The AI draft labels the reading current. The receipt row has not been checked against the source log.
“Decide what the handoff can say about current spacecraft status.”
Not saved by this site. Your browser may restore text when you navigate back.
A strong answer, step by step
Open each step in turn. This is one strong answer, not the only one.
Step 1: Which timestamp matters?
What would you do here? Open the move you’d make.
Use the row’s receipt time
Tempting, but it misses something. The 14:10 receipt does not establish when the spacecraft sample was taken.
Use the original sample time
The strong move. The case defines freshness from verified measurement time.
Use the time the summary was generated
Tempting, but it misses something. A fresh summary can describe old telemetry.
See how a strong candidate says it
“Use the verified sample time. The receipt time only tells me when the ground service received the row.”
Why it works: A recent receipt can carry an older reading.
Step 2: What would verify the draft?
What would you do here? Open the move you’d make.
Accept the handoff because the displayed value is in range
Tempting, but it misses something. A value can be in range and still too old to establish current state.
Compare with the next draft
Tempting, but it misses something. Two summaries can repeat the same receipt row.
Verify the time and sequence ID in the source log
The strong move. This checks that the displayed timestamp belongs to the event.
See how a strong candidate says it
“A genuine 14:08 sample would be 4 minutes old. I would check the event time and sequence ID in the source log before calling it current.”
Why it works: The listed sample time passes the threshold only if it describes the actual sample.
Step 3: What can you say now?
The source log shows that the 14:10 receipt replayed a 13:58 sample. The latest verified sample for the required reading is at 14:03.
What would you do here? Open the move you’d make.
Mark current status unconfirmed
The strong move. The newest verified evidence is outside the case’s freshness window.
Keep the reading current because the replay arrived recently
Tempting, but it misses something. The receipt time does not make a 13:58 reading newer.
Report a new spacecraft fault
Tempting, but it misses something. The discrepancy shows a freshness problem, not a verified fault in the spacecraft.
See how a strong candidate says it
“The replay is 14 minutes old and the latest verified sample is 9 minutes old. Both exceed 6 minutes. I would correct the handoff and mark current status unconfirmed.”
Why it works: A stale observation establishes a past reading. It does not establish a new diagnosis.
Step 4: Who owns the next check?
What would you do here? Open the move you’d make.
Ask the AI to make the status more certain
Tempting, but it misses something. A wording change cannot supply a current sample.
Hand off the verified time and name the next owner
The strong move. The lead can distinguish the data issue from spacecraft state.
Remove the timestamp from the handoff
Tempting, but it misses something. That hides why the current-state claim failed.
See how a strong candidate says it
“Tell the mission lead that the last verified sample is from 14:03 and current status is unconfirmed. Ask the ground systems owner to check the replay and report the next verified sample.”
Why it works: The handoff gives the lead an observation, a limit and an owner.
The answer, in short
- Decision
- Correct the current-state line and escalate the replay to the ground systems owner.
- Because
- The last verified sample is 9 minutes old, outside the 6-minute limit.
- What would change it
- A newer applicable sample with a verified event time could support an updated status.
Common traps
- Use receipt time as evidence of sample freshness.
- Treat old normal data as a current all-clear.
- Treat stale telemetry as proof of a spacecraft fault.
Check your answer
- Did I separate the receipt time from the event time?
- Did I check the source event and its sequence ID?
- Did I compute both actual sample ages?
- Did I state what is uncertain and who checks it?
Last reviewed Nov 11, 2026