Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-16 21:18:08 UTC · snapshot created 2026-11-16 21:19:40 UTC · last check 2026-11-17 19:35:15 UTC

E.8:4.2.1.3 - Choose examples by the explanation they make usable

Determine the content owed to the reader from the subject, declared scope and receiving work. Include the relations, grounds, alternatives and conditions needed for that work; do not let the circumstances of a convenient example decide which of them to explain. This is a priority in deciding adequacy, not a compulsory order of discovery or presentation.

A case, sketch or attempted calculation can reveal a missing relation before the general account is finished. Carry that discovery back into the account and distinguish a reusable condition from an incidental feature of the case.

When the reader is learning to model a domain, say what the reader must do with the domain’s own types. For a transdisciplinary principle, explain which distinction applies to those types, how to recognize the relation and what inference it warrants. For a domain principle, supply the field’s own rule and its conditions. If the intended result is a way of working, explain how to select or construct the next operation, what it produces, and which dependent choices to revisit when its grounds change. A single publication may teach all of these. On unfamiliar material, ask the reader to select, relate or revise the local types and use them to reach a result in the recipient’s terms. A worked case makes that reasoning inspectable. C.39.WA:4.3 distinguishes the relations used in such inferences.

When an author uses a case to test an independent choice, identify the choice the prompt leaves open, the sources and help available at that point, and what the learner actually supplied. A problem statement in a brief can support a test of evaluating that formulation. To test formulating the problem, use work in which the learner still had to frame it. An earlier working record can supply that evidence. E.23.CDI:4.2.1 guides the separate decision about how a holder can acquire and demonstrate a capability under its working conditions.

Keep the explained subject and its example distinguishable. When teaching a Method, identify the reusable way, the actual or stipulated performance that illustrates it, and the material on which that performance works. Show which choice or action in the example enacts which operation and why its result is usable next.

In an explanation-design pattern, a calculation of a mean can be material supplied to the explainer; selecting unequal groups to expose a misleading shortcut illustrates the explainer’s Method. Correct arithmetic supplies the mathematical result. The account of selecting and using the contrast explains the teaching move. These contributions can appear together without changing the pattern’s subject to arithmetic.

Make the common claim, its scope and its grounds available in the explanation. It may be expressed alongside cases, through a derivation or through a named accessible supplier. State what may vary and which conditions make the relation or operation applicable.

If the text calls the example a stricter model, compare the two models for the same inquiry under B.5.MR.

When cases suggest a new general claim, develop and qualify that claim through the relevant subject Method. A constructed instance can demonstrate an operation, a counterexample can defeat a universal claim, and observed cases can contribute empirical evidence; the wider inference retains the grounds appropriate to that use.

Select an example for the contribution it makes: making an unfamiliar relation inspectable, exposing an intermediate operation, distinguishing plausible rules, showing a boundary, or connecting several Methods in use. Work the correspondence between the account and the instance.

A correct answer can fit more than one rule; choose values or a comparison that lets the reader distinguish the intended relation. Preserve adequate direct explanation when an additional example would contribute nothing to the declared use.

Archetypal Grounding remains a content function of a canonical pattern; it is not a requirement to insert an example into every paragraph, slide or section derived from that pattern.

Choose meaningful variety from the promised subject. Recover the differences in objects, relations, conditions, available grounds and receiving work that the account must handle. Select cases that make those differences intelligible, including ordinary applications as well as contrasts and limits.

A numerical derivation, a causal explanation with uncertain evidence and a recommendation under competing purposes can require different explanatory moves. Changing numbers within a derivation does not supply the other two.

Several materially different examples may be necessary to ground a general account even when each example is locally simple. Explain what remains common across them and what changes for a subject-specific reason.

For human learning, HCD.5:4.2.1 and HCD.6.1:4.2.2 connect explanations with a distribution of qualified encounters and focused contrasts. Use that contribution when a learner must recognize or use a family that one pair cannot expose. A demonstrated distinction can be available before a complete verbal rule; preserve its qualified examples and conditions instead of inventing a formula. The framework author’s obligation is to make the claimed commonality and its basis usable, including the limits of what has been explained.

Decide whether to continue the same case. Continuity can make an earlier result, a changing state or the consequences of a choice available to the next operation. It can also avoid reintroducing circumstances the reader already understands. Retain that benefit when the case still shows the relations now needed.

At each consequential transition, return to the subject being explained: which operation or principle is this instance making usable? If a new question needs different objects, a competing method or a condition the case cannot represent faithfully, change the case, juxtapose a contrasting one or use a direct explanation.

Keep the general reasoning connected while examples change. Retain the varied cases needed for that account; shorten incidental story development when it displaces the next required connection.

Check the account at its promised scope. Compare what the explanation lets the intended reader recover with what the subject and receiving work require. The reader should be able to explain the governing relation, its grounds and conditions, and use it across the material variations included in the promise. Choose those variations from the subject, not only from what is easy to change inside the chosen setting.

Inspect the correspondence back to the Method or principle being taught as well as the correctness of the example’s domain result. Supply a missing general operation, explanation or accessible supplier; add or revise cases when the required correspondence or variation remains hard to recover. Use F.19’s evidence and coverage conditions for a reader-recovery conclusion.

For example, a continuing transaction can show why a later update must use the state produced by an earlier one: retaining the same transaction makes that dependency visible. In an account of resource use across Methods, show the different relations of a consumable specimen and reusable information. Explain consumption and reuse, then show how each changes the receiving operation.

The author’s reusable move is to select and connect cases by the relations owed to the reader; the transaction, specimen and information are the material used to perform that move. A reader who already understands a short algebraic derivation may need no narrative case for that inference. These are choices about the contribution required, not a fixed allocation of examples.