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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 17:24:51 UTC · snapshot created 2026-10-03 17:30:20 UTC · last check 2026-10-03 17:40:10 UTC

A.6.6:2 - Problem

Typical failure modes this pattern is designed to eliminate:

  1. Relation-kind elision. One verb phrase is used to cover: ID-to-registry reference, claim-to-evidence admissibility, calibration-to-standard, property-to-object attribution, policy gating, etc. Rules and invariants cannot be stated because the relation kind is unspecified.

  2. Perspective flip (dependent-view vs base-view). The same situation is described alternately as “X is anchored/grounded” and “Y is an anchor/ground”, with incompatible naming, hidden directionality, and silent re-typing of the ends.

  3. Base–witness confusion. Evidence, pins, certificates, or proofs are treated as “the base”, even when they are only witnesses for a base relation (or conversely: a true base is treated as a mere witness).

  4. Scope/time collapse. Based declarations are treated as timeless truths; time dependence is smuggled in via “current/latest/recently”, violating explicit Γ_time discipline.

  5. Γ_time used as a proxy for freshness. Authors treat Γ_time as “freshness” or “evidence decay”, collapsing TimePolicy with witness-timespan/freshness predicates.

  6. Decision use without its required basis. Declarations that gate work, publication, or assurance omit the basis required by that decision. A witness, pin, or time selector is required only when that use needs it; omitting the required basis prevents its audit.

  7. Grounding conflation. “Grounding” is used as if it were one relation, while FPF already distinguishes at least:

    • constructive grounding of a model-edge by a trace (tv:groundedBy),
    • situational/empirical grounding of an episteme via a grounding holon (C.2.1),
    • source-local meaning recovery and, when needed, an F.17 SchemeSenseCell and LocalSenseBasisRelation (not a base declaration).

  8. Slot/basing conflation. A.6.5 distinguishes relation positions, their fillers, and stored references. Umbrella basing language can hide the direct relation at the next layer, while record-edit language can be mistaken for change in the relation itself.

  9. Anchor relapse (source or meaning surrogate). “Anchor/anchoring” is used to mean “the source”, “the meaning”, “the global reference”, or “the thing that makes this true”. This hides the exact source, scheme, expression, local claim, and any obtaining basis relation behind a metaphor; the phrase alone does not let a reviewer recover them.

  10. Support bucket relapse. “Support”, “support basis”, “support relation”, or “support record” is used as a generic container for unlike relations. Some cases are direct base-dependence; others are evidence use, assurance input, causal-use support basis, mathematical-lens use, work enablement, source description, publication companionship, or ordinary help. Treating them as one support relation recreates the under-described dependence that A.6.6 is meant to repair.