Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:40:20 UTC

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

Anti-patternSymptomRepair
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 inflationThe acting side is modeled as U.Transformer, as a special system kind, or as a provisional phrase placed in a U.System slot.When System recognition is needed, retain the U.Entity and A.1 disposition or blocker until actingSystemRef can identify that same entity as a System. Add a local TransformerSystemRole classification only after A.2/C.3 establishes the system-role kind from its system-candidate domain, work-facing membership distinction, member/non-member boundary and continuity rule. Add participation or assignment only when that relation is claimed.
Boundary as object by wordBoundary 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 actionBecause a system acted, the work is treated as successful.Use A.15.1 and evidence-use patterns for performed work and success.
Evidence by producerThe 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 containmentA tool or teacher changing another holon is treated as its containing whole.Keep transformation and part-whole claims separate.