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 02:22:15 UTC · snapshot created 2026-10-03 03:38:22 UTC · last check 2026-10-03 04:10:10 UTC

A.6.3.CSC:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternFailureAvoid by
Helpful summary becomes authorityA reader relies on the coarsened rendering for a downstream decision that its claims do not support.State the unsupported downstream use and reopen trigger.
Citation launderingA coarsened rendering is cited as if it were the source.Keep the source-bearing side named and reopenable.
Label-as-evidenceA reader treats a lookup handle as evidence for a claim in the source.State retrieval-only use.
Redaction-as-closureWithheld detail is treated as resolved detail.State the sharing boundary and accountability reopen condition.
Stance cureprojection or nonEquivalent is used instead of establishing the operative relation, supporting its bounded use, or stating loss and source return.Recover the operative relation under its governing pattern, support its bounded use, and keep the CSC loss account and source return. For a Bridge between exact local senses with different interpretation bases, use F.9 with a separate bounded-use claim; an F.9.1 stance note remains optional reader help.
Briefing-as-workA reader treats a summary as sufficient basis for a work plan, execution cue, gate decision, or approval.Use the applicable A.15 pattern for the Work plan or actual Work. For an authority-looking claim, select the matching A.6 A6-AW-* row by the assertion and follow its direct subject pattern; use A.20 or A.21 for the actual constraint or gate claim.
Summary-chain source lossA note summarizes an already coarsened note and loses the original source and loss envelope.Keep the same source-bearing side and added loss delta visible, or reopen that source-bearing side.
Aggregation EntityOfConcern shiftA quotient or bundle turns several entities or alternatives into one new proxy EntityOfConcern.Apply A.6.4 rather than treating EntityOfConcern shift as a same-lineage source-to-rendering case.