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 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 07:05:20 UTC

C.3:14 - Detail Map

C.3 is the head pattern for typed reasoning. It leaves each detailed mechanism at its direct neighboring pattern while preserving a discoverable route to that mechanism.

Needed detailDirect locusContent carried there
Kind identity, subkind relation, and continuityC.3.1admitted U.Kind and U.SubkindOf, criterion-entailment or exhaustive closed-domain obtaining, preorder and classification equivalence, participant-determined relation identity, and operational before/after continuity.
Declaration, candidate judgment, and extensionC.3.2KindSignature, exact four-key judgment, true/false/unknown, optional KindExtension, and scope/formality/evidence boundaries.
Cross-local kind useC.3.3identity comparison first; same-kind reuse without a bridge; for distinct kinds, an obtaining directional KindBridge, its separate assertion, preservation/loss, and a fresh admissible receiving judgment.
Local adaptation without cloning a kindC.3.4A KindUseAdaptationDeclaration for one named local use of an exact base kind, its pinned base-kind judgment and additional candidate-feature constraints, the exact three-valued KindUseAdaptationJudgment, and any separately declared KindUseAdaptationCorrespondenceDeclaration between two exact adaptation declarations.
Abstraction facetC.3.5KindAT as an editorial planning facet on one exact local kind, with no effect on the kind, declaration, judgment, extension, bridge assessment, guard, or F–G–R.
Typed guards and applied examplesC.3.ADeclaration-level kind compatibility and exact candidate-use judgments kept separate across regulatory, assurance, ESG, and Method–Work uses, including the independently grounded actual W : U.Work boundary.

Do not treat this compact head pattern as the whole C.3 discipline when a case needs declaration, classification, extension, Bridge, kind-use adaptation, abstraction, or applied-guard detail. Use the neighboring C.3 pattern that defines or constrains the live detail.