A.12:7 - Common Anti-Patterns and How to Avoid Them

Anti-pattern	Symptom	Repair
Self-action literalism	“The system fixed itself” is accepted as one undivided claim.	Identify the acting and changed participants. Use `ReflexiveSplit@Context` only when §4.2’s two-entity-part and one-holon conditions hold.
Transformer kind inflation	The acting side is modeled as `U.Transformer`, as a special system kind, or as a provisional phrase placed in a `U.System` slot.	Before recognition retain the exact `U.Entity` and A.1 disposition or blocker and leave `actingSystemRef` unfilled. After recognition use the exact `U.System`. Add a local `TransformerSystemRole` classification only after C.3 recovers that kind from its system-candidate domain, work-facing membership distinction, member/non-member boundary, and continuity rule. Add acting-side participation or an assignment separately only when that exact relation is current.
Boundary as object by word	Boundary or interaction words become durable root objects.	Identify the relation actually claimed: holon delimitation, boundary crossing, transformation, signaling, evidence, source use or publication use. Apply its defining or testing rule; §4.1 gives the condition for recovering an identity-bearing ClaimGraph.
Work success by action	Because a system acted, the work is treated as successful.	Use A.15.1 and evidence-use patterns for performed work and success.
Evidence by producer	The acting system’s own output is accepted as enough evidence.	Use §4.5 to identify which claim the output supports under A.10.
Manufacturing as containment	A tool or teacher changing another holon is treated as its containing whole.	Keep transformation and part-whole claims separate.