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 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 13:55:20 UTC

E.17.EFP:4.3 - Explanation class set

The explanation-class set used in this profile is:

  • SourcePinnedExplanation
  • SourceLinkedExplanationReconstruction
  • DidacticRetelling
  • SpeculativeRetelling

In field form, the local assignment is explanationClass = SourcePinnedExplanation | SourceLinkedExplanationReconstruction | DidacticRetelling | SpeculativeRetelling.

Class assignment follows, and never replaces, the ontic first screen.

  • SourcePinnedExplanation qualifies a form or representation that expresses enough of the exact source edition for the declared use, with action-changing qualifications, source return and use-relevant omissions recoverable. It claims no whole-source coverage.
  • SourceLinkedExplanationReconstruction qualifies a non-obvious connective only when it remains in the same source ClaimGraph because a stated derivation from exact source claims recovers it, or because the source ClaimGraph already reports an exact relation occurrence whose obtaining is independently established under its defining pattern. An independently true relation that the source does not claim belongs to another target ClaimGraph.
  • DidacticRetelling qualifies teaching or onboarding use of a sufficient source form, including a partial expression, or of an exact target connected under A.6.3.CR, A.6.3.CSC or another applicable pattern when pedagogy changes claims, concern or effective scheme.
  • SpeculativeRetelling qualifies only the bounded exploratory use of a form of a separately constituted hypothesis episteme, normally produced under B.5.2. It is not a speculative form of the original source ClaimGraph.

These values are not U.Kind values, MVPK faces, semantic merit grades, source-to-target relations, or episteme identities. They state how the published form may be used after those objects and relations have been recovered.

Class assignment is per published form on a face, not one blanket label for a whole multi-face bundle. If a PlainView form stays source-pinned while a TechCard form expresses a separately related target episteme, the bundle names both exact epistemes and the class difference.