Show where every supported answer came from
Attach visible source, date, limitation and confirmation information to every supported answer.
01 · Understand
Why this issue exists
An answer without evidence can sound confident while being outdated, incomplete or unapproved.
02 · Investigate
Broken record exercise
Four blank labels are not evidence
A classroom record matches the question but has no source title, route, date or limitation. The interface could hide the blank labels—or the service could withhold the unsupported answer.
- 1Should the answer still be shown?
- 2Which evidence fields are mandatory?
- 3Where should evidence validation happen?
- 4What is the difference between confirmed and review-pending?
03 · Decide
What should happen when required evidence is incomplete?
04 · Make the thinking visible
Team workspace
Discuss first, then record the team’s reasoning. These notes stay in this browser until you copy them.
Explain what each field tells the customer: title, route, date, limitation and confirmation.
State exactly when evidence is complete enough for a supported answer.
How will a customer see that content awaits written NIS confirmation?
05 · Scaffold
Model evidence as part of the answer contract
Do not paste citation text into the interface. Complete the validation behaviour so every future interface receives the same evidence.
class Evidence:
source_title: str
source_route: str
as_of: str
limitation: str
confirmation: str
def is_complete(self) -> bool:
# Which fields are required, and what counts as empty?
...06 · Prove it
Evidence checklist
Tick an item only when the team can show the evidence and another student can explain it.
Push further
Stretch challenge
Design a test for an answer with a real-looking source title but no as-of date. Decide its severity and justify it.