Link to current text
F.5:3 - Forces
| Force | Tension |
|---|
| Local fit versus cross-local neutrality | A local system-role-kind name must fit the named practice or source use; a public U-kind name must not privilege one witness. |
| Brevity versus object recovery | A usable name must still let a reader distinguish kind, description, classification, assignment, status, Method, Work, relation, and episteme use. |
| Teaching versus widening | A Plain designation should help readers without broadening the Tech designation. |
| Stability versus changed meaning | Names should survive harmless edition or publication changes, but real sense changes need a split, rename, or lineage record. |
| Morphology versus ontology | Word form guides expectations but establishes no kind. SystemRole does not create a universal kind or assignment. |
| Open-world use versus name burden | A lightweight local label may be enough; durable public reuse can require F.18 or F.17, and an actual cross-local relation can require C.3.3 or F.9. |