FPF Reference

    A.6.P:3 — Forces

    Preface node heading:a-6-p-3-forces:12279

    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
    Universality vs precisionThe repair must be reusable across domains, but must not hide the distinctions it is meant to recover.
    Prose convenience vs relation-specification clarityHumans want short verbs; engineering/assurance needs declared kinds, slots, and invariants.
    Kernel minimality vs safetyFew primitives are good; umbrella relations are cross‑Context safety hazards.
    Multi‑view reality vs coherenceViewpoints must be expressible without silent polarity flips or re‑typing.
    Evolution vs auditabilityRelations change; edits must not rewrite meaning invisibly.
    Stack disciplineSignature invariants, admissibility, deontics, and evidence/work must not be mixed (A.6 + A.6.B).

    Last Updated: 2026-06-08 — upstream FPF commit 093d30e8 (github.com/ailev/FPF)