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

Anti-pattern	Why it fails	Better use
Ready label as authorization	A label is treated as permission, conflict resolution, work authorization, or gate passage.	Use `A.2.8.PER` for the exact permission/conflict result, A.21 for gate decision, or A.15.4 when a reliance appearance is being used as a reason for work or reliance before the subject pattern slot, relation, or project-side reference is named.
Full kit as work done	Prepared inputs are treated as target work completion.	Record preparation work separately and target work only when it occurs.
Baseline as actuals	Planned slot fillers are treated as launch or performed values.	Keep planned fillers in A.15.3 and record variance after work.
MOVE imported as kind	TameFlow source wording becomes an FPF object.	Recover intended work, commitment, readiness, gate, preparation work, or performed work under FPF patterns.