Objectivesby the end of this lesson
- Explain why a written log matters more than memory.
- Record an observation with enough context to repeat it.
- Keep what you saw separate from what you think it means.
Every useful finding starts as a plain record of what happened. This sample lesson shows how a Learn page uses the shared reading template, with a few lesson-only parts.
Why keep a log
Model behaviour can vary between runs. A log turns a vague memory into something you, and later a reviewer, can check. Only test systems you are permitted to test, and note that permission in the log.
Write one entry
Each entry needs enough detail to repeat it: when, which model, what you sent and what came back.
- id: obs-001
date: 2026-09-12
model: example-model # sample, not a real system
prompt: "Summarise the attached policy in two sentences."
observed: "Returned three sentences; omitted section 4."
notes: "Repeat with a shorter policy before concluding."Separate the layers
Keep the record of what happened apart from your reading of it. The same three layers from the writing template apply here.
Exercise 1about 15 min · sample
Log three observations
- Pick a task you are allowed to test, such as summarising a public document.
- Run it three times and write one log entry per run.
- Compare the entries. Note anything that changed, without explaining it yet.
Show a sample answer
Placeholder: a sample answer would appear here, written in the same log format.
Check your log
Read your entries as if someone else wrote them. Could you repeat each one from the log alone? If not, add what is missing.