fpf.tools
Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading
Source · lines 26242–26251

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

A.14:10 - Common Anti-Patterns and How to Avoid Them

  • Member as component. A person, team, document, or object belongs to a collection and is then counted as structurally integrated.
  • Aspect by label. A Characteristic, concern, viewpoint, view, projection, partition, heading, dashboard slice, or time window is called an aspect and entered into a part tree. Recover the actual claim; require the full AspectOf occurrence when structural parthood is intended.
  • System-role expression as part. A local kind, assignment, or relation position is put into a part tree instead of using its direct pattern.
  • Method as part. A Method, recipe, or algorithm is treated as a structural component instead of using Method, MethodDescription, Work, or transformation patterns.
  • Portion without measure. Some fuel, data, time, or text is named as a portion without measure kind, unit, boundary, and additivity conditions.
  • Phase as replacement or lineage. Another episteme, version label, or Work segment is treated as PhaseOf without applying C.2.1 or A.15.1.
  • Diagram or trace as relation. A breakdown, graph, table, construction trace, or validation mode is used as proof that parthood or identity obtains.