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

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:00:10 UTC

E.10.D2:4.1.3 - Specification-use admission

Use a ...Spec name only when the receiving use depends on specification force and all applicable conditions are recoverable:

  1. the exact description episteme and its C.2.1 constitution;
  2. checkable claims, invariants, criteria, or acceptance conditions in its ClaimGraph;
  3. a named harness, validation, conformance, measurement, or evaluation relation capable of checking those claims for the stated use;
  4. when viewpoint selection affects reliance, the named describing use and its exact selected viewpoint are preserved or explicitly updated.

Declared formality, notation discipline, comparators, tolerances, and measurement rules are named when the claims depend on them. They do not substitute for the checkable claims or the harness. If the conditions are absent, call the episteme a description and present proposed criteria as proposals; a Spec suffix, schema, signature, approval, or publication does not supply specification force.

Specification use does not create another episteme identity. A revision that changes ClaimGraph, EntityOfConcern, or effective ReferenceScheme identifies another episteme under C.2.1; a changed harness, evaluation result, publication, or relying use changes its own neighboring object or relation.