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:01:07 UTC · snapshot created 2026-10-03 08:04:31 UTC · last check 2026-10-03 08:05:10 UTC

A.1.SCR:8 - Common Anti-Patterns and Exact Repairs

Anti-patternWhy it failsRepair
Complete A.1 test before the decision is knownClassification work may change nothing.State what depends on systemhood; take the subject-pattern exit when it does not.
Pattern list without an actor/change bearerThe reader still cannot act.Name the exact subject and concrete decision.
Temporary reading treated as a kindEvaluation position becomes ontology.Keep one exact U.Entity under an admitted kind test.
Unknown as a third ontic stateMissing information becomes world-side indeterminacy.Name the missing input and blocked decision.
Neighbor bundleDifferent identity laws disappear.Return the subject first, then separately governed claims needed now.
Physical-realization identityCo-location or one embodiment merges kinds.Apply each identity rule and relation governor.
Project designation inferredRecognition or affectedness is mistaken for designation as the project system-of-interest.Name the plan or decision; test any system-role kind and system-role assignment separately.
Software service treated as systemSource-domain metonymy silently chooses a bearer.Begin in A.6.P, name the exact referent, and enter here only for a system-dependent claim.