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 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 13:30:20 UTC

B.2.2:5.4 - Bias-Annotation

Bias riskFailureMitigation
Named aggregate as systemA fleet, platform, or cell name is treated as system recognition.Apply B.2 to one exact candidate; require the complete A.1 criterion and the direct U.System criterion.
Component evidence transferComponent certificates are read as assurance for the proposed new whole after its recognition under U.System.Re-test each claim against that exact recognized system and use exact evidence or assurance relations; do not transfer support by label.
Coordination as wholeA controller, protocol, or coordination relation is treated as automatic system MHT.Recover the obtaining relation, then require B.2 whole reidentification plus complete A.1 and U.System recognition; keep any support separate.
Description as systemDashboard, simulation, model, twin, or bill is treated as the operating system.Use episteme, publication, source-use, and architecture-description patterns for description objects.
Transformation as containmentAn external system changes a holon and is treated as its part or containing whole without a separately obtaining part-whole relation.Use A.12, A.3.4, A.15.1, B.2.5, and part-whole patterns separately.