fpf.tools
Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading
Source · lines 115071–115080

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 16:02:47 UTC · snapshot created 2026-10-03 16:03:51 UTC · last check 2026-10-03 16:05:05 UTC

G.3:1 - Problem frame

A team is defining or evolving a CG‑Frame (via G.1) and has plural, competing SoTA traditions and constructs (via G.2). The team needs an admissibility-ready CHR publication that makes downstream work possible without hidden semantic drift:

  • CAL authoring (G.4) needs typed, admissible operands and guard/legality surfaces to build admissibility and acceptance rules (thresholds and policy cut‑offs remain governed by CAL).
  • Selector/dispatch (G.5) needs CHR‑typed quantities and explicit provenance pins so selection can remain set-returning and auditable under admissible orders.
  • Reuse beyond the defining source or use must name the exact characteristic and scale editions, bearer, scope and validity window, reference plane, evidence, and intended downstream use. Cite an F.9 relation only when it actually obtains between the named F.17 cells; any claim that relies on the relation for this use remains a separate bounded-use claim under C.2.1 and F.9; its evidence-bearing reliance follows A.10 and any applicable B.3 assurance requirement.

The resulting publication is a CHR Pack that is CG‑Frame‑scoped, notation‑independent, and UTS‑published, with explicit edition/policy pins sufficient for reproducibility and RSCR.