#A.6.C:3 — Forces
Preface node
heading:a-6-c-3-forces:7669
#Content
| Force | Tension |
|---|---|
| Conversational convenience | People will keep saying “contract”; banning the term is unrealistic. |
| Ontological correctness | “Contract” is a metaphor unless we explicitly locate who promises/commits and what can be evidenced. |
| Boundary diversity | Software APIs, hardware connectors, protocols, and SLAs share the “contract” word but differ in what is adjudicated and how. |
| Multi-view publication | Faces are necessary for audience fit, but rephrasing easily creates new commitments. |
| Adjudicability | “Guarantee” claims must either be (i) semantic truths, (ii) deontic commitments, or (iii) evidenced properties—otherwise they are empty rhetoric. |
| Minimality | The unpacking should be lightweight enough to apply during routine authoring and review. |