FPF Reference

C.3.A:A.4 Worked examples [I]

Preface node heading:c-3-a-a-4-worked-examples-i:34166

Content

(1) Healthcare — “Adult” dosage rule across jurisdictions

Reg source. Jurisdiction Y defines AdultPerson@RegY (AT around K2, F4) with age at least 18; your hospital Context uses AdultPatient (age at least 21). Claim. “For all x ∈ AdultPatient: dosage ≤ D/kg for drug M.” Adoption.

  • KindBridge. Map AdultPerson@RegY → AdultPatient; CL^k = 1; loss note: boundary mismatch (18↔21).
  • Scope. {jurisdiction=Y, formulary=M, time selector (Γ_time)=from 2026‑01‑01}.
  • Guard. Guard_RegAdopt passes; R penalized by Ψ(1). Policy narrows Scope to mapped cohort (age≥21) for in‑house use.
  • Change. If Y changes adult to ≥19 (new edition), run Guard_RegChange: version the kind, refresh the bridge, re‑assess CL^k, update guards.

(2) Privacy — GDPR↔CCPA PII across Contexts

Reg kinds. PersonalData@GDPR, PersonalInformation@CCPA. Internal kind. PersonalData@Product with masks per data store. Policy claim. “No sharing of SensitiveAttribute outside processors.” Adoption.

  • KindBridges. SensitiveAttribute@GDPR → SensitiveAttribute@Product (CL^k=2); SensitivePersonalInformation@CCPA → SensitiveAttribute@Product (CL^k=1, loss: biometric nuance).
  • Scope. Two policies with SpanUnion over {jurisdiction=EU} and {jurisdiction=CA}, each with its own Γ_time windows and evidence freshness.
  • Guards. For CA, apply stronger R penalty (Ψ(1)), and narrow to the mapped subset (exclude ambiguous fields).
  • Do not. Do not rename GDPR terms to local labels without a KindBridge.

(3) Export control — US EAR “600‑series” classification

Reg kind. EAR600SeriesItem@US (AT≈K2, F3→F4 as predicates are formalized). Local kind. Product@Company. Work scope. {destination=countries, end_use, time selector (Γ_time)=shipment date} for the shipping capability. Adoption.

  • KindBridge. Map EAR600SeriesItem@US → Product@Company; CL^k=2 (loss: component kit edge cases); loss notes recorded.

  • Capability guard (Method–Work).

    • U.WorkScope(Ship) covers JobSlice (destination, end use, time).
    • MemberOf(product, EAR600_mapped, JobSlice) defined (classification present).
    • Apply Ψ(2) to R (classification uncertainty) and, if reusing US scope text, Φ(CL_scope) too.

  • Outcome. Shipment admitted only for allowed destinations; higher R may require manual review.

(4) Finance — IFRS vs US GAAP “Lease”

Reg kinds. Lease@IFRS, Lease@USGAAP. Local kind. LeaseStandard@Corp used in policy “recognize lease liabilities.” Adoption.

  • KindBridge. Lease@IFRS → LeaseStandard@Corp (CL^k=2; loss: short‑term exceptions differ).
  • Scope. {jurisdiction=IFRS, Γ_time=financial period, ledger=v7}.
  • Evidence. LA plans cover subkinds (operating vs finance) per your classification; the kind‑bridge congruence level (CL^k) drives extra testing near boundary cases.