Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 10:39:28 UTC · snapshot created 2026-10-03 10:40:04 UTC · last check 2026-10-03 10:55:17 UTC

A.19.USCM:11.1 - SoTA alignment map

SoTA practice pointer, post‑2015+Primary source examples, post‑2015+Where it connects to USCMAdoption status
Prefer monotone and interpretable scoring surfaces where appropriateExplainable additive and monotone model lines, e.g., Lou et al. 2016; Nori et al. 2019; monotone deep lattice style models, e.g., You et al. 2017Expressed as admissibility‑bounded transform freedom via CGSpecSlot.SCP and explicit scalarization rules; method details stay out of the kernelAdapt
Treat probabilistic scores as measures requiring calibration, not raw outputsCalibration practice, e.g., temperature scaling (Guo et al. 2017) and successorsExpressed as “score is a measure on an explicit scale,” bounded by SCP+CSLC and evidence gating; calibration itself is wired as method semantics, not kernel lawAdapt
Keep uncertainty explicit and allow set‑valued scoring when appropriateModern conformal prediction practice, e.g., Romano et al. 2019; Barber et al. 2021Expressed as “vector scores allowed; unknown not coerced; no hidden scalarization,” enabling downstream set‑valued comparison/selectionAdapt
Keep architectural commitments traceable to one governing patternISO/IEC/IEEE 42010:2022 architecture description disciplineExpressed as explicit governing-pattern assignment and Tell+Cite stubs elsewhere (no competing semantics)Adopt

Notes per row

  1. USCM does not “implement a particular scoring model”; it preserves a stable, admissibility‑gated surface on which such models can be wired.
  2. Calibration is treated as a lawful transform family that must live within SCP+CSLC; the kernel does not mandate a specific calibration method.
  3. Set‑valued scoring aligns with USCM’s “vector first, scalar by declaration” law, and is naturally consumed by CPM/SelectorMechanism without forcing a spurious total order.
  4. Governing-pattern traceability is used here to keep the spec teachable and non-duplicative; it does not add new governance cards or admissibility gates.