G.Core:6 - Bias-annotation (informative)
Preface node
heading:g-core-6-bias-annotation-informative:135982
What this page is
This is generated FPF reference text from the specification preface or supporting sections. It helps interpret FPF; it is not FPF Reference product documentation.
Methodology
Use it to understand how the specification wants to be read, then return to a route, pattern, or work packet for active work. Cite generated IDs only when the wording changes the task decision.
Content
-
Centralization bias: One governing hub can become too thick. Mitigation: delegation-first citation; keep only Part‑G‑wide invariants and typed indices here.
-
Over-typing bias: A trigger catalogue can become overly granular. Mitigation: granularity discipline + scope notes; only add new kinds when planning/selection needs it.
-
Refactor rigidity bias: Preserving IDs can feel cumbersome. Mitigation: delegation items preserve IDs while enabling deduplication.
-
Default absolutism bias: Defaults may require conditional rules. Mitigation: Default Governing Definition Index allows conditional default rules with explicit applicability conditions.
-
Pragmatic bias: adds authoring overhead (linkage sections, alias maps). Mitigation: For ordinary linkage, cite the obligations with their use conditions directly or use a short linkage section. When moving shared norms from a
G.xintoG.Core, put exactly oneCC‑Gx‑CoreReffirst in the affected checklist (§4.5). -
Didactic bias: risks “glossy hub prose” that hides missing CC coverage. Mitigation: enforce CC/Solution coherence (E.19) and keep invariants checkable via
CC‑GCORE‑….
Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)