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

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 12:25:14 UTC

C.2.2:4.1 - Canonical triad relation

Definition DEF‑C2.2‑1 (Epistemic location). An epistemic location for a claim c is the tuple:

Loc(c) = ⟨F(c), G(c), R_eff(c)⟩

where:

  • F(c) is Formality (C.2.3), treated as an ordinal.
  • G(c) is Claim scope (A.2.6), treated as a set-like scope object.
  • R_eff(c) names the effective warrant for this claim and use. Its meaning and scale come from the B.3 receiving model, not from the letter R. A probability-like or ratio-scale value in [0,1] needs that model; an ordinal proxy keeps its declared ordinal meaning. If no common quantitative model is justified, report R as unquantified with the separate support and bounded conclusion, rather than substitute zero or invent a score. When a guard consumes a path-specific value, identify the actual PathId and its model (§4.8.A / G.6); a declared policy name alone does not warrant collapsing paths into one scalar.

A location always concerns one exact claim. G carries its U.ClaimScope; any stance, reference plane, effective scheme, model-use basis, working situation, evidence basis, or validity window is stated separately when it changes interpretation or use:

  • No generic K or Context value is part of epistemic-location identity; the exact subject-specific values above remain independently governed.
  • S ∈ {design, run} is the claim’s stance value; keep design-time and run-time assurance separate.
  • ReferencePlane is declared where applicable; plane crossings apply CL^plane and penalize R only.
  • When the claim is published on the Working‑Model surface, the author also declares validationMode ∈ {postulate, inferential, axiomatic} (E.14 / B.3).

Mode-to-lane hint (informative). validationMode sets the default expectation for which assurance lane carries the initial support load (B.3.3 or B.3.5). It does not add a new characteristic and does not change the meaning of R:

  • axiomatic → VA-dominant (constructive grounding or proof carriers); if ReferencePlane=world, LA may still be required.
  • inferential → VA+TA-dominant (reasoned chain + typing/alignment assurance); LA is optional and scope-bound.
  • postulate → LA-dominant (empirical validation with freshness/decay); VA is optional. In all modes, R remains warrant, not ontological truth; “proof ⇒ R=1 in the world” is a category error.

Formal-input rule. Empirical R may be N/A for a strictly axiomatic claim. Preserve the proof and its conclusion under the stated axioms; do not set R_proxy := F for an R fold. The tag line=formal, a postulative mode, or rescaling F into [0,1] supplies no conversion model. A declared F-derived ordinal proxy is valid only for its own ordinal meaning. Any F-derived value used as another quantity needs a receiving model establishing its meaning, scale, conversion, assumptions, and warranted application; in particular, checkability alone does not establish a probability about a real system.

⟨F,G,R⟩ is an assurance tuple, not a U.CharacteristicSpace; do not draw “trajectories” in ⟨F,G,R⟩.