| Mathematical usefulness | Graphs, categories, tuples, algebra, morphisms, paths, slices, quotients, folds, refinements, factorizations, and wiring can expose structure that prose misses. | Mathematical form can look stronger than the claim it can carry. |
| EoC separation | The selected E.18 TFS or E.18.NET network, its E.18.2 mathematical description, its E.17 publication, and its C.29 lens-use adequacy are different values. | One visible source or publication face may present all of them at once. |
| Composition and decomposition | One TFS and recursive TFS networks need reviewable composition, factorization, slice, fold, and refinement claims. | The expression can hide which exact E.18 TFS, E.18.NET network, or independently identified part is being described. |
| Publication usability | Readers need diagrams, tables, equations, and views. | A publication face can be mistaken for evidence, gate passage, or performed work. |
| Related-claim economy | Apply E.18 to select one exact flow structure, A.3.4 to identify one actual bounded change, E.17 to publish a face, A.20 or A.21 to obtain validity or gate results, A.15 to identify plans or Work, and C.30 to state an architecture claim. | Repeating those patterns’ boundary doctrine inside E.18.2 creates fanout. |