A.15.2:4.3 - Clear distinctions for schedule, process, and workflow wording
| If you say… | In FPF it is… | Why |
|---|---|---|
| “The schedule for tomorrow’s surgeries” | U.WorkPlan | Episteme declaring intended cases, windows, intended performer Systems and local system-role-kind conditions, resources, dependencies, and targets without asserting occurrence. |
| “The workflow for appendectomy” | U.MethodDescription and U.Method | Recipe and semantic way, not a calendar. |
| “The process already ran at 10:00” | A Work occurrence admitted under U.Work only when A.15.1 grounds that dated individual | Identify its performer System, obtaining assignment, enacted Method, temporal extent, and containing System. Add participation, resource use, change, result, acceptance, or outcome only when that separate claim is actually being made. |
| “The thermodynamic trajectory” | a trajectory representation or model; U.Dynamics only when the episteme meets A.3.3’s state-space and transition-law criterion; add exact changed-subject and U.Transformation claims only when their direct predicates obtain | A trajectory expression is neither plan nor performed work by form. |
| “The plan assigns Dr. Lee” | U.WorkPlan carrying a claim about the System intended to perform the Work and its local system-role-kind condition; cite an assignment occurrence and its declared species only when that assignment already exists | The plan does not create or validate an assignment for the performed Work interval. |
| “The budget for Shift-B” | U.WorkPlan planned resource-budget claim | The plan states the budget. A.15.1 identifies later Work, the applicable resource-use predicate states what it consumed, and B.1.6 aggregates those facts only when a ledger or allocation result is needed. |
Schedule-word guard. Schedule-like words do not determine the kind by themselves. Use
U.WorkPlanonly when the text actually states intended Work, a horizon or window, the System intended to perform the Work or its local system-role-kind conditions, and enough constraints, resources, dependencies, targets, or baseline to coordinate it. Otherwise use the pattern for the Method, instructions, dated Work, evidence, gate, publication use, or representation actually claimed.