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 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 05:45:20 UTC

C.30.AD:7 - Common Anti-Patterns and How to Avoid Them

Anti-patternSymptomRepair
Description-as-architectureA document, diagram, model, graph, view set, or card is said to be the architecture or to create an obtaining architecture relation.Recover the exact holon, ArchitectureRelation occurrence, or selected structure; keep the episteme, representation, publication, and source-to-use relation distinct.
Viewpoint-as-structure-kind or view constructorA stakeholder, role, concern, viewpoint label, authoring template, query, or bundle is used as if it named the selected structure or granted U.View membership.Use E.17.0 for exact viewpoint conformance and C.30.ASV for selected structure and kind.
Multi-view fogMany views are listed, but their separate C.2.1 identities, conformance relations, selected structures, or correspondence cannot be recovered.Add the description and viewpoint references, conformance relations, selected structures, and correspondence claims or relations that actually hold.
Coarse model as subject hierarchyA grouped or lower-resolution description is treated as proof that the subject has the same levels, parts, or relations.State the description-side grouping, mapping, preserved and lost distinctions, and allowed use; establish any subject-side relation separately.
Specification-as-authorityA specification-looking description is used as Work, gate passage, decision, assurance, evidence, work authorization, or release authorization.Declare the specification use and use the pattern that defines or tests the other claim.
Freshness launderingA recently generated diagram is treated as adequate because it is current.Record the bounded freshness claim, source edition, and refresh trigger; do not treat currentness as adequacy, evidence, grounding, or assurance.
Architecture-documentation takeoverPractitioner guidance is dominated by diagrams, publications, and wording guards instead of architecture relations, structures, descriptions, and views.Keep C.30 about architecture and C.30.AD about descriptions and their use; use the relevant patterns for representation and publication.