Section 308 of 440

Complete canonical tutorial. This reader section contains the same teaching body as PWR-126 · Uncertainty communication. Open the Power dossier.

PWR-126 · Metacognition & Epistemic Resilience

Repair a fictional delivery estimate until a reader can teach it back

Communicating uncertainty means stating the estimate, its basis, a meaningful limit, and what changes the next action. This pack supplies a harmless delivery dataset, three draft messages, reader teach-backs, and a six-item scoring checklist. The learner repairs misunderstanding rather than chasing reassurance, trust, or persuasion.

Tutorial curriculum · current public edition · Revision 7T · Full Tutorial Edition

Revision 7T · Full Tutorial Edition · complete governed practice tutorial

Repair a fictional delivery estimate until a reader can teach it back

Communicating uncertainty means stating the estimate, its basis, a meaningful limit, and what changes the next action. This pack supplies a harmless delivery dataset, three draft messages, reader teach-backs, and a six-item scoring checklist. The learner repairs misunderstanding rather than chasing reassurance, trust, or persuasion.

Authority and safety

  • Use only the fictional archive-box scenario; do not adapt it to medicine, crisis response, politics, finance, legal advice, or another high-stakes message.
  • Comprehension is the target. A clear message can still be based on an uncertain or wrong estimate.
  • The reader may disagree or decline; no persuasion or non-consensual testing is authorised.

Exact materials

  • The fictional delivery scenario in the fixture caption
  • A blank baseline-message and teach-back prediction worksheet
  • The six-item checklist: window, number plus plain language, source, limit, action and change trigger
  • The uncertainty labels ALEATORY, EPISTEMIC and MIXED
  • The staged model message and teach-back key, opened only after the learner's baseline and repair are locked

Set up in this order

  1. Read only the scenario caption. Write your own baseline message and one expected reader teach-back before opening the staged key.
  2. Calculate in-window, early and late proportions from all 80 deliveries.
  3. Name the uncertainty: delivery-to-delivery variation is aleatory; uncertainty about whether history still represents the new backlog is epistemic; together the message has mixed uncertainty.
  4. Score your baseline for window, number plus plain language, source, limit, action and change trigger. Preserve the first score.
  5. Compare your expected teach-back with the data. Mark any invented guarantee, missing source, missing variability or missing trigger.
  6. Repair your own message without stronger reassurance and write a second teach-back prediction.
  7. Open the staged model only now. Compare field by field and record what your repair still missed; never rewrite the baseline as if the model had been known.

Supplied fixture

Scenario: of 80 similar deliveries, 56 arrived Tuesday–Thursday, 12 earlier and 12 later. A new carrier backlog may make history less representative. If absent Thursday at 17:00, the fictional coordinator asks for an update. The fixture is blank so the baseline cannot be contaminated by a supplied draft.
StageLearner messageExpected reader teach-backUncertainty typeChecklist score out of 6Missing element or repair
Baseline — key closed[write][predict][classify][score][preserve omissions]
Repair — key still closed[rewrite][predict again][preserve classification][rescore][state exact repair]
Model comparison — key open[do not copy into baseline][compare][check][compare][record remaining gap]

Check your work only after you finish

Lock every response first. The checking page is separate so the answers are not exposed inside this exercise.

Open the separate checking page →

Scoring rule

Award 1 point for each of the six explicit message elements, 1 for a correct MIXED uncertainty classification and 1 for a teach-back that preserves estimate, uncertainty and trigger: 8 total. Baseline and repair remain separate. Opening or copying the staged model before locking the repair invalidates the baseline comparison.

Worked example

  1. Verify M2's number: 56/80=70%, so the arithmetic is correct.
  2. Score M2 at 2/6 for time window and 70%/7-in-10 wording.
  3. Use the teach-back to find guarantee and missing-source errors.
  4. Add 56 of 80, 12 early, 12 late, the backlog limit, current action, and Thursday 17:00 trigger.
  5. Compare the repaired M3 teach-back with every source field.

