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

• Maturity monism. Replace five facets with one stage word. Repair by publishing explicit slot placement.
• Formality capture. Use F to stand in for articulation, closure, or anchoring. Repair by naming the actual facet subject pattern.
• Carrier collapse. Treat a document, cue pack, or routed note as if it were the position itself. Repair by separating carrier lane, publication form, publication face, and position claim.
• Threshold folklore. Speak of readiness without any explicit threshold declaration. Repair by publishing relevant local threshold notes on explicit slots.
• Bridge by vibe. Similar stage language is treated as equivalence. Recover the two exact F.17 local senses and test F.9; cite a Bridge only when its predicate obtains. Otherwise keep both positions local and route the actual comparison or translation question.
• Corridor inflation. Treat the navigation cluster or corridor map as if it were the subject-pattern set for all downstream semantics. Repair by naming the pattern that governs the current chart, seam, or downstream claim; identify any seam publication form separately.