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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 16:02:47 UTC · snapshot created 2026-10-03 16:03:51 UTC · last check 2026-10-03 16:50:10 UTC

A.15.8:8 - Anti-patterns

  • Composite by coupling. Treating person, device, service, records, and environment as one performer because they jointly matter.
  • Future Work from a plan. Giving intended performance, intended performers, or proposed relations actual Work identity or obtaining attribution.
  • Umbrella slots. Adding universal attention, memory, cue, or Work-state fields instead of recovering exact objects and relations.
  • Carrier equals state. Treating a note, trace, checkpoint, model context, or file as identical to the world state or claim it carries.
  • Perfect-run readiness. Generalizing one successful live configuration to interruption, handoff, support loss, or changed conditions.
  • Probe as assurance. Treating success under one probe as universal capability, safety, permission, release, or certification.
  • FPF as domain algorithm. Inventing a universal timeout, checkpoint, cue, redundancy, practice, or recovery procedure in this pattern.
  • Configuration as architecture by default. Naming a support list a Structure or ArchitectureRelation without the direct admission and selection rules.