FPF Reference

    A.6.B:3 — Forces

    Preface node heading:a-6-b-3-forces:7904

    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
    Precision vs readabilityPredicate‑style constraints reduce ambiguity; narrative helps adoption.
    Evolvability vs enforceabilityStable laws should not embed volatile runtime gates; governance still needs enforcement hooks.
    Auditability vs simplicityEvidence makes claims adjudicable; evidence also introduces operational design obligations.
    Local meaning vs reuseBoundaries must be local; reuse must be explicit via IDs and references, not duplicated prose.

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