FPF Reference

    A.6.P:0 — TERM and LEX token guards (local-first)

    Preface node heading:a-6-p-0-term-and-lex-token-guards-local-first:12226

    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

    This pattern reserves the following tokens in Tech and normative prose:

    • RPR — Relational Precision Restoration (the governing repair discipline; not a new U.Type).
    • RelationKind — a Context-local vocabulary token (signature-level) that fixes polarity and SlotSpecs for participant and qualifier positions. It is a registry entry token, not a relation instance.
    • QualifiedRelationRecord — the slot-explicit relation instance record kind (Context-local episteme/record kind); instances carry a relationKind token reference plus explicit participant/qualifier slots.

    Mint-or-reuse note (pattern-level). This pattern mints the label RPR, the role name RelationKind, and the generic shape name QualifiedRelationRecord as local-first terms for relation precision restoration. It reuses existing FPF terms (U.Signature, SlotKind, ValueKind, RefKind, Bridges, CL, U.Scope, Γ_time, U.View, U.Viewpoint, evidence pins, and carriers) without changing their meanings.

    Definitions (pattern-level; non-deontic).

    • RelationKind token — a declared vocabulary element (signature-level) whose public definition fixes polarity and SlotSpecs for participant and qualifier positions, and that is referenced by L, A, D, and E-classified claims that govern admissibility, duties, commitments, evidence, and work.
    • QualifiedRelationRecord — a Context-local episteme/record kind whose relationKind field points (by id/ref) to a RelationKind token and whose instance records make all relation-specification-required participant/qualifier slots explicit.

    Rename-guards (common collisions):

    • agreement-like boundary wording — Plain shorthand for a published boundary-interface description; a conforming text MUST NOT treat such wording as itself establishing a promise or obligation. Promises, duties, and gates are classified under A.6.B.
    • bind and binding — reserved for name binding (Identifier to SlotKind or slot instance) and MUST NOT be used as a synonym for relation instance edits.
    • same, synced, linked, connected, anchored, grounded, supported, and supporting — treated as umbrella tokens; allowed as Plain gloss only when immediately mapped to an explicit RelationKind token (Tech) or to an claim kind governed by an FPF pattern named by value or admissible-use boundary via rewrite rules.

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