C.3.2:14 - Common Anti-Patterns and Remedies

Anti-pattern	Remedy
Treating a kind and its `KindSignature` as one object	Identify the kind and declaration episteme separately.
Returning `unknown` for a candidate outside ValueKind or applicability	Return `not-applicable` and form no judgment.
Returning `false` for missing support	Preserve `unknown`; let the receiving guard decide whether to decline use.
Treating any evidence item or record as membership	Ask whether the criterion directly concerns that governed episteme, relation, status, or publication occurrence. If not, keep it only as support.
Reusing a world-side belongs-to predicate or minting a relation by notation	Keep the result as a classification judgment unless a direct relation pattern is justified.
Treating an extension or braces as ontology	Keep the candidate domain and extension as representations; use C.29 when claim-bearing.
Attaching scope or formality to the kind	Keep them on their declaration or assertion epistemes.
Editing an extension to hide a subkind counterexample	Repair the relation proposal, declaration alignment, or distinct-kind bridge.
Classifying a record as actual Work	Recover an independently grounded `W : U.Work`; keep its record separate.