Source changed 2026-10-03 17:24:51 UTC · snapshot created 2026-10-03 17:30:20 UTC · last check 2026-10-03 18:00:10 UTC
A.15.4:9 - Relations
Cluster relation:A.15.4 is a cluster member under A.15 for work-relevant appearance-based reliance repair; it does not replace the A.15 system-role-kind, assignment, Method, plan, and Work kernel.
Uses:E.17, E.17:5.1b, E.17:5.1c, and E.17:5.1d for source-relation and use-boundary vocabulary; E.17.EFP for explanation faithfulness and source-finding; A.16.0 for source transfer; A.6, A.6.B, and A.6.C for boundary wording; A.10 for evidence and currentness; B.3 for assurance; A.15.5 for work-entry readiness; A.20 for constraint validity; A.21 for gate decisions; A.2.1 for exact system-role assignments; A.2.5 for assignment-state relations; A.13 for actual performers’ core agency bases; A.15.1 for independently admitted dated Work; F.6 only when the receiving result must also identify the assignment under which that Work was performed; and A.2.8, A.2.8.PER, and A.2.9 only through the single permission and authority branch in §3.
E.10 and E.10.MOVE relation-selection rule: When the direct question is already known, apply its subject pattern directly or use the §3 lookup. Use E.10.MOVE when work-entry or readiness wording still hides the governed claim. Use E.10.ARCH when the distinction among a world-side fact, reusable declaration, claim or report, and representation remains unresolved. Permission or authority uses the single §3 branch. A.15.4 starts only while a required relation or result is still hidden by the reliance appearance.
A.15 boundary relation: use A.15 directly when the remaining question under repair is system-role-kind, assignment, Method, plan, and Work alignment rather than a reliance appearance being used as a reason for Work or reliance.