F.11:13 - Relations

Builds on:

• Use A.3 and A.3.1 for U.Method, A.3.2 for U.MethodDescription, and A.15 and A.15.1 for dated U.Work.
• Use B.1.5 for Method composition and Work enactment, C.2.1 for the identity of every claim-bearing episteme and report, and E.10.D1 when vague context wording hides the actual source, scheme, scope, use, situation, or evidence basis.
• Use the direct transformation, observation, or control pattern when an output claim is made; F.11 creates no universal actuation kind.

Constrains:

• F.4 and F.6: a local system-role kind, its description, an assignment, and performed-Work attribution remain distinct from Method, MethodDescription, Work, and output.
• F.5: use distinct Plain and Tech designations when one source expression hides different subjects.
• F.7 and F.9: compare exact local claims or F.17 cells and cite F.9 only when a semantic relation actually obtains. A shared heading creates no identity, relation, or use licence.

Used by. Part C examples and the A.3, A.15, and B.1.5 method-and-work stack. Every MethodDescription membership judgement, enactment, performed-Work attribution, description use, observation, output, evidence use, or publication claim still uses the pattern that defines or tests it.