Practice lab · ICUD-003
Bring one real decision. Read one short idea, do one field-note action, say what would change your mind, then return to the map and see what you actually practiced.
The loop
Worked example · fictional
A fictional volunteer team needs to choose Saturday or Sunday for a small pilot. It records a chosen preference for Saturday, an assumption about room availability, an unknown attendance count, and a trigger: three confirmed Sunday attendees would reopen the decision. It is an illustrative exercise, not evidence about a real place, event, or person.
Practice modules
All modules are optional. Only Complete counts as practiced; Skipped remains distinct.
6–8 minutes · Start with the handle, not the whole life question.
Read
Name the action, scope, and evidence boundary in one sentence.
Do & reflect
Evidence boundary: A narrow question makes reasoning inspectable; it does not prove that the chosen action is good or that the outcome will occur.
6 minutes · Separate observed inputs from the rest.
Read
Known values can carry a source or measurement note.
Do & reflect
Evidence boundary: Writing an input under Known records your present classification. This learning system does not independently verify it.
6 minutes · Let preferences stay preferences.
Read
Chosen values are deliberate preferences, not hidden facts.
Do & reflect
Evidence boundary: A stated preference explains the model’s scope. It does not turn that preference into a verified fact or universal rule.
8 minutes · Make dependence visible.
Read
An assumption should show why it is used, impact if wrong, and a way to verify.
Do & reflect
Evidence boundary: The register makes dependence visible. It neither validates the assumption nor estimates how likely it is to be correct.
6 minutes · Do not turn a gap into zero.
Read
Unknown inputs can remain visibly incomplete.
Do & reflect
Evidence boundary: Naming a gap prevents false precision. It does not resolve the gap or determine whether proceeding is safe.
8 minutes · Let ambiguous changes interrupt you.
Read
Preserve inputs when meaning is stable; clear or confirm when it is not.
Do & reflect
Evidence boundary: This thought test identifies semantic risk. It does not guarantee that a real conversion or migration is complete.
8 minutes · Make the path from input to action inspectable.
Read
Show the model in ordinary language so disagreement can be productive.
Do & reflect
Evidence boundary: An inspectable chain supports review and disagreement. It does not make weak inputs strong or judgment objective.
8 minutes · Keep why, not only what.
Read
A saved answer without its assumptions is only a souvenir.
Do & reflect
Evidence boundary: A versioned record preserves what you believed at a point in time. It is not a promise that old reasoning remains current.
8 minutes · Say where support ends.
Read
State what the record demonstrates, then stop where observation and testing stop.
Do & reflect
Evidence boundary: A boundary statement is not professional advice, a safety finding, or proof of a real-world outcome.
8 minutes · Make revision a planned part of the decision.
Read
A review trigger gives future evidence somewhere useful to land.
Do & reflect
Evidence boundary: A review trigger supports disciplined revision. It cannot guarantee that you will receive, recognize, or correctly interpret new evidence.
“Practiced” means you marked a module complete. It does not mean ICU checked your answer or that a decision is correct, safe, current, or professionally reviewed.
This companion uses only existing first-party ICU material: the O023 book, O027 course, and O026 field notes. No external, documentary, or generated media is included. The Cedar Room example is fictional interpretation.
modules.json · progress contract · provenance · search benchmark