| one actual bounded change under conditions | A.3.4 | A source label identifies no transformation until the exact changed referent, temporal or formal boundary, boundary conditions, actual subject facts, and continuity or reidentification basis are recoverable. |
| selected structure over transformation loci and adjacent governed values | E.18 | TransformationFlowStructure positions, relates, or locates those loci and values. Selection or common structure membership establishes neither an actual transformation occurrence nor transformation composition, parthood, or partlessness. |
| mathematical expression over a selected structure or formal object | E.18.2, C.29, A.6.0, or the direct formal pattern | Recover project-world work separately under A.15.1 when the current use also claims it. |
| semantic way of doing | A.3.1 | Recover the semantic way of doing under A.3.1; identify dated work, mechanism, evidence, or transformation claims separately when current. |
| episteme describing a way of doing | A.3.2 | For example, code, a protocol, a solver model, a proof script, a process model, or a diagram may describe a method. |
| law-governed operation algebra, laws, admissibility predicates, transport, audit, or mechanism-governing-definition assignment | A.6.1 and E.20 | Recover the mechanism’s defining content under A.6.1 and E.20. |
| planned or dated work | A.15.2 or A.15.1 | Identify the plan or dated occurrence under its governing pattern; recover any Method, MethodDescription, transformation-flow structure, or evidence claim separately. |
| pattern-use recommendation, work-entry readiness, language-state move, architecture candidate use, or call-planning next action | E.10.MOVE first, then E.11.PUR, A.15.5, A.16, C.30, C.24, or the subject pattern | Move-like wording is not transformation wording unless a bounded U.Transformation or selected TransformationFlowStructure is actually current. |
| function-like wording inside a change situation | A.3.4.P only to distinguish the actual transformation, selected TransformationFlowStructure, a System claimed to act under an exact actor-side relation, a differently typed influence source under its exact relation, boundary binding, or FunctioningRef?; use A.6.F for detailed function-kind discrimination | For an actual-transformation claim, recover its occurrence basis; for an actor claim, use the performed-Work or non-Work basis in 4.4. |
| state-space and transition-law episteme | A.3.3 | Dynamics can model possible or claimed change; recover any claimed actual occurrence independently under A.3.4. |
| time window, cadence, duration, latency, freshness, currentness, trajectory, inertia, or effort | C.27.TA; use C.27 for temporal-claim adequacy | C.27.TA supplies positive temporal subject matter; C.27 governs temporal-claim adequacy. Recover transformation identity under A.3.4 when that separate claim is current. |
| evidence, provenance, source, publication, dashboard, view, gate, decision, assurance, result, or release claim | the direct governing evidence, source, publication, gate, decision, assurance, result, or release pattern | A visible record or path does not establish evidence sufficiency, assurance, gate passage, deontic permission, work authorization, release authorization, performed work, or acceptance by itself. |