C.3.A:8 - Guard anti-patterns and remedies (informative)

Anti-pattern	Why it is wrong	Remedy
Widening G to repair kind mismatch	applicability is not typed compatibility	repair the order/bridge/adapter or refuse
Asking whether an unnamed candidate “counts”	hides candidate identity and signature edition	stay at declaration level or name the exact candidate and four inputs
Treating unavailable support as `false`	turns non-settlement into world-side failure	retain `unknown`; let the guard refuse separately
Treating a mask label as a kind	hides the declaration and constraints	designate the exact RoleMask edition and evaluate `J_mask`
Copying source classification through a bridge	bridge evidence is not target truth	recover the target declaration and evaluate the target candidate afresh
Gating on KindAT	the facet is not a guard Characteristic	use the actual declaration, judgment, scope, evidence, and policy predicates
Calling a plan, row, or JobSlice “the work”	erases the world/episteme boundary	identify the independently grounded dated Work occurrence when Work is current