Correct result: The repaired M3 scores 6/6 and supports accurate teach-back without implying that 70% is certainty.

Right and wrong

Right and wrong comparison
MomentRight / saferWrong / riskierWhy
Numbers and words70%, about 7 in 10 of 80.Probably soon.Vague wording hides range and reference class.
LimitationBacklog may reduce relevance.Eighty cases make it certain.Changed conditions remain important.
ComprehensionAsk for estimate-limit-trigger teach-back.Ask whether it feels trustworthy.Trust does not prove understanding.
ActionNo action now; update if absent at the trigger.Wait indefinitely because 70% reassures.A usable message includes a change condition.

Common mistakes and fixes

Common mistakes and corrections
MistakeFix
Percentage without denominator.Add 56 of 80 and about 7 in 10.
Hiding changed conditions.Name the new backlog.
Treating silence as comprehension.Use the supplied teach-back checklist.
Repairing with stronger reassurance.Rewrite the missing estimate, source, limit, or trigger.

Evidence boundary

What the tutorial may—and may not—claim.

Supportable claim

Numeric uncertainty can often be communicated without large trust loss, while wording and cultural context materially affect reception.

Measurement boundary

Declare uncertainty type, format, source, audience, language, comprehension, trust, decision and equity; trust is not the sole success criterion.

Myth

Use the perfect phrase and everyone will understand risk

Metric

Comprehension, calibrated trust and decision quality for a declared uncertainty message

Boundary

A trusted message is not necessarily understood, accurate, fair or actionable.

Negative and limiting findings

  • Vague verbal uncertainty could reduce trust.
  • Effects differed by country, source and topic, and comprehension/decision quality were not always established.

Prohibited wording

  • one perfect uncertainty phrase
  • numbers make communication objective
  • trust proves understanding
  • AI can calibrate any message automatically

Direct source register

Evidence that supports—and limits—the route.

The effects of communicating uncertainty on public trust in facts and numbers

Anne Marthe van der Bles; Sander van der Linden; Alexandra L. J. Freeman; David J. Spiegelhalter · 2020 · PRIMARY_RESEARCH

Supports only the bounded empirical proposition in the declared configurations. Constrains generalisation, transfer, certainty or efficacy; it is not optional context.

The effects of communicating uncertainty around statistics, on public trust

John Kerr; Anne-Marthe van der Bles; Sarah Dryhurst; Claudia R. Schneider; Vivien Chopurian; Alexandra L. J. Freeman; Sander van der Linden · 2023 · PRIMARY_RESEARCH

Supports only the bounded empirical proposition in the declared configurations. Constrains generalisation, transfer, certainty or efficacy; it is not optional context.

Artificial Intelligence Risk Management Framework (AI RMF 1.0)

National Institute of Standards and Technology · 2023 · OFFICIAL_FRAMEWORK

Constrains generalisation, transfer, certainty or efficacy; it is not optional context. Supplies an official safety, access or governance boundary and is not empirical efficacy evidence.

Tutorial delivery controls

Learn, adapt, troubleshoot and resume

Estimated timeEstimated 17 min reading and worksheet pass
DifficultyIntroductory
EquipmentBasic stationery or digital tools
SpaceDesk / seated
Method qualityEstablished10 of 10 structural checks present. Automated method-readiness band; human editorial sign-off is separate.
Evidence contextG1; Focused research depthScientific support is evaluated separately from teaching-method structure.
Editorial reviewPending manual sign-offNo human approval is claimed until reviewer, date and content hash are recorded.
Your tutorial progress0 of 7 steps complete
0 of 7 steps complete
Download learner worksheet

Progress is saved only in this browser on this device.

Step-by-step learner mode

Each activity includes its success check, a nearby accessible alternative and an “I’m stuck” correction path. Alternatives preserve the target where possible; when they change the task, Titan labels them as related rather than equivalent.

01

Read only the scenario caption

