C.3.A:A.3 Regulatory guards
Preface node
heading:c-3-a-a-3-regulatory-guards:45641
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).
- Check P's governed scope and explicit time against
S_local. - Recover the exact authority/local declarations, KindBridge relation, and bridge assertion.
- Check bridge applicability and route its consequence to R.
- Evaluate
J(candidate, localKind, localSignatureEdition, S_local). - Continue only on
true; retain knownfalseorunknownbefore refusing. - Check freshness of relied-on regulatory and candidate support separately.
Guard_RegChange(change, impactedDeclarations, impactedScopes).
- Decide whether the change alters criterion, reference scheme, applicability, or more than one.
- Author the required signature episteme edition and let C.3.1 settle kind continuity.
- Update Scope independently when jurisdiction/version/time coverage changes.
- Reassess the bridge assertion's mapping, loss,
CL^k, evidence, and admitted use. - 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-07-28 — upstream FPF commit 17edd955 (github.com/ailev/FPF)