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 10:17:34 UTC · last check 2026-10-03 10:35:10 UTC

E.18:7.1 - Common Anti-Patterns and How to Avoid Them

Anti-patternSymptomRepair
Graph expression as selected structureA mathematical graph, morphism chain, or tool pipeline is treated as the TransformationFlowStructure itself.Separate selected structure from mathematical description; use E.18.2 and C.29 when lens adequacy is live.
Flow as performed workA valuation or path is treated as a work occurrence or work procedure.Keep work planning and performed work with the A.15 family.
Gate everywhereInternal step validity, crossing, launch, and gate-decision publication are collapsed.Use A.20 for internal constraint validity, A.21 for gate fit, aggregation, and decision, and E.17 for publication.
Publication face as evidenceAn MVPK face or dashboard view is treated as evidence, gate passage, release authorization, or deontic permission.Use E.17 for publication, A.10 for evidence/currentness, A.21 for gate effects, A.2.9 for an issuing act, A.2.8.PER for strong/weak permission, exercise, non-violation, or conflict, A.2.8 only for an actual duty/recommendation/prohibition commitment, and the actual release authority for release.
Whole-flow refreshAny small edition, source-use relation, or source-publication relation change triggers a whole-structure rewrite.Refresh the smallest affected path slice, crossing, edition pin, source-use relation, source-publication relation, or publication face.