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 05:05:10 UTC

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

Anti-patternWhy it failsRepair move
Endpoint dossier before targetOrdinary work stalls before a useful table, diagram, or notation exists.Produce the target and source comparison first; open exact identities only at a named receiving-use trigger.
Every format shift is harmlessRepresentation changes alter inspection, salience, and recoverability.State the practical representation/reasoning delta and compare source with target.
Scheme, semiotic mode, and viewpoint collapsedUsers cannot tell what changed or which claim needs review.Name only the distinction that changes use, and keep viewpoint under E.17.0 when it is current.
Notation becomes ontologyGeometry or notation appears to define the world.Point every target-side relation back to source claims or establish the new ontology claim separately.
Occurrence description treated as occurrenceA changed description, publication, layout, or carrier appears to change relation identity.Keep six-participant identity on the occurrence and identify the description under C.2.1.
Retargeting hidden as representationA changed EntityOfConcern is mislabeled as same-concern conversion.Use A.6.4 when the concern changes.
Latent case firstDecode demands overwhelm the ordinary representation task.Keep latent use exploratory until decoding access and recovery evidence are explicit.