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

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 12:40:18 UTC

G.11:8 - Common Anti-Patterns and How to Avoid Them (informative)

Anti-patternSymptomWhy it failsRepair
Full-rerun maniaAny edit triggers a global rebuildCosts explode; drift hides (no scope rationale)Enforce slice-scoped plans (CC‑G11.1); require closure rationale for global scope
Editionless telemetryTelemetry lacks …Ref.editionReruns are non-comparable; parity breaksBlock publication on missing pins (CC‑G11.2)
Alias-as-semanticsT* labels are treated as meaningTrigger meaning fragments; regressions become untestableDock aliases through G.Core.TriggerAliasMap.G11; record canonical ids
Silent crossing during refreshRefresh changes context or plane assumptions without crossingsViolates crossing visibility; penalties become hiddenRequire crossing pins and E.18 visibility; block publication (CC‑G11.6)
Default smugglingRefresh introduces “helpful” default dominance or PortfolioMode behaviorCompeting defaults appear; downstream arguments driftCite governing definitions through G.Core.DefaultGoverningDefinitionIndex (CC‑G11.8)
Lost currentness warningA later recipient relies beyond the supported condition or window because the changed limitation was omitted.The old result can no longer support that receiving use.Keep the minimum useful warning or decision with the existing result; use a deprecation notice only for actual deprecation. An unchanged immediate use needs no skip-refresh record (CC‑G11.7).