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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:25:59 UTC · snapshot created 2026-10-03 08:26:43 UTC · last check 2026-10-03 08:35:10 UTC

A.19.USCM:0 - At a glance — didactic, informative

  • Suite stage: score (ordering lives only in A.19.CHR:4.5 / suite_protocols; suite membership is a set in A.19.CHR:4.2).
  • Inputs, conceptual: an admitted measure profile for the exact evaluated bearer, plus CNSpecRef, CGSpecRef, and ScoringMethodDescriptionRef; their editions name the criteria, claim scope and selected slices, qualification window, comparison or reference basis, evidence policy, and intended result use. MinimalEvidenceRef may override the CG-Spec minimum.
  • Output: ScoreProfileSlot = a set of score measures (vector scores are first‑class; a scalar score is allowed only if explicitly declared).
  • Non‑goals: does not normalize (UNM), aggregate (ULSAM), compare (CPM), select (SelectorMechanism), threshold, publish, or emit telemetry; it is a scoring step with explicit admissibility and evidence surfaces.
  • P2W seam: an A.15.2 baseline selects editions and policies, including ScoringMethodDescriptionRef when USCM is used. A.15.3 typed filling applies only to independently declared receiving positions under A.19.CHR:4.7.2. Actual Score bindings obtain under §4.1; Audit records the effective refs and pins.
  • Failure mode: tri‑state guard (pass|degrade|abstain); unknown never coerces to pass, and MUST NOT be coerced to 0/false.
  • Quick rule of thumb: if CGSpecSlot.SCP is missing → ScoreEligibility = abstain (fail‑closed); if ScoringMethodDescriptionSlot is missing → ScoreEligibility = abstain (no implicit scoring method); if CN‑Spec.comparability requires normalization‑based comparability → normalization MUST be explicit in choreography (Uses/pins), never hidden inside Score.