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

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:00:05 UTC

E.10.D2:14 - SoTA-echoing and source use

Source or practice lineFPF useBoundary
ISO/IEC/IEEE 42010 architecture-description practice, retained as established-practice lineagePreserve the useful separation among described architecture, concern-bearing viewpoint, view, correspondence, and publication when testing architecture cases.It is neither FPF ontology nor a claim about the current best architecting method; it grants no evidence, assurance, gate, decision, or work authority.
ISO/IEC/IEEE 29148:2018 requirements-engineering practice, retained as established specification lineageStress that specification use depends on checkable requirements, verification or validation, and a named life-cycle use rather than official appearance.The standard does not supply C.2.1 identity, E.17.0 describing-use viewpoint selection, or the direct FPF checking relation; detailed prose is not a specification by name.
Current FPF C.2.1, E.17.0, E.24.PUB, A.1.1, A.2.6, A.10/B.3, G.11, and C.29 interfacesSupply the authoritative local identities and direct-use boundaries for episteme, viewpoint/view, publication, model use, scope, reliance, currentness, and representation.E.10.D2 consumes those interfaces; it does not mint a rival description ontology or copy every neighbor into one pattern.
Rodin’s constructive identity and near-sameness line, used as conceptual lineageKeep same-label and different-presentation cases answerable by explicit identity discriminators and evidence-backed comparison.Similar wording or a shared formal substrate does not establish the same EntityOfConcern, same episteme, an obtaining Bridge, or admissible substitution.

Reopen this source-use synthesis when a cited standard changes the practical distinction, or when the current FPF constitution, viewpoint, publication, specification-use, Bridge, or representation interface changes enough that one of the routed decisions above would be stated differently. A newer source matters only when it changes the working decision, not merely because it is newer.