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

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 12:00:09 UTC

E.5.3:4 - Solution — One‑Way, Acyclic Imports

Define a strict partial order over FPF ecosystem families and guard meaning flow (see E.10 V-1): imports between families point only upward in stability, and no Core semantics may derive from Tooling/Pedagogy. No linters or machine checking in Conceptual Core.

imports is a dependency DAG, not a specialisation relation (normative). Whenever an artefact exposes an explicit imports : [...] list (e.g., SignatureManifest.imports in A.6.0), treat the dependency claims carried by imports as dependency edges governed by this section: the induced imports graph MUST be acyclic (a DAG) and MUST respect the declared direction. imports MUST NOT be used to encode specialisation (e.g., ⊑ / ⊑⁺ between mechanisms); specialisation relations and any specialisation-chain claims are declared separately under their defining rules. For mechanism declarations, apply A.6.1:4.8 to the comparison claim and C.29 when a mathematical morphism is claimed.

Pedagogical Companion ⟶ Tooling Reference ⟶ Conceptual Core

  1. Allowed edges Dependencies between families MAY point only upward (toward greater semantic stability). No cycle is ever permitted.

  2. No downward import Conceptual Core patterns SHALL NOT import Tooling Reference or Pedagogical Companion family members. Tooling Reference family members SHALL NOT import Pedagogical Companion family members.

  3. Future layers Any new family is inserted below an existing one or becomes part of the Tooling or Pedagogy strata; the ordering extends accordingly.