Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-21 17:39:26 UTC · snapshot created 2026-11-21 17:40:20 UTC · last check 2026-11-21 18:05:10 UTC

A.22:4.1d - Transformation-flow structure network profile

Use E.18.NET when one engineering use selects two or more independently identified transformation-flow structures, or nested networks of them, together with obtaining relations across their boundaries. Apply the four A.22 discriminators: the TFS or nested-network members are the constituents; the cross-member relation occurrences satisfy their defining predicates and identity rules; the applied endpoint, boundary-exposure, and acyclic direct-member constraints are selected under E.18.NET; and the named network-use frame states the practical question, admissible action, and stop or return condition.

Any optional explanatory overread follows F.19:4 and remains outside structure identity. The return condition reopens selection when a member, relation, constraint, or use-frame value changes and is not a fifth identity discriminator. The result is one dependent, non-agentive U.Structure specialization. E.18.NET defines the network’s detailed identity, reference, recursion, local-state, and conformance rules; A.22 does not copy those fields.

Use the first discriminator to record structure constituents. Introduce a separately re-identifiable world-side membership relation only when a receiving use needs it and can supply its participants, obtaining predicate, and identity rule.