C.19.2:8 - Common Anti-Patterns and How to Avoid Them

Anti-pattern	Repair
Configure everything because the basis is rich.	Name the useful-result threshold and retain only setup work with expected return.
Invent a rival to make the method look comparative.	Use the one-apparatus path until candidate or choice work is genuinely current.
Call candidate generation a choice.	Use `C.39` to explain a missing way or `C.40` to vary and examine usable material; let `C.11` operate on the existing eligible set. Add `C.18` when the generation account or archive/front claim matters.
Treat the apparatus-choice `ChoiceResult` as an application plan or the problem-facing result.	Keep selected object, plan, dated work, application note, and domain result separate.
Let a `U.MethodDescription` episteme, its described Method, a plan, option row, publication, or reader position perform Work.	State in ordinary language that an admitted System performs dated Work using the Method. Recover its A.13 core and independently admit the Work under A.15.1; add F.6 only when the present use needs precise assignment-bound attribution. Expand assignment and attribution detail only when that use needs it, attribution is ambiguous, or the source wording must be repaired.
Rank heterogeneous candidates under one hidden “depth” score.	Preserve direct kinds and compare only declared use-bearing dimensions without hidden scalarization.