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:05:04 UTC

A.1:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternSymptomRepair
System as universal rootA theory, document, model, source, or dashboard receives physical system properties.Re-type as U.Episteme, publication, source-use object, or another direct object before using system claims.
Document edited itselfA model, theory, or document is said to perform a revision.Name the revising U.System. If the account claims revision Work, first recover that System’s A.13 core—local agential system-role kind and criterion, classification, and obtaining assignment with the required scope, situation, and window—then use A.15.1 to admit the Work. A short account may omit restating these facts only when they remain recoverable; add F.6 only for precise assignment-bound attribution. Changed claim content identifies another U.Episteme; test any edition relation separately, and distinguish publication or carrier changes under their own patterns.
Collection as actorA list, batch, pool, fleet, or community is said to decide or perform Work.Identify the Systems claimed to decide or perform Work. If the collection is claimed to act as one System, establish its constructive recognition and acting eligibility; retain a mere membership or collection-characteristic claim at that scope.
Interaction as one umbrellaSignal, source use, publication use, transformation, measurement, and control are all called interaction.Recover the direct relation; use F.9 for a needed semantic correspondence or difference between two local senses from different semantic contexts, and A.3.4 when bounded change is current.
Omnibus participation relationReferences to system-role-kind classification or assignment, capability, method, work, transformation, evidence, and time are packed into one additional relation-shaped record.Keep the direct relation occurrences separate; select their organization as U.Structure only when that organization changes the receiving use.
Boundary by drawingA box, folder, section, dashboard view, or diagram is treated as the holon boundary.Recover the delimitation relation, criterion, or selected structure from its direct pattern; keep the drawing as a description or view.
Architecture without holonA selected structure is discussed without the holon whose structure is selected.Use A.1 to name the holon, then A.22 and C.30 for selected structure and architecture.