FPF Reference

    A.6.C:3 — Forces

    Preface node heading:a-6-c-3-forces:9451

    What this page is

    This is generated FPF reference text from the specification preface or supporting sections. It helps interpret FPF; it is not FPF Reference product documentation.

    Methodology

    Use it to understand how the specification wants to be read, then return to a route, pattern, or work packet for active work. Cite generated IDs only when the wording changes the task decision.

    Content

    ForceTension
    Conversational conveniencePeople will keep saying “contract”; banning the term is unrealistic.
    Ontological correctness“Contract” is a metaphor unless we explicitly locate who promises or commits and what can be evidenced.
    Boundary diversitySoftware APIs, hardware connectors, protocols, and SLAs share the “contract” word but differ in what is adjudicated and how.
    Multi-view publicationFaces 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.
    MinimalityThe unpacking should be lightweight enough to apply during routine authoring and review.

    Last Updated: 2026-06-17 — upstream FPF commit 646b0b9b (github.com/ailev/FPF)