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 10:39:28 UTC · snapshot created 2026-10-03 10:40:04 UTC · last check 2026-10-03 11:25:15 UTC

C.27:5.1 - Pattern-Use Notes

  • A local resistance value of unknown is allowed. It blocks stronger use without the direct evidence or assumption boundary required for that use; it does not force a new theory.
  • A historical trend does not supply a control horizon, update rule, constraints, or stability.
  • Evidence from policy A does not carry policy B merely because both policies concern the same rate.
  • Equal final scores do not erase unequal adaptation windows, effort, rework, validity, or recovery.
  • Scalar throughput does not describe a whole multi-object work cycle when interactions and aggregation change the result.
  • Metric improvement does not establish System improvement.
  • A temporal metric does not become value merely by publication or target use.
  • Measurement as action does not make QL relevant by itself.
  • Adding fields does not turn a diagnostic or planning claim into a causal, benchmark, promise-like, gate, or assurance claim. That use changes only when the required direct result and supported-use boundary are present.
  • The C.27 result cites the direct result only when its supported use relies on it.