F.11:4 - Core idea (didactic)
Use four questions, then state only the relations that actually obtain:
- Method — the way. An algorithm, test method, clinical pathway, or welding technique is a way of doing under A.3 and A.3.1.
- MethodDescription — the description episteme. An SOP, program text, BPMN or SPEM model, or other 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 performance, run, batch, or service episode is
U.Workunder 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. A setpoint, command, duty-cycle value, signal, or changed output is identified under its direct pattern and related 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.
Work may enact a Method when the exact enactment relation and evidence are stated. A System may perform Work under an obtaining system-role assignment when A.15.1 and F.6 support that attribution. 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.