Evidence · Lesson 04
Build a canonical story record
Capture stable facts once so every answer variant and follow-up has the same source of truth.
What you will learn
- Capture stable facts once so every answer variant and follow-up has the same source of truth.
Minimum durable record
Record the event, time period, role, stakes, responsibility, constraints, alternatives, personal and team actions, result, evidence, caveat, reflection, and confidentiality status. Missing detail can remain unknown.
- Dates and role are stable.
- Personal action is separate from team action.
- Sensitive names and customer details are generalized before practice.
Variants cannot backfill facts
A concise or question-specific answer may omit detail, but it must not introduce a metric, decision, role, technology, or outcome that the canonical story does not support.
- New claim? Update or confirm the story first.
- Material adverse facts remain present.
- Every metric retains its source and unit.
One source, multiple presentations
A story record contains a migration decision, a rollback, and a later test harness.
The concise version claims a flawless launch while the deep-dive version admits a rollback.
Both versions state that the first rollout was reversed. The concise version says why and what changed; the deep dive adds the technical trigger and test design.
- Omission must not invert reality.
- Depth can change without changing facts.
- The adverse fact improves follow-up resilience.
Draft a canonical record for one event before writing an answer.
- 1List immutable facts and known unknowns.
- 2Separate personal action, team action, and outcome.
- 3Write the confidentiality-safe version of every proper noun or sensitive number.
Open the answer check
Another truthful presentation of the event should be derivable without inventing a fact or exposing information you cannot share.
Finish this lesson
Record completion when you have worked through the material. Completion is learning progress, not evidence of mastery.
Loading completion…