C.3:10 - Common Anti-Patterns and How to Avoid Them

• Treating a programming type, schema class, source ontology class, regulatory category, or ordinary noun as a durable public FPF U-kind.
• Treating a KindSignature as the kind, or attaching its formality and claim scope to the kind.
• Using a world-side belongs-to predicate or minting a classification relation merely to state one judgment.
• Treating evidence availability, a schema row, or a publication form as sufficient for classification when the criterion requires a different governed condition.
• Returning false when the criterion cannot be evaluated.
• Treating KindExtension or mathematical set notation as ontology.
• Repairing a subkind counterexample by silently changing an extension table.
• Treating a plan or work record as a dated work occurrence.