FPF Reference

    A.6.B:5.1 — Quadrant L: Laws & Definitions

    Preface node heading:a-6-b-5-1-quadrant-l-laws-definitions:12470

    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

    Intent. State truth‑conditional content: definitions, invariants, typing and well-formedness constraints, equational laws.

    Adjudication. In‑description: can be checked by inspection, proof, type validation, or model reasoning.

    Canonical form. Definition: / Invariant: / predicate‑style constraints using “is / iff / for all”.

    Prohibitions.

    • An L-* statement MUST NOT contain RFC deontic keywords (MUST, SHALL, SHOULD, or MAY) as operators inside the law or definition itself.
    • An L-* statement MUST NOT encode runtime gate predicates (those are A-*).
    • An L-* statement MUST NOT assert evidence availability or measurement outcomes (those are E-*).

    A.7 EntityOfConcern binding. Identify what the L-* definition, invariant, or typing rule concerns, separately from the episteme carrying the claim. Its EntityOfConcern need not itself be a description and may be Work.

    Typical dependence. A-* and E-* claims may reference L-* IDs or canonical locations for vocabulary, metric definitions, and invariants needed for interpretation.

    Last Updated: 2026-10-12 — upstream FPF commit f2bc67dd (github.com/ailev/FPF)