FPF Reference

    A.6.B:12 — Consequences

    Preface node heading:a-6-b-12-consequences:8449

    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

    BenefitsTrade‑offs / mitigations
    Stable modular boundaries. Laws don’t accidentally become gates; governance doesn’t masquerade as truth.Requires writers to split sentences; mitigated by the triangle decomposition pattern.
    Auditability by construction. Commitments can be linked to adjudicable evidence carriers.Requires evidence to be designed; mitigated by keeping evidence conceptual and carrier‑anchored.
    Reduced semantic drift across faces. IDs + explicit references prevent accidental divergence.More cross‑references; mitigated by a Claim Register (optional but recommended).

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