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 08:25:59 UTC · snapshot created 2026-10-03 08:26:43 UTC · last check 2026-10-03 09:10:20 UTC

E.9:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternWhat it looks likeWhy it failsRepair
Process brief disguised as DRRThe record explains baton movement, packet state, review timing, or current campaign state.It describes development process rather than the FPF content decision.Remove mutable process state and keep only the decision grounds, selected answer, alternatives, and consequences.
Shadow specificationThe DRR becomes the only place where stable semantics, examples, source-use rules, or validation rules remain after the Core has moved.Later FPF readers cannot use the decision because it never became pattern content.Distribute enduring content into the selected patterns and selected non-pattern FPF kind-reference pairs; leave the DRR as provenance.
Four-label shellThe record has Problem frame, Decision, Rationale, and Consequences headings, but no decision grounds, use-value, alternatives, content distribution, or impact account by value.The minimum kernel is labeled but not substantively recoverable.Fill the decision-inspection content blocks needed for the decision, or use the lightweight variant only for true Delta-0 / Delta-1 edits.
Tentative carrier listThe DRR says a pattern may need work later, is most likely affected, or should be watched if touched.A named distribution question is postponed while pretending to be decided.Classify each named pattern or selected non-pattern FPF kind-reference pair now: selected, rejected, inherited unchanged, or outside the current decision with a named record.
Loss without use/reopen ruleThe decision summarizes, redacts, simplifies, or otherwise declares a source-loss mode but does not state admissible use, non-admissible downstream use, recoverability, and reopen conditions.A representation with undeclared source loss can be used as if it were the full source.Add the source-loss and recoverability template: preserved distinctions, dropped distinctions, admissible uses, non-admissible uses, recoverability class, and reopen or stop rule.
Free paraphrase importThe DRR restates a source-borne method, architecture claim, accepted decision-ground item, or reusable source passage in smoother prose but does not say whether it quoted, narrowed, instantiated, used as decision grounds, turned into draft guidance, kept example-only, or retired the source use.The paraphrase can widen, weaken, or redirect the source while appearing to preserve it.State the source-use result and loss and addition account, or keep the passage as a quotation or an example-only source named by value.
Decorative SoTA appendixSources are listed after the fact or treated as SoTA because they are official, recent, popular, or famous, but they do not change the selected answer, boundary, or validation obligation.The record looks researched while the decision remains unchallenged by current best-known practice.State what each load-bearing source makes the decision adopt, adapt, or reject, why it is current under E.8, and which uncertainty would materially change the answer.
Negative catalogue as the decisionDiscussion history, every rejected option, every Pillar, and every taxonomy lens occupy more space than the positive answer and first drafting action.Authors must reconstruct the selected move from exclusions and ritual coverage.Keep only alternatives and lens effects that explain the selected answer, boundary, or reopen condition. Leave the rest outside the current DRR; retain it elsewhere only when a named later use needs that history.
Proxy replay for a broad ruleA schema, invented fact pack, lane comparison, or checklist is used to justify a rule that will rewrite practitioner-facing hosts.The tested proxy can stay usable while the actual host entry, action, result, or burden degrades.Replay the complete proposed rule on an actual predecessor/proposed host pair and its true direct consumers before fanout.
Record as work or authorityA filled, approved-looking, published, or adequate-looking DRR is said to have made the decision, passed review, authorized Core change, or performed realization.Method, work, result, episteme, assessment, status/authority, and downstream change collapse.Recover only the distinctions the current claim needs; let the DRR record rather than perform them.