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 10:39:28 UTC · snapshot created 2026-10-03 10:40:04 UTC · last check 2026-10-03 11:40:09 UTC

A.19.ECS:7 - Common Anti-Patterns and How to Avoid Them

Anti-patternSymptomRepair
Scale set from air.Coordinates appear because they are familiar.Rebuild from evaluated object kind, use, contrast cases, failure modes, domain tradition, first principles, and current source-use relation.
Wrong-kind object forced through the table.Objects outside the declared kind are either scored as weak members of that kind or silently exempted from declared coordinates.Add an object-kind-fit rule and boundary cases: before opening, return to a suitable evaluation; after invocation, record an explicit object-kind-fit defect/value or repair status.
Checklist masquerading as characteristic space.A list of tasks is treated as coordinates.Convert each task row to an evaluated EntityOfConcern property with a characteristic, scale, value meaning, and evidence rule, or move it to work planning.
One total quality score.Several ordinal values are averaged.Use coordinates, statuses, dominance or comparison rule, and protected trade-offs; do not scalarize unless an neighboring pattern governing the claim explicitly declares the operation.
Improvement without floor.A loop continues because more change is possible.State floor, exceptional meaning, stop condition, and reopen condition.
Hidden value drift.The evaluation changes while old evaluations are compared as if nothing changed.Version the evaluation and state comparability, bridge, or retirement.
Evaluation theft.The new evaluation starts asserting evidence, assurance, gate, work, decision, or publication truth without the corresponding predicate and case facts.State each neighboring subject assertion under its exact predicate or constraint and leave only the value evaluation here.
Result prose as evaluation.An evaluator returns a narrative, two-column table, checklist count, or value list without evidence basis and short rationales.Define the result-row shape, require short rationales and evidence basis, and apply the declared missingness rule to each coordinate whose needed evidence is missing or unchecked.
Evidence basis as evaluated-object method.Corpus projection, retrieval, currentness, comparator, monolith-parity, quality-status evidence, or author or reviewer turn correspondence is written in the evaluated object as if it were what the evaluated-object user does.Move the evidence to the evaluation result, evidence basis, projection carrier, or selected publication carrier; keep only the user action or boundary that the evidence justifies.
Coordinate wording as ontology change.A coordinate or repair name sounds cleaner, but changes the evaluated object kind, characteristic kind, relation or claim kind, admissible use, or scope.Treat it as a changed evaluation decision, recover the pre/post kind relation, and repair or reopen the evaluation rather than accepting lexical cleanup.