A.7:9 - Anti‑patterns (with fixes)

System-role-kind-as-behaviour — calling the system-role kind a function or saying it acts. Fix: Name the acting System and direct behaviour or Work first. Add the local kind, assignment, Method, or Capability only when that stronger claim is current; none of them acts.
Episteme‑as‑system — “the model routed traffic” when “model” denotes an episteme rather than the deployed acting System. Fix: Name the System that used the episteme; keep recoverable deployed-System shorthand when that is the intended referent. Add Work, carrier, assignment, evidence, or source details only when the receiving claim uses them.
Triad everywhere — omitting Work entirely. Fix: Add a Work occurrence only when performed action is claimed; a design-time distinction diagram need not pretend that Work occurred.
Composition blur — using one “process operator” for unlike claims. Fix: Recover the subject and intended result, then use :5.7 to select the system, Method, temporal or Work-resource rule and its prerequisites.
Formal set, world-side collection, and collective collapse — mathematical inclusion or collection belonging is used to make a grouping act or to infer constructive parthood. Fix: Keep formal inclusion with its mathematical or representation rule; state world-side belonging under the collection’s own rule; require all six A.1 matters for a collective System; state any constructive part relation separately.
Unspecified evidence use — citing content as evidence without identifying the episteme, target claim, or conditions needed for that use. Fix: Recover the evidence-use relation. Add A.10 carrier/source-currentness refs when that evidence or source use depends on them; a carrier reference alone does not establish support.
Holon/system drift — “holon maintains temperature”. Fix: Say system; reserve “holon” for neutral mereology.
Function and system-role-kind swap in tables — columns labelled “Function” whose entries are local system-role kinds. Fix: Rename the column to System-role kind. If behaviour is also being compared, give it a separate column and state the actual behaviour claim under its direct rule, including A.6.F functional behaviour or A.3.4 transformation where applicable.
Process‑word leakage — domain “process” used as FPF operator. Fix: Use the exact Γ operator for the composition claim. Keep a clear domain use of “process”; if it is ambiguous, state the actual Method, Work, transformation, mechanism, or other object intended.
Carrier and episteme swap — “we versioned the model” meaning a file was renamed. Fix: State whether the episteme content changed; if only a carrier was renamed, say so.
Publication-as-mechanism — modelling “publication” as if it were a Method or Mechanism. Fix: Identify the Description episteme directly through C.2.1 and keep specification use and publication separate. Name an actual authoring, measurement, observation, model, source-use, representation, or refinement relation only when current; operational build, render, or upload activity is separate Work by a System on carriers.
Form-first MethodDescription — “this is an SOP/algorithm/script, therefore it is a MethodDescription.” Fix: Identify the C.2.1 episteme, resolve one admitted Method as its exact EntityOfConcern, and find at least one substantive way-of-doing claim; otherwise retain only the source cue.
Mandatory description hop — a Method identifier or receiving methodRef is forced through a document or description edition. Fix: Resolve designation and the receiving reference directly to the exact Method under their effective ReferenceScheme discipline; cite methodDescriptionRef separately only when its claims are actually used.
Lifecycle time as membership — authoring, revision, citation, approval, publication, or use is treated as creating MethodDescription membership. Fix: Keep those Work and neighboring relations under their subject patterns; reapply the same A.3.2 membership test to the independently identified episteme.