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 02:22:15 UTC · snapshot created 2026-10-03 03:38:22 UTC · last check 2026-10-03 04:50:20 UTC

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

  • Meta-wrapper inflation. Treat A.16.0 as obligatory around every move. Repair by publishing a local A.16 move note unless a later use depends on the history.
  • One-publication myth. Record a changed claim discriminator under the same episteme edition. Repair by identifying the different epistemes and only the lineage links whose predicates obtain.
  • Pattern and form collapse. Treat a pattern reference as if it were a publication form. Repair by naming the form and the cited pattern’s concrete definition, constraint, or test separately.
  • Form and face collapse. Treat seam publications as if they minted a second MVPK face family. Repair by naming form and face separately.
  • Multi-route and fork collapse. Treat several live routes for one selected episteme edition as if they were already several successor epistemes.
  • Hidden work crossing or invented responsibility handoff. Do not describe operationalization as purely linguistic when it required new world-facing work, and do not treat that crossing or next-use docking as a responsibility transfer. Publish the work boundary; open the separate A.16.0:4.6 branch only for an actual responsibility, commitment, permission, or authority change.