Source changed 2026-10-03 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 13:15:03 UTC
A.15.2:7e - Relations
Builds on: C.2.1 for episteme identity and local assertion identity; A.15 for System-Role-Method-Work alignment; A.15.1 for independently identified performed Work occurrences admitted under U.Work; A.2.1 for direct U.SystemRoleAssignment species; A.2.2 for qualified holder-ability claims, thresholds and fit conditions; A.3.1 for U.Method; and A.3.2 for U.MethodDescription.
Coordinates with: A.15.3 for planned filling against exact governed declarations; A.6.1 for operation argument and result declarations; A.6.5 for RelationSignature participant declarations; A.6.RCD for the existing-direct/local-compound/reusable-predicate/relation-kind economy; E.24/E.24.UK for any later kind admission; A.6.REL only after an admitted direct or derived relation needs occurrence discipline; A.15.4 for work-relevant appearance-based reliance repair; A.15.5 for work-entry readiness; C.27.TA for direct temporal-aspect claims; B.1.4 for temporal aggregation; B.1.6 for performed-resource aggregation; A.10 for accounts of independently established evidence-provenance relations; B.3 for assurance; A.20 for internal constraint results and A.21 for gate decisions; C.32.P2S for architecturing-flow references to intended work; E.17 for publication-use questions; and F.9 only for exact cross-context SchemeSenseCell correspondence, with any proposed use and reliance routed through checklist item 7.
Used by: P2W carry-through when principle-to-work reasoning reaches WorkPlanning, and P2S carry-through when architecture-selected structures require intended-work epistemes. Both uses keep present plan subject, possible future performance, readiness, performed Work, actual use, evidence, gate, comparison, result, and downstream effect separately governed.