Read only the scenario caption. Write your own baseline message and one expected reader teach-back before opening the staged key.

Why this step exists

“Read only the scenario caption” creates the auditable value, condition or statement needed for the tutorial’s later comparison and conclusion.

Success check

A legible entry directly completes “Read only the scenario caption” and records the requested condition, decision or boundary without adding a new claim.

I’m stuck on this step

Reset: Re-read this authored instruction — “Read only the scenario caption. Write your own baseline message and one expected reader teach-back before opening the staged key.” — and its success check, then attempt only this step.

  1. Possible snag: Treating silence as comprehension.

    Correction: Use the supplied teach-back checklist.

Stop / get help: A governed step-by-step lesson may be completed independently inside its stated limits. Stop if the declared configuration cannot be maintained, uncertainty becomes material, adverse effects appear, or qualified authority is required.

02

Calculate in-window, early and late proportions from all 80 deliveries

Calculate in-window, early and late proportions from all 80 deliveries.

Why this step exists

“Calculate in-window, early and late proportions from all 80 deliveries” creates the auditable value, condition or statement needed for the tutorial’s later comparison and conclusion.

Success check

The work shows the value requested by “Calculate in-window, early and late proportions from all 80 deliveries”, retains the supplied units or signs and leaves any unsupported value unknown.

I’m stuck on this step

Reset: Re-read this authored instruction — “Calculate in-window, early and late proportions from all 80 deliveries.” — and its success check, then attempt only this step.

  1. Possible snag: The result from “Calculate in-window, early and late proportions from all 80 deliveries.” does not yet meet this declared check: The work shows the value requested by “Calculate in-window, early and late proportions from all 80 deliveries”, retains the supplied units or signs and leaves any unsupported value unknown.

    Correction: Return to the start of “Calculate in-window, early and late proportions from all 80 deliveries”, reduce complexity or pace, and repeat only the part needed to satisfy: “The work shows the value requested by “Calculate in-window, early and late proportions from all 80 deliveries”, retains the supplied units or signs and leaves any unsupported value unknown.”

Stop / get help: A governed step-by-step lesson may be completed independently inside its stated limits. Stop if the declared configuration cannot be maintained, uncertainty becomes material, adverse effects appear, or qualified authority is required.

03

Name the uncertainty: delivery-to-delivery variation is aleatory

Name the uncertainty: delivery-to-delivery variation is aleatory; uncertainty about whether history still represents the new backlog is epistemic; together the message has mixed uncertainty.

Why this step exists

“Name the uncertainty: delivery-to-delivery variation is aleatory” establishes the exact Uncertainty communication question or boundary that every later comparison must preserve.

Success check

Evidence of completion shows the learner followed this exact instruction without adding an unstated step: “Name the uncertainty: delivery-to-delivery variation is aleatory; uncertainty about whether history still represents the new backlog is epistemic; together the message has mixed uncertainty.”

I’m stuck on this step

Reset: Re-read this authored instruction — “Name the uncertainty: delivery-to-delivery variation is aleatory; uncertainty about whether history still represents the new backlog is epistemic; together the message has mixed uncertainty.” — and its success check, then attempt only this step.

  1. Possible snag: Percentage without denominator.

    Correction: Add 56 of 80 and about 7 in 10.

  2. Possible snag: Hiding changed conditions.

    Correction: Name the new backlog.

Stop / get help: A governed step-by-step lesson may be completed independently inside its stated limits. Stop if the declared configuration cannot be maintained, uncertainty becomes material, adverse effects appear, or qualified authority is required.

04

Score your baseline for window, number plus plain language, source, limit, action…

Score your baseline for window, number plus plain language, source, limit, action and change trigger. Preserve the first score.

Why this step exists

“Score your baseline for window, number plus plain language, source, limit, action and change trigger” creates the auditable value, condition or statement needed for the tutorial’s later comparison and conclusion.

Success check

