A.2.6:21 - Relations - Cross-Pattern Coordination

A.2.6:21.1 - With F–G–R (C.2.2)

• G is Claim scope. Use set algebra (∩ / SpanUnion).
• F remains the expression rigor (C.2.3); R captures evidence currentness and bounded reliance. Observed loss may bear on the translation-use claim; its permitted-loss tolerance remains in that claim rather than in G or the Bridge profile.
• Composition. F follows C.2.3’s weakest-essential-support bound. R follows the justified support-composition model or non-aggregate synthesis under C.2.2. G follows §7.2–§7.3 (set rules).

A.2.6:21.2 - With Formality (C.2.3)

• No conflation. Raising F does not change G unless scope predicates change.
• Guarding rigor. ESG may use Formality >= F_k alongside scope coverage.

A.2.6:21.3 - With Work & Run (A.15)

• Work scope delimits the exact job slices on which a capability’s deliverability claim is evaluated.
• Method–Work gates use Work scope coverage plus measures and qualification windows.

A.2.6:21.4 - With exact F.9 Bridge occurrences

• Translation boundary. Use an exact F.9 Bridge only for exact local-sense translation. State the translation’s direction, rule, tolerated loss, and polarity in a separate C.2.1 claim. Before the receiving use proceeds, require A.10 pass for ordinary reliance or, when an actual named assurance claim is current, a B.3 AssuranceResult for the same use with disposition=supported-for-use.
• Best practice. If the bounded-use claim’s rule and tolerance permit translation only for part of the source scope, identify that part and return its target image; do not turn observed mapping loss into a Bridge identity field or a generic R penalty.

A.2.6:21.5 - With Capability governance (A.2.2)

• Capabilities MUST declare Work scope, measures, qualification windows; gates MUST verify all three.
• Capability refits that preserve the set (unit changes) are Refit, not Δ(WorkScope).