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 07:30:20 UTC

C.22.2:6 - Characterization, Indicators, and Comparability

ProblemCard states either a recoverable characterization relation and comparability or parity relation, or an explicit current reason why the problem can proceed without one.

The heavy content stays with existing FPF patterns:

  • C.16 carries measurement characterization, backing, and comparability discipline;
  • A.19 carries characteristic, scale, unit, polarity, and indicator-use discipline;
  • C.25 carries Q-bundles and quality-like multi-characteristic bundles;
  • G.9 carries parity, comparison-window, comparator, budget, unit, repeatability, and reproducibility pins;
  • G.0 carries comparison-frame and CG-Spec governance;
  • G.4 carries acceptance clauses and threshold predicates;
  • use G.5 for selector-facing selected-set result declaration when the problem enters a selected set; when actual audience availability is separately current, use E.17 for a source-backed publication face and return to source and E.24.PUB for the publication occurrence, form, carrier, audience, bounded use, and availability.

Missing characterization or parity relation is a current disposition. When that relation is current, apply the characterization, parity, search, or pool pattern before treating the problem as ready for P2W.

The C.22.2 candidate acceptance criterion separates functional check, constraint compliance, risk or safety boundary, parity or comparison relation, and freshness window when those relations are current. Comparison frame, CG-Spec, or comparability governance is governed by G.0. Acceptance clauses and acceptance threshold predicates apply G.4; C.22.2 may name only the needed relation, cue, or reference. Passing a test, improving one observed indicator value, or naming an acceptance phrase is not by itself sufficient for P2W use.