The work shows the value requested by “Score your baseline for window, number plus plain language, source, limit, action and change trigger”, retains the supplied units or signs and leaves any unsupported value unknown.

I’m stuck on this step

Reset: Re-read this authored instruction — “Score your baseline for window, number plus plain language, source, limit, action and change trigger. Preserve the first score.” — and its success check, then attempt only this step.

  1. Possible snag: The result from “Score your baseline for window, number plus plain language, source, limit, action and change trigger. Preserve the first score.” does not yet meet this declared check: The work shows the value requested by “Score your baseline for window, number plus plain language, source, limit, action and change trigger”, retains the supplied units or signs and leaves any unsupported value unknown.

    Correction: Return to the start of “Score your baseline for window, number plus plain language, source, limit, action…”, reduce complexity or pace, and repeat only the part needed to satisfy: “The work shows the value requested by “Score your baseline for window, number plus plain language, source, limit, action and change trigger”, retains the supplied units or signs and leaves any unsupported value unknown.”

Stop / get help: A governed step-by-step lesson may be completed independently inside its stated limits. Stop if the declared configuration cannot be maintained, uncertainty becomes material, adverse effects appear, or qualified authority is required.

05

Compare your expected teach-back with the data

Compare your expected teach-back with the data. Mark any invented guarantee, missing source, missing variability or missing trigger.

Why this step exists

“Compare your expected teach-back with the data” isolates the named evidence distinction so the learner can interpret Uncertainty communication without extending the claim.

Success check

The output directly answers “Compare your expected teach-back with the data”, names the relevant distinction and stays within the supplied record.

I’m stuck on this step

Reset: Re-read this authored instruction — “Compare your expected teach-back with the data. Mark any invented guarantee, missing source, missing variability or missing trigger.” — and its success check, then attempt only this step.

  1. Possible snag: Repairing with stronger reassurance.

    Correction: Rewrite the missing estimate, source, limit, or trigger.

Stop / get help: A governed step-by-step lesson may be completed independently inside its stated limits. Stop if the declared configuration cannot be maintained, uncertainty becomes material, adverse effects appear, or qualified authority is required.

06

Repair your own message without stronger reassurance and write a second teach-back…

Repair your own message without stronger reassurance and write a second teach-back prediction.

Why this step exists

“Repair your own message without stronger reassurance and write a second teach-back prediction” creates the auditable value, condition or statement needed for the tutorial’s later comparison and conclusion.

Success check

A legible entry directly completes “Repair your own message without stronger reassurance and write a second teach-back prediction” and records the requested condition, decision or boundary without adding a new claim.

I’m stuck on this step

Reset: Re-read this authored instruction — “Repair your own message without stronger reassurance and write a second teach-back prediction.” — and its success check, then attempt only this step.

  1. Possible snag: The result from “Repair your own message without stronger reassurance and write a second teach-back prediction.” does not yet meet this declared check: A legible entry directly completes “Repair your own message without stronger reassurance and write a second teach-back prediction” and records the requested condition, decision or boundary without adding a new claim.

    Correction: Return to the start of “Repair your own message without stronger reassurance and write a second teach-back…”, reduce complexity or pace, and repeat only the part needed to satisfy: “A legible entry directly completes “Repair your own message without stronger reassurance and write a second teach-back prediction” and records the requested condition, decision or boundary without adding a new claim.”

Stop / get help: A governed step-by-step lesson may be completed independently inside its stated limits. Stop if the declared configuration cannot be maintained, uncertainty becomes material, adverse effects appear, or qualified authority is required.

07

Open the staged model only now

Open the staged model only now. Compare field by field and record what your repair still missed; never rewrite the baseline as if the model had been known.

Why this step exists

“Open the staged model only now” creates the auditable value, condition or statement needed for the tutorial’s later comparison and conclusion.

Success check

A legible entry directly completes “Open the staged model only now” and records the requested condition, decision or boundary without adding a new claim.

I’m stuck on this step

