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:10:10 UTC

B.2.3:5.4 - Bias-Annotation

Bias riskFailureMitigation
Library as theoryA repository, dashboard, or reading list is treated as one claim-bearing episteme.Identify B.2’s exact candidate, execute A.1, and test its C.2.1 ClaimGraph/EntityOfConcern/ReferenceScheme constitution.
Publication as epistemeA PDF, report, standard document, model card, or dashboard is treated as the episteme itself.Keep the episteme, publication form, and carrier distinct under C.2.1, E.17, E.24.PUB, and source-use patterns.
Episteme agencyA theory, standard, or doctrine is described as performing Work or enforcement.Recover every exact acting System through A.13 and let A.15.1 independently admit the Work. Add F.6 only when the receiving account expressly consumes precise assignment-bound attribution; a missing or failed attribution does not demote the Work.
Morphing as MHTView, translation, coarsening, or retargeting is called a new episteme whole.Use A.6 episteme-morphism patterns unless B.2 whole reidentification remains current.
Source trust transferTrust in constituent sources becomes assurance for the result episteme.Re-evaluate assurance and source-use relations for the result episteme; retain only those that still apply to its exact claims.