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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 14:15:10 UTC

A.19.USCM:7 - Conformance Checklist

A USCM publication or use is conformant if it satisfies:

  1. Mechanism declaration completeness. The A.6.1 operation-local arguments/results, application predicates, identity/extent rules and laws in §4.1 are recoverable, together with the declared imports, subject, admissibility, applicability, transport, time, plane and Audit conditions. SlotIndex projects the argument/result declarations; eligibility retains its tri-state result.

  2. SlotKind discipline. SlotKind tokens match the CHR SlotKind lexicon for the roles used (InputProfileSlot, CNSpecSlot, CGSpecSlot, MinimalEvidenceSlot, ScoringMethodDescriptionSlot, ScoreProfileSlot); no generic ContextSlot is introduced. If a required token is missing, suite-dock it rather than introducing it ad hoc in the mechanism.

  3. SCP+CSLC admissibility is enforced. Any numeric transform used to produce score measures is admissible under CGSpecSlot.SCP and CSLC-lawful; illicit operations (especially “convenient arithmetic” over non-lawful scales) are excluded.

  4. ScoringMethod is explicit and auditable. Score cites ScoringMethodDescriptionSlot (edition-pinned when reproducibility matters). Its domain, codomain, Scale, polarity and use-required properties are disclosed and satisfy the applicable SCP/CSLC restrictions. Apply C.16 for any measurement claim.

  5. No implicit normalization. Score does not silently perform UNM. If CN‑Spec.comparability requires normalization‑based routing, the normalization step is explicit in choreography (Uses/pins) and auditable.

  6. No hidden scalarization. Vector scores are permitted. A scalar score is produced only when explicitly declared, and partial‑order semantics are not reduced to a scalar tie‑breaker.

  7. Unknown and evidence handling is explicit. Unknown / insufficient evidence is not coerced to 0/false. Eligibility uses GuardDecision ∈ {pass|degrade|abstain} and evaluates evidence against the effective policy (MinimalEvidenceSlot override or CGSpecSlot.MinimalEvidence).

  8. Planning and actual binding remain separate. A.15.2 carries the intended edition/policy baseline; A.15.3 governs typed filling only for independently declared positions. The actual application uses its effective bindings under §4.1, and Audit records their refs and pins. Planned selection alone does not establish actual use.

  9. Relation and plane discipline. Another bearer, scope and window, basis, method, plane, or result use gets a fresh eligibility decision. Any F.9 Bridge, kind relation, or plane relation is cited only when the score or conclusion relies on that obtaining relation, and supported loss routes to R_eff.

  10. Specialization discipline, if extended. Any specialization of USCM (⊑/⊑⁺) follows the following extension conditions: SlotKind invariance for inherited ops, no new mandatory inputs to the inherited Score op, and any extra outputs or ops expressed only via ⊑⁺.