Reset: Re-read this authored instruction — “Open the staged model only now. Compare field by field and record what your repair still missed; never rewrite the baseline as if the model had been known.” — and its success check, then attempt only this step.

  1. Possible snag: The result from “Open the staged model only now. Compare field by field and record what your repair still missed; never rewrite the baseline as if the model had been known.” does not yet meet this declared check: A legible entry directly completes “Open the staged model only now” and records the requested condition, decision or boundary without adding a new claim.

    Correction: Return to the start of “Open the staged model only now”, reduce complexity or pace, and repeat only the part needed to satisfy: “A legible entry directly completes “Open the staged model only now” and records the requested condition, decision or boundary without adding a new claim.”

Stop / get help: A governed step-by-step lesson may be completed independently inside its stated limits. Stop if the declared configuration cannot be maintained, uncertainty becomes material, adverse effects appear, or qualified authority is required.

Correct versus incorrect execution

These accessible process diagrams are built from the tutorial’s own right/wrong teaching. They are not anatomical illustrations and do not add technique beyond the canonical tutorial.

Numbers and words — Vague wording hides range and reference class.
PWR-126 correct and incorrect comparison: Numbers and wordsNumbers and words. Correct or safer: 70%, about 7 in 10 of 80.. Wrong or riskier: Probably soon.. Why: Vague wording hides range and reference class.SITUATIONNumbers and wordsCORRECT / SAFER70%, about 7 in 10 of 80.WRONG / RISKIERProbably soon.YESNO
Correct / safer

70%, about 7 in 10 of 80.

Wrong / riskier

Probably soon.

Limitation — Changed conditions remain important.
PWR-126 correct and incorrect comparison: LimitationLimitation. Correct or safer: Backlog may reduce relevance.. Wrong or riskier: Eighty cases make it certain.. Why: Changed conditions remain important.SITUATIONLimitationCORRECT / SAFERBacklog may reduce relevance.WRONG / RISKIEREighty cases make it certain.YESNO
Correct / safer

Backlog may reduce relevance.

Wrong / riskier

Eighty cases make it certain.

Comprehension — Trust does not prove understanding.
PWR-126 correct and incorrect comparison: ComprehensionComprehension. Correct or safer: Ask for estimate-limit-trigger teach-back.. Wrong or riskier: Ask whether it feels trustworthy.. Why: Trust does not prove understanding.SITUATIONComprehensionCORRECT / SAFERAsk for estimate-limit-trigger teach-back.WRONG / RISKIERAsk whether it feels trustworthy.YESNO
Correct / safer

Ask for estimate-limit-trigger teach-back.

Wrong / riskier

Ask whether it feels trustworthy.

Action — A usable message includes a change condition.
PWR-126 correct and incorrect comparison: ActionAction. Correct or safer: No action now; update if absent at the trigger.. Wrong or riskier: Wait indefinitely because 70% reassures.. Why: A usable message includes a change condition.SITUATIONActionCORRECT / SAFERNo action now; update if absent at the trigger.WRONG / RISKIERWait indefinitely because 70% reassures.YESNO
Correct / safer

No action now; update if absent at the trigger.

Wrong / riskier

Wait indefinitely because 70% reassures.

Method-structure checklist

10 of 10 structural checks present

  • Ordered, Power-specific instructions — present
  • Every activity has a success check — present
  • Materials or supplied records are declared — present
  • Measurement or assessment rule is present — present
  • Tutorial-specific troubleshooting is present — present
  • Stopping or escalation boundary is present — present
  • Every activity has an adjacent alternative — present
  • Correct-versus-incorrect comparison is present — present
  • Evidence context is bound to the Power record — present
  • Planning metadata is present — present

The method-readiness band and presence checklist assess tutorial presentation and are separate from evidence quality for the underlying Power. They are automated editorial aids, not human approval.

Manual editorial sign-off: Pending. This tutorial must not display a human-approved state until an identified editor signs the exact content hash.