Skip to content

I don't know, but here's how I'd reason

Make the unknown visible and your next inference inspectable.

Predict first

Before you read: predict

A player resumes after a handoff. The only artifact is a screen recording; there is no component contract or trace. An interviewer asks whether the player-session record is durable.

Which continuation is useful and truthful?

Pick one

The 30-second version

Say what you do not know once. Separate a confirmed observation from the conclusion you are considering, then name the evidence that could change it. Give a conditional expectation with a confidence limit, rather than invented internals. When a contract or trace adds a decisive fact, explain the causal difference and update the expectation. [S1][S2]

Make the unknown visible and your next inference inspectable.

How it works

Step 1 of 5

State the boundary. Say that direct knowledge is absent; do not fill the gap with a familiar pattern. [S1][S2]

Analogy: Identifying an unlabeled paint sample

A conservation scientist examines an unlabeled paint sample. She observes a blue pigment and a cracked binder, but does not name the original workshop as fact. She calls one period plausible, marks that as an inference, and asks for a pigment assay or archive record. A lab result can revise the period expectation without turning the first answer into a failure.

In the analogy In the answer
Blue pigment and cracked binder Observed artifact or known fact
Plausible period Conditional inference
Assay or archive record Discriminating evidence
Workshop unknown Direct knowledge boundary
Lab result Newly confirmed fact

The analogy does not explain streaming durability or establish that a component will fail in one way. It shows why a plausible comparison remains an inference. The cited interview account supplies only the assessment context: questions probe thinking, causal explanation and adaptation rather than recalled patterns. [S2]

The local five moves make an answer auditable: boundary, observation, inference, evidence and revision. They are a curriculum scaffold, not a claimed universal interview script. The allowed sources do not prove a universal confidence formula or a mandatory verification method. A learner should use the available artifact and state the missing evidence, not manufacture certainty. [S1][S2]

A nearby fact is useful when it narrows a question without pretending to settle it. An artifact can reveal one event while leaving the component responsible for it unknown. Confidence belongs on the resulting inference, with a reason for its limit. A percentage is not a substitute for a premise, and a familiar design is not evidence that this component uses the same one. A discriminating check must be capable of separating the explanations actually under consideration. Explain how its possible findings would affect the claim.

Try it

Answer first, then check. Nothing is saved.

Question 1 of 5

A review verifies only that two devices carry the same opaque handoff ID. It does not verify the persistence layer.

Which starting point is sound?

Pick one

Question 2 of 5

A screen recording confirms that a player resumed after handoff. It says nothing about a store failure.

Which claim calibrates confidence correctly?

Pick one

Question 3 of 5

A resume recording fits two explanations: a local snapshot or a durable server record.

Which next action can distinguish them?

Pick one

Question 4 of 5

A review has a handoff recording but no component contract, trace or reproduction.

Which comment keeps the local-snapshot alternative in view without turning it into a reason to stop?

Pick one

Question 5 of 5

A candidate initially expects a durable server record at low confidence. A component contract later states that the handoff token is cached locally only.

What should the candidate do next?

Pick one

Go deeper

Pro tip

Practise on two unrelated artifacts. After each 20-second response, label every sentence as observation, inference or proposed check, then revise one label that is doing the wrong job.

Checked against the tools and docs as of 2026-09-30.