E.18.1:12 - Relations

• Apply A.22.CGUS when P2W identifies one A.22 structure whose local loci, selected relations, applied constraints, and at least two potential continuations are recoverable. Judge enabled, disabled, unknown, and error outcomes for the present case separately from structure identity and membership.

• E.18.3 qualifies that exact A.22-selected CGUS through positions, bindings, and already-obtaining occurrences from one independently identified E.18 substrate. E.18 defines the one-TFS and parent-relative internal-SubflowRef interfaces; E.18.NET defines independently identified network members and exact obtaining cross-member relations. P2W cites those exact values, adds no subset, reciprocal record, or hybrid structure schema, and neither reidentifies nor routes them.

• G.2 supplies SoTA harvesting, source selection, competing-tradition synthesis, and the refreshable synthesis pack before DPF hardening can rely on a source-derived seed. Add A.10 for claim-bound source or provenance, G.6 for addressable path citation or shared provenance representation, B.3 for assurance of a named reliance use, and G.11 for currentness and refresh only when that stronger use is current.

• E.4.DPF guides DPF authoring. When the framework-architecture question is live, E.9 records the selected answer and E.4.PFAD profiles its framework-specific content; E.4.PFR handles an optional framework-relation record only when a named maintenance use needs one.

• E.23 defines and tests repeated quality improvement only after the object version and evaluation are recoverable; P2W may carry a seed to that point but does not become the improvement method.

• G.11 defines and tests currentness, admitted-source decay, source-use relation change, edition change, and refresh when a changed source publication, source-use relation, or telemetry reopens the smallest affected P2W application.

• E.18 defines and tests the selected TransformationFlowStructure, its internal transfer, flow valuation, positions, crossings and local state bindings. Apply A.20 for a current internal constraint-validity claim and A.21 for a current gate profile application, check mapping or gate decision; cite those separate results only when the P2W continuation uses them.

• C.22.2 defines and tests the accepted problem-side record and problem-side claims related to the carried distinction.

• A.6.P supplies recovery and readable statement of each direct relation. A.6.REL defines and tests direct obtaining, occurrence individuation, and receiver-conditioned use of any reusable RelationSignature; P2W cites the occurrence, assertion or description returned there and copies none of that doctrine into ClaimContent. Use A.6.RCD, E.24, and E.24.UK for any later P2W relation-kind candidate and admission, while A.6.0 declares a RelationSignature only after that settlement. F.8/F.18/F.17 open only when an external naming or publication use is current; the header’s Tech/Plain pattern label and local note-field phrases create no NameCard, term row, U-kind, relation or MethodDescription.

Canonical question-to-pattern map. Read each row independently. The row order is not a declaration or work sequence, and each pattern keeps the definition, test, and basis of the result it returns.