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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 02:22:15 UTC · snapshot created 2026-10-03 03:38:22 UTC · last check 2026-10-03 04:45:20 UTC

F.0.1:11 - SoTA-Echoing

Current practice line and exact sourcesDecision and effect in F.0.1Limit kept visible
ISO 1087:2019 and ISO 704:2022 distinguish objects, concepts, definitions, and designations.Adopt, with a boundary. Recover the source-local designation and concept contribution before comparison.Standard status establishes neither one universal vocabulary nor the receiving claim.
Kapferer and Zimmermann, Domain-driven Architecture Modeling and Rapid Prototyping with Context Mapper (2021), keep a software-domain model and language within a named DDD boundary and make inter-boundary relations explicit.Adapt as a software-domain example. Use that boundary only when a DDD bounded context is the actual subject.It does not warrant a transdisciplinary U.BoundedContext or make that object the source of all meaning.
Abd Nikooie Pour et al., Results of the Ontology Alignment Evaluation Initiative 2025 (2025); Giglou et al., LLMs4OM (2024); Hu and Ichise, From Matching to Retrieval: A New Role for LLMs in Ontology Alignment (2025); and Qiang et al., OAEI-LLM (2024).Adapt. Use lexical, structural, retrieved, or model-produced correspondences to find candidates worth inspecting; establish an F.9 relation only from the exact recovered senses and its relation profile.A benchmark result, similarity score, or model answer establishes neither semantic identity nor the separate C.2.1 claim that a Bridge suits a receiving use.
W3C SHACL (2017) and DCAT 3 (2024) separate constraints, validation, catalog metadata, versions, and provenance from described subject claims.Adapt. Keep source and edition metadata recoverable and use a compact source note when useful.Metadata form, validation, or provenance establishes neither meaning, truth, reliance, nor assurance.

The non-dominated combination is a plain local answer first, an exact durable address only for reuse, an inspectable relation only when current, and receiving-use judgment separately.