E.18.2:10 - Relations

• Apply E.18’s one-TFS identity, allowed-locus, selection-constraint, and local-value rules to select one TransformationFlowStructure and identify the flow valuation, path, slice, crossing, transfer annotations, and refresh locality used by the claim.
• Apply E.18.NET’s membership, boundary, and cross-member relation requirements to select one network of independently identified TFS or nested-network members and identify its obtaining cross-member relation occurrences.
• Apply A.3.4 to identify an actual bounded U.Transformation, its changed referent, boundary, facts, and continuity or reidentification rule.
• Apply C.29 to evaluate mathematical-lens use and retain its returned adequacy, preserved/lost structure, payoff, obstruction, or stop result when that claim is current.
• Use C.2.1 for description-episteme identity and E.17 for publication faces and their publication boundary.
• Use A.6.0 for formal-substrate signatures, A.6.1 for mechanisms and applications, A.6.5 for slot discipline, and E.20 for mechanism-method placement.
• Apply A.15.1 to identify performed Work, A.15.2 to identify work plans, A.20 to obtain internal-step validity, A.21 to obtain gate results, A.10 to state evidence relations, B.3 to obtain assurance, and C.11 to obtain local choices.
• Apply C.30 to state architecture claims, C.30.AD to identify architecture descriptions, C.30.ASV to evaluate structural views, A.6.F to state function/bearer claims, A.6.M to state module-interface relations, and C.31 to state reusable-structure characteristics.