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

• Shadow progression. Treating early/late as a master scale. Split the judgement into the named facets.
• Formality capture. Letting F stand in for closure or articulation. Publish those facets explicitly.
• Bundle inflation. Turning U.LanguageStateFacetProfile into a second A.19. Keep it thin and referential.
• Opaque readiness. Using words such as ready or mature without naming which facet justifies the claim.
• Route-note capture. Letting an informative route note act as a move rule, gate state, or endpoint rule. Keep route notes informative. Use A.16 for admissible moves, the applicable pattern for a downstream definition or test, the applicable gate or Work pattern for those claims, and an authoritySourceRef only when an external authority actually supplies the rule.