Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 14:36:52 UTC · snapshot created 2026-10-03 14:38:14 UTC · last check 2026-10-03 15:25:20 UTC

B.3.5:14.7 - SoTA-Echoing

The assurance profile uses the three contributions below.

Source lineAdopt, adapt, or rejectChange in B.3.5
A.14’s current constructional comparisonAdopt construction and identity before relation choice. Reject both a universal collection-membership predicate and any inference from belonging either to parthood or to the impossibility of parthood.S-3.d/e, CC-CT2R-3/5/5a, and the Fleet North case keep collection belonging and a separately grounded part claim distinct.
ISO/IEC/IEEE 15026-2:2022, Assurance caseAdapt its separate, maintained assurance-case structure: an elected support account stays inspectable and current beside the claim it supports. Reject a mandatory full assurance case for every direct relation. The FPF-specific validationMode triad is only the author’s declared posture; the standard is not cited as its source.The Solution, S-2/S-3, B.3.4 currentness relation, and conformance rows require support only after profile election and keep claim, support, and posture separate.
NIST’s current Digital Thread for Manufacturing programmeAdapt traceable model-based information, validation, and conformance across engineering, manufacturing, and quality. Reject a shared model, thread, exchange, or passing syntax check as proof of a world-side relation.tv:groundedBy, the trace-family rule, and the two worked cases keep the support account versioned and inspectable while the direct relation and its own rule decide what obtains; a trace or evidence item creates neither the relation nor its identity.

At comparable correctness and currentness, always exposing the heavier account costs more to write and read, while a bare direct sentence cannot meet an elected assurance need. B.3.5 therefore starts with one readable relation and adds one branch-specific account only when the publication elects the profile. The cost is that the relation assertion and its support must be checked for currentness separately.

Reopen only the affected source row and rule if A.14 changes the construction/belonging decision, a later ISO 15026-2 edition changes assurance-case structure or maintenance, or newer model-based-engineering evidence demonstrates a lower-effort way to retain direct meaning, declared posture, traceability, and independent currentness. A changed member, rule, trace, or evidence item instead reopens the affected assertion; it does not by itself reopen this architecture.