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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:25:59 UTC · snapshot created 2026-10-03 08:26:43 UTC · last check 2026-10-03 08:35:10 UTC

G.10:8.1 - Anti‑patterns and remedies

  • AP‑1 Format‑as‑governing‑specification. Remedy: keep Core surfaces conceptual (E.5.2); move serialisation to Annex/Interop; enforce CC‑G10.1.
  • AP‑2 Hidden edition drift. Remedy: require …Ref.edition pins in AuditPins and treat edition changes as RSCR‑relevant via canonical trigger kinds.
  • AP‑3 “QD archive present” but missing definition pins. Remedy: enforce CC‑G10.2 and the G.10:Ext.QDArchiveShippingPins pin declarations.
  • AP‑4 Telemetry silently becomes dominance. Remedy: keep telemetry report‑only unless an explicit CAL policy promotes it; require policy‑id recorded (ties to CC‑G10.3 and MOO discipline).
  • AP‑5 No PathSlice key → refresh becomes global. Remedy: enforce PathSlice‑keyed telemetry and path citations (G.10‑5, G.10‑6).
  • AP‑6 Cross‑Context reuse without visible crossing pins. Remedy: require CrossingBundleIds + Bridge/CL policy pins; fail fast on missing/non‑conformant bundles (CC‑G10.7).
  • AP‑7 Interop ingestion rewrites semantics. Remedy: ingest interop as cited notes only; semantics remain in G.13 (G.10‑7, G.10:Ext.InteropCitation).
  • AP‑8 Derived-view collapse. Remedy: ship sourceSetFamily, derivedViewKind, basePaletteRef, and the declared Q or reachability basis with enough explicitness that one derived tradition view cannot masquerade as the default palette meaning.