FPF Reference

    C.3.A:A.3 Regulatory guards

    Preface node heading:c-3-a-a-3-regulatory-guards:46672

    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

    Guard_RegAdopt(P, candidate, authorityKind, authoritySignatureEdition, localKind, localSignatureEdition, S_local).

    1. Check P's governed scope and explicit time against S_local.
    2. Recover the exact authority/local declarations and establish their declaration-level compatibility under §4.1; recover the KindBridge relation and bridge assertion when the use requires a correspondence between distinct kinds.
    3. For any required bridge, check applicability and route its consequence to R.
    4. Evaluate J(candidate, localKind, localSignatureEdition, S_local).
    5. Continue only on true; retain known false or unknown before refusing.
    6. Check freshness of relied-on regulatory and candidate support separately.

    Guard_RegChange(change, impactedDeclarations, impactedScopes).

    1. Decide whether the change alters criterion, reference scheme, applicability, or more than one.
    2. Author the required declaration episteme, check its signature qualification and any edition relation under C.3.2:5, and let C.3.1 settle kind continuity.
    3. Update Scope independently when jurisdiction/version/time coverage changes.
    4. Reassess whether the receiving use now requires a correspondence between distinct kinds, and, when it does, the obtaining KindBridge relation and its assertion's mapping, loss, CL^k, evidence, and admitted use.
    5. Evaluate affected exact candidates for the new receiving use under the new declaration edition while preserving every prior judgment indexed to its prior edition and slice; do not edit a set representation or rewrite historical judgments as a substitute.

    Guard_RegXContextUse(P, candidate, sourceKind, targetKind, targetSignatureEdition, S_target). Apply Guard_XContext_Typed and then the exact target candidate judgment. A missing target dependency yields unknown; it is not cured by a high bridge assessment.

    Last Updated: 2026-09-05 — upstream FPF commit 9fba9529 (github.com/ailev/FPF)