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

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 17:15:04 UTC

E.18.1:6 - Bias-Annotation

Lenses tested: Gov, Arch, Ontological and epistemic, Prag, Did. Scope: accepted problem-side record plus carried distinction moving toward FPF applications.

  • Governance bias (Gov): permission, gate, release, assurance, and decision cues remain local cues until the relation and participants are stated: an A.2.8.PER permission result, A.21 GateDecision, A.15.1 release U.Work occurrence plus any required named subject release predicate, B.3 assurance result, or direct decision result. The word authorization supplies none of them.
  • Architectural bias (Arch): diagrams, selected structures, and module-interface language help formulate the next relation question; they do not replace the accepted claim, receiving use, separately identified viewpoint or model-use participant, applicable pattern contribution, or returned result.
  • Ontological and epistemic bias: a source publication, diagram, compact note, or formal declaration remains separate from the subject EntityOfConcern and from the relation or result claimed through the particular pattern contribution used for the current question.
  • Pragmatic bias (Prag): the carry-through structure is useful for action without becoming a prescribed project procedure.
  • Didactic bias (Did): the local P2W mantra and positive carry-through structure come before the heavier relation aids, so precision does not bury the working P2W application.