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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 05:55:15 UTC

A.19.ULSAM:5 - Archetypal grounding (didactic, informative)

A.19.ULSAM:5.1 - Tell

  • In CHR, ULSAM exists to keep the stage fold_Γ? explicit: if a pipeline wants folding, it invokes ULSAM.Fold_Γ; otherwise it skips the stage. Folding MUST NOT be smuggled into USCM.Score, CPM.Compare, or SelectorMechanism.Select.
  • For a U.System decision: ULSAM explicitly folds the admitted measures about the named System, under the declared grouping or membership basis and CG-Spec fold policy, only when that aggregate result is actually needed.
  • For a U.Episteme assessment: ULSAM explicitly folds the admitted evidential or measurement set about that episteme into an aggregate coordinate, using an aggregation model justified for that exact quantity and support dependence; reliability-like wording alone supplies no weakest-link law.

A.19.ULSAM:5.2 - Show

Scenario A (manager-facing): “roll up” a multi-metric readiness into one reliability-like coordinate.

  1. A CHR pipeline produces a set of admitted measures (post-USCM or directly from characteristic measures): MeasureSetSlot = {m₁, m₂, …, m_k}.
  2. The team wants a single “readiness” measure m_ready to be used as an input to later comparison/selection. The temptation is to “just average” or “just do weighted sum”.
  3. ULSAM forces three explicit questions before folding:
    • Admissibility: Is the fold admissible under CGSpecSlot.SCP (units/scale) and CGSpecSlot.Γ_fold (declared fold kinds)?
    • Evidence: Is the evidence posture sufficient under MinimalEvidence? If not, do we degrade or abstain?
    • Policy identity: What is the identity of the fold (which ΓFoldRef, which edition)?
  4. Only then, the pipeline performs: Fold_Γ(MeasureSetSlot, CNSpecSlot, CGSpecSlot, GammaFoldSlot, MinimalEvidenceSlot?) → (AggregatedMeasureSlot, ContributorSetSlot?). The audit records ΓFoldRef and (optionally) the contributor surface.

Scenario B (engineer-facing): proposed aggregation across different bases.

  • A project tries to fold measures with different bearers, membership rules, scales, comparison bases, or reference planes. ULSAM first checks whether one admitted set and lawful fold can be stated. If the conclusion relies on an F.9 Bridge, kind relation, aggregation or membership relation, or plane relation, the project cites that exact obtaining relation and its loss; otherwise it constitutes separate folds or fails closed.