FPF Reference

    Repair assignment rule

    Preface node heading:repair-assignment-rule:25669

    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

    Missing record or relation repair assignment. If the required governing record or relation is unavailable to the acting user, assign only prospective repair work, request work, decision work, work-plan work, or source-relation gap work to the holder, work-performing system, maintainer, verifier, or project role holder identified by the relevant RoleAssignmentRef or governing pattern relation for the missing relation. The acting user records the blocked work claim or reliance claim, the missing relation, and the safe narrowed use now.

    Reliance-appearance kind check. First name the actual kind of the reliance appearance: episteme, episteme publication, publication form, carrier, rendering, dashboard tile, credential view, generated/copied wording, or source-finding cue. If it exposes a typed ref, follow that ref to the direct owner and test the owner's obtaining or result criterion. If it exposes only a face, carrier, wording, or record entry, use it for orientation/source-finding until the direct object and evidence/currentness relation are recovered.

    Source-relation guard. Release urgency, delegated-claim urgency, compliance concern, color, salience, copied wording, or generated wording does not replace the source relation named by value. A dashboard tile may guide release only as a current view of the relevant GateDecision plus evidence relation, currentness relation, scope, and window.

    Last Updated: 2026-07-28 — upstream FPF commit 17edd955 (github.com/ailev/FPF)