C.3.A:4.4 - Guard_MaskedUse — exact RoleMask use
Intent. Use exact candidate candidate under a named RoleMask declaration in TargetSlice.
Guard_MaskedUse(artifact, candidate, kind, kindSignatureEdition, roleMaskEdition, TargetSlice) SHALL:
- recover the exact C.2.1 RoleMask declaration episteme, its base kind, pinned base signature edition, intended use, candidate-feature constraints, bindings, dependencies, and definedness;
- check artifact scope separately through USM;
- evaluate
J_mask(candidate, kind, kindSignatureEdition, roleMaskEdition, TargetSlice); - continue only on
true, refuse while preserving knownfalse, and fail closed while preservingunknown; - keep context predicates out of the candidate-feature criterion; and
- for cross-context use, compare base-kind identity and recover target declarations; when this use requires a correspondence between distinct kinds, establish the KindBridge relation and assertion under C.3.3; recover any separate
MaskAdapterdeclaration episteme before evaluating the target masked judgment.
A mask name is not a kind synonym. Repeated mask use can trigger review for a separately identified local kind and independently obtaining U.SubkindOf relation; no guard or catalog action performs that admission.