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

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

C.3.4:8 - Interactions

C.3.4:8.1 - With Kinds and Subkinds

Use an adaptation declaration for procedural tailoring. If the criterion becomes conceptual and stable, identify another local kind and establish the exact obtaining U.SubkindOf relation. Repeated declaration use, promotion language, and a catalog link do not establish that relation.

C.3.4:8.2 - With Judgment and Declarations

  • The base KindSignature episteme supplies the kind criterion and its own F.
  • The separate adaptation declaration supplies additional candidate-feature constraints or vocabulary bindings and may have its own F.
  • The exact KindUseAdaptationJudgment pins both editions and preserves unknown; neither formality value belongs to the kind, candidate, or truth value.
  • An optional extension-like result remains only a pinned-edition representation of true adaptation judgments.

C.3.4:8.3 - With KindBridge

A locality change first prompts kind-identity comparison. When the same base kind continues, select the receiving signature and adaptation declaration and evaluate a fresh candidate result without a KindBridge. When two independently identified kinds are distinct and an exact directional correspondence is relied on, establish the C.3.3 KindBridge, its assertion, the receiving declaration, and any needed adaptation-correspondence declaration. Only justified bridge penalties affect R; F, G, admissibility, and classification truth remain unchanged.

C.3.4:8.4 - With Guards

Guard_KindUseAdaptation designates exact adaptation and base-signature editions, checks admissibility, evaluates an admissible candidate, checks Scope separately, and keeps not-applicable, unknown, and refusal distinct. For distinct-kind cross-local use, it composes with the C.3.3 guard only after the bridge and receiving declarations are recoverable. For same-kind reuse, it performs the fresh receiving evaluation without inventing a bridge.