| A1 | Design as occurrence | “The process achieved X” points to a diagram. | MethodDescription becomes Work. | Name the description and the actual Work separately. |
| A2 | Approval as evidence | “Approved SOP, therefore target satisfied.” | A status about a description replaces outcome evidence. | Use observations of Work and the relevant evaluation relation. |
| A3 | Work as record | U.Work is described as the record of an event. | Occurrence, episteme, and carrier collapse. | Keep Work actual; model report or record separately. |
| A4 | Work = control output | A setpoint log is treated as the full execution. | Conditions, delays, and other Work facts disappear. | Name Work and its outputs separately. |
| A5 | Universal Actuation | Every case receives an Actuation box or kind. | Domain-specific outputs are forced into a false umbrella. | Use the direct control or transformation pattern and actual output kind. |
| A6 | Generic Bridge transfer | A Bridge is said to transfer facts between Method, description, Work, and output. | Different relation families collapse. | State MethodDescription membership, enactment, performed-Work, description-use, output, observation, or evidence claims under their own patterns. |
| A7 | Source-word collapse | Task, activity, and process are interchanged by label. | Source-local claims vanish. | Recover exact meanings; use F.9 only for an actual semantic relation. |
| A8 | Recipe as system role | A description is said to assign responsibility. | MethodDescription and system-role assignment collapse. | Use A.2 for the local system-role kind and A.2.1 for the assignment; F.4 only for a separately needed kind description and F.6 only for precise performed-Work attribution. A.3.2 governs the MethodDescription. |
| A9 | System-in-Role shorthand | The acting participant is a mask-like pseudo-object. | System, kind, assignment, and Work attribution disappear. | Name those four claims separately where material. |
| A10 | Retroactive description | A new description version is assumed to change past Work. | Historical occurrence claims become unstable. | Keep past Work and its actual description-use evidence unchanged. |
| A11 | Signal-only compliance | Commands are treated as proof of outcome. | Intended influence replaces observed result. | Use observations under C.16 and evidence relations under A.10 and B.3. |
| A12 | MethodDescription as kind | A description vocabulary is treated as a taxonomy of Methods. | Description and kindhood collapse. | Establish any kind claim through C.3 and A.3 and keep the description separate. |