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

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 06:10:20 UTC

G.11:2 - Problem — Why naive refresh breaks comparability and admissibility

A refresh loop fails (conceptually) when any of the following happens:

  1. Full-rerun mania. Minor edits (e.g., a single Bridge calibration) trigger pack-wide rebuilds without a traceable scope rationale.
  2. Editionless telemetry. Telemetry signals are recorded without edition pins, making reruns non-comparable and parity-unreplayable.
  3. Alias-as-semantics. Local trigger aliases are treated as if they define meaning, fragmenting refresh semantics across patterns.
  4. Silent crossings. Refresh actions implicitly change crossing assumptions (UTS, Path, or policy pins) without a visible CrossingBundle.
  5. Orchestration smuggles semantics. Refresh introduces new default behaviors (dominance, PortfolioMode, or Γ-fold) or coerces partial orders into scalars “for convenience.”