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 16:02:47 UTC · snapshot created 2026-10-03 16:03:51 UTC · last check 2026-10-03 16:25:20 UTC

A.6.P.WMR:6 - Bias-Annotation

Lenses tested: Gov, Arch, Onto/Epist, Prag, Did. Scope: Limited to recovering one method-or-work boundary claim after A.6.P has isolated it; not Universal governance for all relation ambiguity, work identity, production, evidence, publication, transfer, or receiving use.

The pattern deliberately weights Onto/Epist toward exact entities, relation kinds, claim distinctions, and non-invention, and Prag toward the shortest usable result from the four-exit architecture. Did puts ordinary wording and heterogeneous cases before heavier assurance. The Arch cost is coordinating the defining content and predicates for several exact claims rather than one convenient input, output, or result architecture. The Gov boundary is that WMR cannot admit a missing relation: a current definition must supply its predicate, participants, applicability, and occurrence rule, or the result remains missing-governor. Mitigation is the three-question ordinary core, two conditional assurance questions, four truthful exits, and independent factually unsupported, missing-information, and missing-governor reasons. Only the last can open a concrete ontology-definition question. The following domain-bias rows are informative risk cues; they add no duties beyond the checklist.

BiasCountermeasure
Artifact biasThe countermeasure distinguishes a changed continuing referent, newly constituted entity, episteme, resource, or delivered item before any result reading.
Workflow biasArrows, stages, WBS rows, and work-package names remain descriptions or plans until exact work and direct relations obtain.
Production biasWork-caused change, entity-identity inception, and production completion remain separate claims.
Data biasEpistemic source-to-use and premise or reference relations remain explicit; a datum does not become an operation argument or work input by default.
Evidence biasAn available record or application binding establishes neither truth, warrant, acceptance, nor downstream use.
Ontology-growth biasAn exact blocker replaces any convenience move toward a broad new kind.