Source changed 2026-10-03 14:36:52 UTC · snapshot created 2026-10-03 14:38:14 UTC · last check 2026-10-03 15:25:20 UTC
E.18.2:4.6 - Bias-Annotation
Bias
How E.18.2 prevents it
Graph-as-world bias
One selected TFS stays with E.18, and one selected network stays with E.18.NET. A graph or algebraic object used in E.18.2 retains its mathematical kind; a stronger claim needs the result returned by the pattern whose Solution answers that question.
Path-as-procedure bias
A mathematical path or path slice can express reachability or locality; method and work-plan claims stay with method and work-plan patterns.
Diagram-as-architecture bias
Architecture adequacy stays with C.30, C.30.ASV, and related architecture patterns; E.18.2 records only the mathematical-description relation.
Math-as-authority bias
No mathematical expression authorizes work, passes a gate, settles evidence, grants release, or proves assurance by itself.
Publication-as-description bias
Publication faces and rendered diagrams stay with E.17 unless the current EntityOfConcern is the mathematical description itself.