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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:25:59 UTC · snapshot created 2026-10-03 08:26:43 UTC · last check 2026-10-03 09:25:05 UTC

A.6.4:11 - SoTA-Echoing

Practice question. What current transformation practice helps a reader keep a transformation definition, its execution, and a correctness claim separate—and what, if anything, can that practice say about whether the source and receiving epistemes concern different entities?

Source or practiceContribution used hereLimit and disposition
Zhao et al., KBX: Verified Model Synchronization via Formal Bidirectional Transformation (2024)KBX separates formal bidirectional-transformation definitions, generation of a synchronizer, and consistency verification.Adapt. This supports the declaration, application, and use-claim split. KBX synchronizes models; it does not decide FPF EntityOfConcern identity or make one bounded use sound.
He and Zan, BIT: A template-based approach to incremental and bidirectional model-to-text transformation (2024)BIT distinguishes a usable surface language, a formally defined core, executable printer/parser behavior, round-trip properties, and empirical cases.Adapt. This supports keeping readable first use, formal declaration, execution, and well-behavedness evidence distinct. BIT’s model/text synchronization does not decide whether two FPF epistemes concern different entities.
Current FPF C.2.1, C.29, and A.6.3.RTC.2.1 identifies each episteme and EntityOfConcern; C.29 bounds the mathematical lens; A.6.3.RT handles representation change with preserved EntityOfConcern.Adopt. These are the direct identity and routing rules.
Fibrations, cospans, Fourier transforms, and data/model mappingsThese provide mathematical lineage and stress cases for endpoints, composition, invariants, and loss.Retain as lineage; reject as ontology shortcut. None proves that the EntityOfConcern changed or that a receiving use is sound.

The A.6.4 split among r, q, and any application occurrence is a bounded FPF synthesis from these distinctions, not an externally established retargeting ontology.