Source changed 2026-10-03 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 11:55:15 UTC
A.6.C:3 — Forces
Force
Tension
Conversational convenience
People will keep saying “contract”; banning the term is unrealistic.
Ontological correctness
Familiar contract wording can hide whether a guarantee is semantic, a prescription, an undertaking, or an observed result.
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 support audience fit when projection is needed; rephrasing can change the claim.
Adjudicability
When “guarantee” or authority wording leaves a consequential ambiguity, recover the semantic truth, exact generic prescription, individual commitment or current grant, entry predicate, or observed/evaluated claim needed by the receiving use.
Minimality
The unpacking should be lightweight enough to apply during routine authoring and review.