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 08:25:59 UTC · snapshot created 2026-10-03 08:26:43 UTC · last check 2026-10-03 10:05:06 UTC

Table of Contents

Public units

UnitTitleUse
ReadmeNotational Engineering - ReadmeFollow connected notational work.
PrefaceNotational Engineering - PrefaceUnderstand the connected methods, their rationale, sources and limits.

Part A - Design what can be expressed and done

§ID & TitleStatusKeywords & Search QueriesDependencies
1NOT.1 - Choose the Distinctions and Operations a Notation Must SupportUsable, evolvingnotation design; reader operation; consequential distinction; expression gallery; requirement. What must a reader distinguish, infer or change using this notation?C.2.8 for recovered structure; A.6.3.RT.OE for an expression under available rules; NOT.2/.3/.7 for construction and repair.
2NOT.2 - Define Expression Rules for Recoverable Binding and CompositionUsable, evolvingsyntax; grammar; grouping; binding; scope; reference; composition. Which rules let users form expressions and recover their grouping, name bindings and connections?NOT.1 for the operation; A.6.3.RT for relation and expression distinctions; NOT.3/.4 and CMP.12 for interpretation and transformation.
3NOT.3 - Give Expressions an Operative InterpretationUsable, evolvingsemantics; interpretation; tacit operation; diagram reading; consequence; evaluator. Which operations let a prepared reader obtain a result from these signs?NOT.2 for formed expressions; MATH.18 for mathematical interpretation; CMP.12 when an effective interpreter is needed.
4NOT.4 - Construct Transformations of Expressions That Preserve Their UseUsable, evolvingrewrite; substitution; graph transformation; side condition; preserved observation; equality saturation. Which expression changes preserve the receiving use, and under what conditions?NOT.2/.3 for binding and meaning; MATH.17/.18 for composition and interpretation; CMP.12 for executable transformation.

Part B - Translate, combine and improve notations

§ID & TitleStatusKeywords & Search QueriesDependencies
1NOT.5 - Translate between Notations while Tracking Lost DistinctionsUsable, evolvingtranslation; abstraction; many-to-one mapping; information loss; complement; round trip. What can the receiver recover, and which discarded distinctions must accompany the translation?NOT.3 for the interpretation; MATH.2/.7/.18 for identification and preserved relations; NOT.6 for continued joint use.
2NOT.6 - Coordinate Complementary Representations through Shared ReferencesUsable, evolvingmultiple representations; shared reference; linked view; synchronization; update intent; constraint conflict. Which correspondences let readers combine results and propagate an intended change between representations?NOT.5 for translation limits; MATH.18 and C.29 for correspondence; ME.9 when representations describe a working method.
3NOT.7 - Redesign a Notation around the Reader’s Difficult OperationsUsable, evolvingnotation redesign; cognitive dimensions; dependency; editing burden; preparation; comparison. Which change makes the difficult operation easier, and where does it move effort?NOT.1–.6 for requirements and operative rules; C.2.8, EXD and HCD for recovery, explanation and capability questions.
4NOT.8 - Construct Temporal or Embodied Notation with a Reading ProcedureUsable, evolvingtemporal notation; embodied notation; rhythm; gesture; frame; segmentation; replay; enactment. How can order, duration or movement be expressed with a usable reading procedure?NOT.1–.7 for design and interpretation; CMP.12 for an effective interpreter; B.5.MPC for physical realization.