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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 05:45:20 UTC

A.3.2:6 - Bias-Annotation

This pattern mainly blocks six recurring biases:

  • carrier-as-description bias: a PDF file, repository, screen, or presentation carrier is treated as the method description. Identify the episteme whose ClaimGraph is being read, then record its C.29 representation and publication relations separately;
  • description-as-method bias: the representation is treated as the way of doing itself;
  • description-as-work bias: executable or operational-looking representation is treated as dated work;
  • approval-as-proof bias: accepted, approved, or regulated descriptions are treated as evidence, gate passage, or safe execution;
  • notation-prestige bias: code, formal notation, or solver files are treated as more authoritative than procedures, diagrams, or guidelines. Compare the actual method claims; representation form supplies no priority;
  • imperative-metaphor bias: graph, query, predicate, or process-model representation is treated as an ordered work-control claim.

First identify the claim-bearing episteme, the claim it makes, and the Method it concerns. When the use needs them, keep its C.29 representation, publication occurrence, publication form, and presentation carrier separate. State each additional plan, Work, evidence, gate, authority, mechanism, formal, or mathematical claim under its exact predicate or constraint with an optional subject-pattern locator.