A.7:4 - Forces
| Force | Tension |
|---|---|
| Didactic brevity vs conceptual precision | Teams want short words (“process”, “function”) ↔ the framework must keep the four distinction families apart. |
| Universality vs domain idioms | We admit engineering idioms (procedure, SOP, algorithm, workflow) ↔ internally we must map them unambiguously. |
| Parsimony vs completeness | Minimal concept set ↔ enough distinctions to avoid the classic traps: system-role kind versus function; description, Method, Capability, and Work; and episteme versus carrier. |