| E.18 TFS paths, crossings, valuations, and E.18.NET network structure become usable across actual architecture relations, bounded claims, selected architecture structures, structural views, and conditional descriptions without merging owners. | Every use names the architecture locus. A network use also distinguishes the actual containing-holon, single-holon claim, or explicit inter-holon branch and keeps every characteristic on a named bearer. |
| Required functional content, transformation-flow structure, and actual transformation stay separable. | Concise “the diagram is the architecture/change” prose is repaired before it carries an FPF claim. |
| Non-flow claim kinds are assigned to their governing patterns. | More governing patterns are named when practitioners try to overuse the diagram, mathematical expression, or selected structure. |
| The E.18 selected-structure boundary stays narrow. | Generic architecture adequacy remains outside E.18. |