A.6:12 - Relations
- Uses A.6.B as the classification authority:
A.6.B:8.4.1selects the job of permission wording. A.6 maps the resulting atomic claim to the stack; it does not put everyA.2.8.PERobject in D. The filled case inA.6.B:8.4.5.4demonstrates this classification. - Coordinates actual effects without merging them: Use A.15.1 only to identify a grounded dated Work occurrence; use A.3.4 for an independently identified actual transformation, including spontaneous or formal change with no Work; state each interaction, causal, production, speech-act, evaluation, evidence, or result claim through its applicable predicate and pattern. A description or carrier alone creates none of them.
- Constrains signature writing: Reinforces A.6.0 separation of Laws vs operational gates (AdmissibilityConditions live in mechanisms).
- Constrains mechanism writing: Uses A.6.1 for OperationAlgebra, LawSet, AdmissibilityConditions and Applicability; local transport and evidence-interface sections retain their own claim classification.
- Requires EntityOfConcern and Description-episteme / publication-carrier discipline: Uses A.7 to prevent category mistakes; ties evidence to evidence carriers and publication faces to descriptions.
- Coordinates
U.View,U.Viewpoint, and publication use: E.17.0 governs viewpoint and view membership; MVPK selects exact epistemes, viewpoints, face uses, and publication forms; A.6.3 governs only optional source-to-receiving construction. - Unpacks “contract” talk: When boundary ambiguity changes interpretation or use, A.6.C applies A.2.3, A.2.8, A.2.8.PER, and A.2.9 to keep promise content, speech act, commitment or grant explicit; use A.15.1 only to identify dated Work, and its §4.6 dispatch requires the exact subject predicate for each application-result, production, change, delivery/transfer, evidence, or acceptance claim.
- Uses relation-specific declaration disciplines: use A.6.5 when an already recovered direct relation needs reusable participant typing. Use A.6.6 when basedness wording hides the dependent, base or direct predicate; stop at the ordinary assertion when it answers the receiving question.
- Coordinates with
C.28 CausalUse-CAL: When boundary prose uses causal-use evidence or a causal-use verdict to justify deployment, release, duty, commitment, or admissibility, A.6 splits the boundary sentence whileC.28carries the causal-use question,CausalityLadderRung, estimand, support basis, support verdict, and supported and unsupported causal uses. - Coordinates work and consequences:
A.15.1supplies only a datedU.Workoccurrence. Its §4.6 table routes an application/result binding, production, change, evaluation result, evidence use, delivery/transfer, and acceptance to separate subject patterns.A.15,A.10,B.3,A.21, andA.20govern the enactment-alignment, evidence, assurance, gate, or constraint claim when current.