C.3.A:Annex A - Regulatory and compliance alignment [A/I]

Preface node heading:c-3-a-annex-a-regulatory-and-compliance-alignment-a-i:59082

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

Purpose and fit

Regulations name categories such as Adult person, Class II medical device, Personal data, and Lease. A local context needs both a faithful category correspondence and explicit jurisdiction/version/time applicability. The kind channel answers “about what”; USM Scope answers “where and when”; neither answers whether one exact local candidate satisfies the target criterion.

Normative obligations

C-REG-1 (Regulatory declarations). Each used regulatory category SHALL be an exact authority-context local kind with a separately identified KindSignature declaration episteme edition. Any F value characterizes that episteme, not the kind.

C-REG-2 (Kind correspondence). Cross-context category use SHALL first compare authority and local kind definitions. If the receiving policy relies on a directional correspondence between distinct kinds, it SHALL recover an obtaining KindBridge relation between exact authority and local kinds plus a separate bridge assertion with mapping, pinned editions, preservation/loss, evidence, definedness, admitted use, and any CL^k required by the consumed assurance or calibration account.

C-REG-3 (Scope). Jurisdiction, effective dates, grace periods, and other contextual applicability conditions SHALL be Claim scope over exact context slices with explicit Gamma_time.

A product-family or platform distinction belongs in Scope only when it is a context-slice dimension of the claim; when it classifies the target entity, recover it as an exact kind and, for candidate-bearing use, an exact candidate judgment. A direct candidate feature remains with its own governor and SHALL NOT be treated as a Scope condition.

C-REG-4 (No synonym shortcut). A legal label, translation row, or policy card SHALL NOT substitute for the KindBridge relation, its assertion, or the target declaration.

C-REG-5 (Exact candidate use). Whenever a policy is applied to candidate candidate, the guard SHALL check receiving admissibility first. For an admissible request it SHALL evaluate J(candidate, localKind, localSignatureEdition, localSlice) and retain true, false, or unknown; otherwise it retains not-applicable without a judgment. Declaration compatibility alone is insufficient.

C-REG-6 (Consequences). Justified kind- and scope-bridge consequences SHALL affect R only. They SHALL NOT alter F, G, or the candidate judgment.

C-REG-7 (Editioning). For a law change that changes the criterion, identify the new declaration episteme and check its signature qualification and any edition relation under C.3.2:5. A change in claim applicability changes Scope. C.3.1 decides kind continuity. Guards SHALL pin editions and time and SHALL NOT rely on “latest”.

C-REG-8 (Local adaptation). A local nuance MAY use a RoleMask declaration. If it becomes a stable conceptual distinction, the context SHALL separately identify any new local kind and establish its obtaining subkind relation; mask reuse does not perform that change.

Regulatory guards

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

  1. Recover the authority/local declarations and establish their declaration-level compatibility under §4.1 steps 1–2; recover the KindBridge relation and assertion when the use requires a correspondence between distinct kinds, and check bridge applicability.
  2. Check P's governed scope and explicit time against S_local.
  3. Check local candidate admissibility; on not-applicable, refuse without forming a judgment; otherwise evaluate J(candidate, localKind, localSignatureEdition, S_local).
  4. Continue only on true; retain known false or unknown before refusing.
  5. Apply only the justified R consequence of each required, applicable bridge.
  6. Check freshness of relied-on regulatory and candidate support before allowing use.

Guard_RegChange(change, impactedDeclarations, impactedScopes).

  1. Decide whether the change alters criterion, reference scheme, applicability, or more than one.
  2. If the declaration’s criterion, interpretation or applicability changes, identify the required edition under C.3.2:5 and use C.3.1 to settle kind continuity. A change confined to the policy’s jurisdiction or effective period can leave the entire classification declaration in force.
  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, evidence, admitted use, and any CL^k required by the consumed assurance or calibration account.
  5. For an affected candidate use, apply the declaration in force in the receiving slice. Preserve judgements already made under their own editions and slices. If the only changed decision concerns where the policy applies, reassess its coverage and reuse classification results whose inputs and grounds still hold.

Guard_RegXContextUse(P, candidate, sourceKind, targetKind, targetSignatureEdition, S_target). Use Guard_XContext_Typed to check that the candidate and slice are admissible before evaluating the target criterion. If the admissibility test returns not-applicable, the guard refuses the use without a classification judgement. For an admissible request, a missing target dependency yields unknown if the available facts leave the criterion unsettled. The bridge assessment supplies neither the missing fact nor the judgement.

Worked examples [I]

Adult dosage across jurisdictions. In this example the authority kind AdultPerson@RegY uses threshold 18 and the hospital kind AdultPatient uses 21. The obtaining KindBridge and its assertion state the boundary loss and CL^k=1. The hospital evaluates its target signature edition in the dated formulary slice. For candidate P-44, suppose the only age information is that P-44 met the authority threshold that day. Ages of 20 and 22 are both compatible. The target age condition remains unknown, and the guard refuses a use requiring positive classification. An attested bound of at least 21 would settle the hospital's age condition under these rules.

GDPR and CCPA. Two source kinds relate to independently identified product-context kinds through separate bridges/assertions. Each policy has its own jurisdiction/time Scope. A data item is governed by a fresh target judgment; an alias table is support, not classification.

Product classification and shipping. Evaluate the product against its category in the target signature edition. The shipping policy uses that judgement together with the particular shipment, destination, intended use and date. Establish the kind correspondence or scope translation where each is needed. If the shipment exceeds the policy’s residual-risk threshold for automatic release, the policy may call for manual review even when the product classification is settled.

IFRS and US GAAP Lease. Each authority kind and local corporate kind remains independently identified. The bridge assertion records the short-term-exception loss. Test planning targets boundary candidates under pinned target declarations rather than treating one shared label as truth.

Guidance and migration [I]

  1. Inventory regulatory claims, exact category declarations, and applicability slices.
  2. Recover or author target KindSignature declaration editions; keep F on those epistemes.
  3. Compare kind identity; establish KindBridge relations and separate assertions with loss and admitted use only for required correspondences between distinct kinds.
  4. Rewrite candidate-bearing guards to pin candidate, local kind, signature edition, and slice.
  5. Preserve unknown and record refusal separately.
  6. Route Scope through USM and bridge consequences through R.
  7. Use RoleMask declarations for local procedural tailoring; separately establish a new kind/order relation only when the distinction becomes conceptual and stable.

Manager's compact pattern [I]

  • Where and when? Claim scope over exact context slices.
  • About what? Exact local kind and signature declaration; KindBridge relation/assertion for a required correspondence between distinct kinds.
  • Which exact thing? Fresh target J(candidate, kind, signatureEdition, slice).
  • Can we act? A separate guard disposition after scope, judgment, bridge, freshness, and policy checks.

Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)