Library / Notational Engineering DPF
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 05:45:20 UTC

NOT.6:4.5 - Propagate the intended change and expose conflicts

Identify what changed and what the change asks to preserve. Separate an explicit new requirement from values merely retained in an old display. A change to one coefficient can require several table cells to change even if those cells were not directly edited.

Follow the affected references and derivations. Recompute dependent contributions or update their correspondence; leave independent information unchanged unless the subject work calls for its revision. If a representation no longer agrees and cannot yet be updated, make that limitation visible before its next joined use.

When edits arrive through several representations, combine their requirements and check whether a compatible result exists. The result can be several admissible revisions or a conflict. Do not manufacture a unique update when the supplied constraints leave a choice; use the declared policy or obtain the missing decision.

Distinguish changes with the same visible outcome but different meanings. Removing an item from an unfinished-work list can mean completion, cancellation or deletion. The intended action determines which other representations change. A suitable change description can be more informative than comparing two finished displays.

If a model and an observation disagree, return to their governing subject account. Updating the observation to match the model would destroy the independent contribution; changing the model may require a modeling decision. Coordination makes the disagreement usable rather than hiding it.