Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 10:39:28 UTC · snapshot created 2026-10-03 10:40:04 UTC · last check 2026-10-03 11:35:10 UTC

C.26.1:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternSymptomRepair
Every interaction is QLAny message, meeting, or API call is called probe-coupled.Require a false passive-read, export, comparison, or optimization use.
Causal action mistaken for probeA deployment or command changes the world, and QL is invoked.Use intervention or work-governing patterns unless the action is being used as a readout of the state it changes.
Bridge loss aloneExport loses local meaning, but no state-changing probe is live.Use F.9 with loss notes.
Context-word driftContext hides source-local meaning, a selected model-use organization, ClaimScope, a probe frame, or a measurement setup.Name the actual value. Retain bounded context only when using the established DDD term.
Relation token leakagecoupledBy(...) appears as if already ratified.Keep it as local drafting form; recover the relation and participants through A.6.P when unclear, and use F.18 only for a reusable name of the settled relation.