E.11.PUA:8 - Common Anti-Patterns and How to Avoid Them

Misuse	Why it fails	Repair
Select from the pattern name	Similar symptoms can have different problem frames and forces.	Inspect the direct pattern and state the result that would answer the current question.
Fill the candidate record first	The record freezes a choice before the `Solution` and boundary are understood.	Inspect first; materialize the candidate only for a named reliance.
Report generated text as the result	Text can describe a physical, clinical, organizational, or learned result without producing it.	Name the exact interim episteme and leave the subject expectation open.
Treat a support record as proof	A well-formed record does not by itself establish the recorded claims.	Establish each claimed inspection or Work occurrence, result, evidence relation, and later-use relation under the pattern that defines or tests that claim.
Call one result the next flow’s input	The same entity may participate in another TFS without changing kind, but an input/tool/context/constraint label does not identify that relation.	Name both `FlowPositionRef` values and the direct relation occurrence. Use E.18 for each local position and E.18.NET only for a current network of independently identified TFS values.