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:20:09 UTC

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

Anti-patternSymptomRepair
Method name as change“This method transforms X” is treated as an actual occurrence.Name the continuing changed subject, boundary, and before/during/after facts; keep the method under A.3.1.
Process diagram as workA workflow diagram is treated as enacted work.Use E.18 or A.3.2 for the diagram; use A.15.1 for dated work.
Dynamics model as permissionA transition law is used to approve action.Keep A.3.3 for the model; use evidence, gate, decision, and assurance patterns for use authority.
Temporal trend as interventionA rate or rhythm trend is treated as proof of changed behavior under an intervention.Use C.27.TA and C.27, then identify the continuing changed subject and its before/during/after facts separately.
Formal construction as workA morphism or proof construction is treated as work performed in a project-world object.Use C.29 or the direct formal pattern for the mathematical relation; name realization and work separately.
Publication as transformationA dashboard or report is treated as the changed state.Use publication or source patterns for that artifact; identify the changed subject separately.
Sliced trajectory as compositionSamples, subintervals, method steps, work parts, concurrent changes, or flow nodes are declared components of one transformation by containment or proximity.Independently identify each actual transformation. If the use needs a positive composition claim, return the parked blocker in 4.2.1; this edition does not choose its future architecture. Sampling or subdivision likewise supplies no evidence of indivisibility.
Resolution-level identification as partlessnessA change identified as one occurrence at the resolution chosen for the task is treated as necessarily atomic, indivisible, or partless, or as automatically composite and holonic.Keep the independently identified U.Transformation; infer neither presence nor absence of finer parts. Do not make a positive composition or A.1 claim until a future accepted architecture supplies its basis.
Work-caused change as productionA change that follows U.Work is called a produced entity or completed production.First close the named work/transformation connection through 4.2.4 or keep its blocker; then separately test production-work participation, first existence of the subject, and the applicable production-completion criterion under A.15.PROD.