F.11:4 - Core idea (didactic)
Use four questions, then state only the relations that obtain:
- Method — the way. A.3 and A.3.1 govern the way of doing, such as a welding technique.
- MethodDescription — the description episteme. An episteme is a
U.MethodDescriptiononly when A.3.2 finds one admitted Method as its exactEntityOfConcernand at least one substantive claim about that Method as a way of doing. - Work — the occurrence. A dated occurrence is
U.Workonly after admission under A.15 and A.15.1. Work is the occurrence itself, not a record of the occurrence; a record or report is a separate episteme or carrier. - Control or transformation output — if present. Identify the output under its direct pattern and relate it to the Work only when that relation obtains.
F.11 allows the plain sentence “this MethodDescription describes the Method” as shorthand for that A.3.2 constitution and membership judgement. It does not add a binary description relation.
Several epistemes may each have the same Method as their exact EntityOfConcern; one episteme may concern one admitted composite Method; and one document or publication may present several separately identified epistemes. One MethodDescription episteme cannot have several Methods as its EntityOfConcern.
Every admitted Work enacts at least one Method. To claim that it enacted the Method in question, identify that Method and the performance history supporting the claim. Recover the actual performer through A.13 and admit the Work independently under A.15.1; add F.6 only when precise attribution to the same obtaining assignment is needed.
A claim that a System or Work used, followed, deviated from, conformed to, or relied on a particular MethodDescription edition is separate. Cite the pattern that defines or tests that claim; use A.10 or B.3 for evidence reliance, and return A.6.RCD missing-governor when no current pattern supplies the needed relation after its participants and sentence are explicit.