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 14:36:52 UTC · snapshot created 2026-10-03 14:38:14 UTC · last check 2026-10-03 14:45:10 UTC

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

Anti-patternSymptomWhy it failsRepair
Pair object by juxtapositionTwo signatures are named and called U.SignatureEngineeringPair.No admitted kind, predicate, applicability, or occurrence identity exists.Retire the pair token; state the exact dependency or use that actually obtains, or merely name both signatures.
ConstructorSignature for every editA one-line revision acquires two operation lexicons, arrow metadata, assignment, evidence, and publication records.Reusable declaration work has replaced the actual task.State the direct revision and stop; add a ConstructorSignature only for a named reuse of its vocabulary and laws.
One publication mixes declaration and work recordTarget laws, constructor notes, review history, gates, and Work evidence share one undifferentiated artifact.Signature, operation description, application, Work, and carrier cannot be distinguished.Separate only the objects current for the receiving use; do not create a ConstructorSignature merely to hold notes.
Silent semantic editA law or applicability changes while consumers still cite the old episteme.A new C.2.1 discriminator triple is presented as the same episteme.Identify the successor episteme and the exact edition, continuity, or reference change actually used.
Arrow as performed operationAn A.6.2 arrow is said to author, validate, or publish a signature.Mathematical relation, application, and Work collapse.Let the arrow compare exact epistemes; identify any application, System, and Work separately.
View as another truthPlain and Tech faces add different commitments.Publication gained semantics.Keep each face a faithful E.17 publication form over the exact source episteme and state any new claim separately; use §4.4 for view membership and boundary claim-set integrity.
Episteme as actorThe ConstructorSignature builds or publishes the TargetSignature.Hides the acting System and gives agency to a description.Say what the signature describes; name the System and Work only when the receiving claim needs them.