| Recognition versus ontology | A description must be easy to read but cannot replace the kind, classification judgment, assignment, capability, Method, or Work occurrence. |
| Kind continuity versus local reuse | The candidate domain, operative membership distinction, member/non-member boundary, and continuity rule decide whether one kind continues. A practice or source change only tells the reader where to compare definitions; a later use may still need a C.3.3 relation between distinct kinds or an F.9 relation between distinct F.17 local-sense cells. |
| Compactness versus completeness | A useful description is small, but a stronger receiving claim may need state, capability, Method, assignment, evidence, or status checks. |
| Open-world use versus form burden | Some uses need only a recognition paragraph; stronger uses need explicit neighboring references without pretending every possible relation is current. |
| Work-facing classification versus episteme use | An admitted system may satisfy a system-role kind and participate in an assignment. An episteme is instead used through evidence, source, publication, requirement, explanation, assurance, or status relations. |