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 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:8 - Common anti-patterns (didactic, informative)

Anti-patternSymptomWhy it fails in FPFHow to avoid
Hidden rollup inside scoring“Our score already averages everything.”Violates the “no hidden aggregation” law and hides Γ‑fold identity.Keep USCM.Score scoring-only; use ULSAM.Fold_Γ as an explicit stage.
Averaging ordinalsMeans on ranks/levels, or unitless mixingIllegal under CSLC/SCP unless explicitly allowed.Keep ordinal outputs as ordinal; compare via CPM; if folding is required, use an ordinal-legal fold explicitly declared by Γ_fold policy.
Implementation default Γ‑fold“If not specified, we use X.”Breaks replayability and violates Γ‑fold admissibility.Require GammaFoldSlot to resolve to CGSpecSlot.Γ_fold or pinned override.
Coercing unknown to a number“Missing metric becomes 0.”Violates tri-state guard discipline; silently changes meaning.Use FoldEligibility_Γ with `{pass
Folding after the admitted set or basis changedMeasures with different bearers, membership rules, scales, scopes or windows, comparison bases, or planes are folded “as-is”The result no longer follows from one declared set and lawful fold; relation labels cannot repair that gap.Re-establish the admitted set and eligibility. Cite an obtaining relation and supported loss only when the fold or receiving use actually relies on it; otherwise keep separate folds or abstain.
Treating fold_Γ as mandatoryAlways folding even when not neededUnnecessary aggregation can hide distinctions needed by the receiving use.Keep fold_Γ? explicitly optional in protocols; prefer vector+CPM+Selector when possible.