FPF Reference

    A.6.B:7 — Mini-register: Claim Register (informative, recommended)

    Preface node heading:a-6-b-7-mini-register-claim-register-informative-recommended:8134

    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

    A Claim Register is a drift‑control device that lists every routable statement verbatim with routing metadata. It is not a new meaning authority.

    IDQuadrantStatement (verbatim)Canonical location (section or publication unit)Stack layerA.7 primary layerviewRefviewpointRefReferencesNotes

    Guidance (informative):

    • The Statement cell should contain the normative text as authored (copy/paste), not a paraphrase.
    • Canonical location should point to the one place the statement “lives” (e.g., Signature.Laws, Mechanism.AdmissibilityConditions, TechCard.NormsCommitments, Evidence.Carriers), so other faces can cite it by ID.
    • Stack layer should be one of {Signature, Mechanism, Norms/Commitments, Evidence/Carriers} to make routing auditable.
    • A.7 primary side is the claim’s primary referent (EntityOfConcern, Description episteme, or publication carrier), even though the claim is always written as a Description episteme.
    • Use References for explicit cross‑quadrant links (e.g., which D-* enforces which A-*, which E-* adjudicates which commitments, which L-* defines a metric used by E-*) and for external standards/policies where applicable.

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