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

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

F.19:6 - Bias-Annotation

F.19 deliberately biases toward direct, reader-usable technical prose. The protected value is kind-preserving clarity, not brevity by itself. A longer rewrite is better when it restores a participant, relation, boundary, or operational detail that the declared use needs.

Likely biasFailureCountermove
Formal-completeness biasSymmetrical contrasts, caveats, and lists look rigorous although they add no supported distinction.Apply the contribution test and state the positive path first.
Adversarial-reader biasAny imaginable mistake is treated as a reason for a guard.Require an independent ground and a plausible intended reader.
Apparatus-preservation biasA process, status, record, card, schema, or quality-proof phrase is replaced by another wrapper.Recover the object and action, then remove or move the wrapper.
Overformalization biasClear metonymy, ellipsis, or a PatternID citation expands into type labels and Work machinery.Formalize only a live distinction or unresolved relation.
Genre-flattening biasUseful rhythm, evocation, or deliberate ambiguity is treated as defective technical accumulation.Apply F.19 only where precise technical recognition or action is the declared use.