E.8:4.2.1.2 - Construct the expression that supports the reader’s operation
Use this move when the needed explanation is available but the author still has to decide what the reader should read, compare, remember, manipulate or carry forward. It also applies when arranging incomplete material is how the reader will discover the question.
A representation can help produce a distinction that was not available before it was used. Its usefulness is not limited to storing a finished answer.
Begin with the reader’s operation and actual material. Try it with a sufficient existing expression before designing another one. Retain the reader’s preparation and available help from §4.2.1.1. If the operation itself is missing, develop or obtain it; rearranging its name cannot supply it.
A.6.3.RT.OE explains how to make an expression operative. Developing formation, interpretation or transformation rules is a separate notation-engineering task. The external Notational Engineering DPF (NOT) offers optional methods for that work.
Construct the contrast before choosing the format. Place together the pieces that the operation needs to distinguish or combine. They can still contain uncertain interpretations or an unanswered question. Attempt the comparison, grouping, substitution or inference.
Where it fails, determine whether a missing fact, a missing operation or the arrangement of the expression prevents the result. Change the arrangement when it hides or confounds an available distinction. Obtain a missing fact when the receiving operation requires it. Preserve an unresolved question when it is the useful result of this attempt.
The unit follows the operation. Two cases may need to remain adjacent to expose a difference; one thought may need to be independently movable without losing the reason it states; an instruction may need its prerequisite at the point of action. Start with these relations rather than a blank form inherited from another task. Stable labels and a small common structure can make repeated comparison possible. Retain those constraints while they help, and revise the one that suppresses a needed distinction.
Choose among expressions by what the reader does with them. Continuous explanation can keep a causal argument or an unfamiliar inference together. A mantra can help retain an already developed connection during work; it cannot teach a missing operation merely by naming it.
A table makes the same questions about several cases jointly inspectable. Its rows and columns need meaningful common interpretations, including the conditions under which values may be compared. A card makes a coherent contribution separately addressable and rearrangeable; explain what a connection between cards means.
A diagram can expose a relation whose incidence, order or spatial organization matters; the appearance of an arrow does not establish a dependency or cause. An executable expression can perform a specified operation, provided its inputs, interpretation, execution context and failure behavior are supplied.
These expressions may be combined. For example, a short explanation can establish a table’s interpretation, the table can support comparison, and a reminder can later cue that same operation. Select only the contributions needed by the intended use.
Expose the interpretation where it is used. A column headed Date can leave its event, role and unit unresolved. A row can represent an observation, an attempted operation, a relation or a claim rather than one physical object.
State the distinctions that affect the operation, including what an empty position means. A missing observation is not zero; a not-applicable question differs from an unanswered one. Use the domain’s kinds, quantities and roles and the relevant FPF distinctions where they settle such a difference.
Distinguish content that must be available from content the practitioner must enter again. A visible value may be derived from a qualified source or retrieved from another record. Show that return when it matters, and require manual entry only for the contribution the person supplies. An illustrative table in a pattern is not automatically a record schema for every performance.
Place, retain and change the support. Place an interpretation or prerequisite beside the first operation that depends on it. Place a reusable example where its intermediate result can be inspected. Keep assurance conditions available before consequential reliance even if their derivation is elsewhere.
If a form will travel without the surrounding prose, carry the interpretation and source return needed in that separated use. A direct link can be sufficient when the recipient has the access and can recognize when to follow it.
Compare the candidate with the best simpler expression by performing the same use at the same preparation. Retain a sufficient existing form when no worthwhile gain is shown. Remove a field or whole support when its contribution is unnecessary or supplied more effectively elsewhere, checking the use that previously depended on it.
Rework instead of adding a second copy when the existing expression contains the right material in an unhelpful arrangement. Add a new support when an operation remains unavailable or requires avoidable reconstruction. Revisit this choice when the question, source, recipient or separation from context changes.
An expert construction establishes what that construction makes available; evidence of reader success or lower effort requires an actual reading under stated conditions.
Worked choice: a date conversion and the form that teaches it. The explanation in §4.2.1.1 requires a source-to-order selection before conversion. Supplier North guarantees month/day/year; South guarantees day/month/year for the files at issue. The intended reader can run a converter given a date order. The author’s task here is to choose an expression that makes the selection, its reason and its limit usable.
Begin with the tempting two-column arrangement:
| Raw text | ISO date |
|---|---|
03/04/2026 | 2026-03-04 or 2026-04-03? |
The cell exposes an unresolved interpretation; selecting one output by appearance would invent information. The author asks what differs between the two legitimate conversions. The supplier guarantees distinguish the two interpretations. Rework the comparison:
| Source of this row | Raw text | Interpretation supplied by the applicable guarantee | Converter result |
|---|---|---|---|
| North | 03/04/2026 | month/day/year | 2026-03-04 |
| South | 03/04/2026 | day/month/year | 2026-04-03 |
The unchanged raw characters and different results remain adjacent. The table expresses the source-to-interpretation relation which the two-column prototype lost. The surrounding explanation shows how the applicable guarantee determines the date order and why guessing from the characters is invalid.
Source designates the supplier for this row; the interpretation is an input to conversion derived from that supplier’s guarantee, not a newly observed property of the date. Neither the interpretation nor the output must be manually recopied by every user.
A separate card for each row would make this small comparison harder to inspect together without supplying a needed rearrangement. A dependency diagram can explain the same selection when its connections become the difficult part, but adds no needed distinction to these two rows. The table and its short explanation therefore serve this example.
For experienced users, “use the applicable source order; do not infer it from an ambiguous date” is a recall cue with a return to the explanation. It does not replace that explanation for someone learning the selection.
Now change the receiving use. A work session contains only North files under one applicable guarantee, and the converter receives that fixed order from the session’s qualified configuration. A repeated source and order entry in every manually completed row supplies nothing further to this session’s conversion. Remove those repeated inputs from the local working view; retain the scope statement and its return to the guarantee. The two-column raw/result view is sufficient there.
If a row is later exported alone or South material enters the session, that contextual supply no longer suffices: recover the row’s source and applicable order before conversion. This is a conditional removal, not a claim that source identity never matters.
In a different change, South starts using mixed orders and supplies no row-level interpretation. Preserve North’s results and the earlier qualified South results. Mark the ambiguous new South row as unresolved; neither a fuller form nor running the converter twice chooses its meaning.
Obtain trustworthy row-order information or correctly matched converted dates before relying on that result. The unknown blocks that conversion, not every other row.
Apply the construction to the pattern’s own arrangement. Keep the selection operation and its use-changing conditions in Solution. Keep the small comparison with the instruction that interprets it; a distant collection of unexplained forms would make the reader reconstruct the missing connection.
The canonical sections and stable addresses organize publication and return. They need not become the author’s order of discovery: rough notes can reveal the source-to-order problem before the first pattern body is composed. Once a pattern body is authored, §4.1 governs its canonical frame; the external notes are not a substitute for its unfinished content.
The raw/result prototype, the source-qualified comparison and the reduced single-source view expose why different forms support the same conversion in different conditions. They are worked constructions, not observations of improved learning or production performance.